daeuniverse/dae

eBPF-based Linux high-performance transparent proxy solution.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 10th, 2026
Created on January 23rd, 2023
Open Issues & Pull Requests: 203 (+0)
GitHub issues: Enabled
Number of forks: 401
Total Stargazers: 6,167 (+2)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 129
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 357 days
Stale 30+ days: 116
Stale 90+ days: 90

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • topic/feature (41)
  • automated-issue (15)
  • release (15)
  • topic/proposal (4)
  • enhancement (3)
  • good first issue (3)
  • ci (2)
  • topic/workaround (2)

Detailed Description

dae is an eBPF-based Linux high-performance transparent proxy solution.

dae addresses the performance overhead typical of proxy applications by implementing traffic splitting and forwarding directly within the Linux kernel using eBPF. This approach allows traffic destined for direct access to bypass the proxy application entirely, achieving minimal performance loss and negligible resource consumption for direct traffic. The tool supports splitting traffic by process name on the local host, by MAC address across a LAN, and through invert match rules. It can automatically switch between proxy nodes based on latency testing for TCP, UDP, IPv4, and IPv6 traffic according to user-defined policies. The project also provides advanced DNS resolution capabilities and supports full-cone NAT for shadowsocks, trojan, and socks5 protocols, along with various other trending proxy protocols.

dae is designed for users who need high-performance transparent proxying on Linux systems and want to minimize the overhead of proxy forwarding. It suits deployments where direct traffic performance is critical and where fine-grained traffic routing based on process, MAC address, or policy is required. The tool is positioned as a successor to v2rayA, abandoning v2ray-core to provide greater flexibility in meeting user needs.

The project maintains active development with regular commits and closed pull requests. Build workflows are consistently passing. The maintainers actively address issues and incorporate community contributions into the codebase.