dae, means goose, is a high-performance transparent proxy solution.
To enhance traffic split performance as much as possible, dae employs the transparent proxy and traffic split suite within the Linux kernel using eBPF. As a result, dae can enable direct traffic to bypass the proxy application's forwarding, facilitating genuine direct traffic passage. Through this remarkable feat, there is minimal performance loss and negligible additional resource consumption for direct traffic.
As a successor of v2rayA, dae abandoned v2ray-core to meet the needs of users more freely.
- Implement
Real Directtraffic split (need ipforward on) to achieve high performance. - Support to split traffic by process name in local host.
- Support to split traffic by MAC address in LAN.
- Support to split traffic with invert match rules.
- Support interface routing policies and reusable rule sets, composed across separate configuration files.
- Support to automatically switch nodes according to policy. That is to say, support to automatically test independent TCP/UDP/IPv4/IPv6 latencies, and then use the best nodes for corresponding traffic according to user-defined policy.
- Support advanced DNS resolution and caching through optional DNS plugins.
- Support full-cone NAT for shadowsocks, trojan(-go) and socks5 (no test).
- Support various trending proxy protocols, seen in proxy-protocols.md.
- Filter-based destination IP overrides without modifying DNS responses.
- Opt-in Surge Module HTTP/HTTPS scripts with a build-time choice of QuickJS-NG or Node.js, CA management, and a documented compatibility subset (Chinese).
Please refer to Quick Start Guide to start using dae right away!
The daemon requires Linux 6.13+ with the kernel features and runtime environment used by dae. Run sudo dae check-kernel to probe support before startup. Geo data files are required only by rules that reference them.
Source builds require Go 1.27.2+, cgo, a target C compiler, and Clang/LLVM for eBPF; see the build guide for static musl and cross-compilation.
The configuration example includes ordered plugins instances and rules flow controls / DNAT. Core DNS is a transparent relay with persistent domain evidence; advanced resolver/cache features are independent plugins. The default build includes Surge. Copy plugins.cfg.example to local plugins.cfg, add external Go plugins, and build them with dae.
DAE_LOCATION_CACHE selects the writable state directory for certificates, subscription caches and Surge resources (default /var/lib/dae).
- If dae shares a public host (such as a VPS) with a Shadowsocks or other UDP server, add
l4proto(udp) && sport(your_server_ports) -> musttorules {}and the same filter with-> directnear the top ofrouting {}. UDP replies to clients could otherwise be proxied or mistaken for DNS queries.mustskips automatic DNS interception;directselects direct forwarding. Avoid explicit bump, MITM or DNAT capture for these replies to keep them in the kernel. - If users in mainland China find that the first screen time is very long when they visit some domestic websites for the first time, please check whether you use foreign DNS to handle some domestic domain in DNS routing. Sometimes this is hard to spot. For example,
ocsp.digicert.cnis included ingeosite:geolocation-!cnunexpectedly, which will cause some tls handshakes to take a long time. Be careful to use such domain sets in DNS routing.
See How it works.
- Automatically check dns upstream and source loop (whether upstream is also a client of us) and remind the user to add sip rule.
- MACv2 extension extraction.
- Log to userspace.
- Protocol-oriented node features detecting (or filter), such as full-cone (especially VMess and VLESS).
- Add quick-start guide
- ...
Special thanks goes to all contributors. If you would like to contribute, please see the instructions. A 5813 lso, it is recommended following the commit-msg-guide.