eBPF-based Linux high-performance transparent proxy solution.
Go to file
2023-01-29 11:19:58 +08:00
.github/workflows chore: add github actions (#1) 2023-01-28 18:32:42 +08:00
cmd fix: panic when there is any lexer error 2023-01-28 18:51:21 +08:00
common feat: support not operator and port, sport routing func 2023-01-29 07:31:52 +08:00
component fix: routing problems 2023-01-29 11:19:58 +08:00
config chore: update copyright 2023-01-28 13:56:06 +08:00
install chore: add github actions (#1) 2023-01-28 18:32:42 +08:00
pkg fix: routing problems 2023-01-29 11:19:58 +08:00
.gitignore feat: support not operator and port, sport routing func 2023-01-29 07:31:52 +08:00
example.conf fix: routing problems 2023-01-29 11:19:58 +08:00
go.mod fix: routing problems 2023-01-29 11:19:58 +08:00
go.sum fix: routing problems 2023-01-29 11:19:58 +08:00
insert.sh optimize: use bpf_map to reduce insns 2023-01-28 11:47:02 +08:00
LICENSE init 2023-01-23 19:54:21 +08:00
logo.png init 2023-01-23 19:54:21 +08:00
main.go chore: update copyright 2023-01-28 13:56:06 +08:00
Makefile chore: add github actions (#1) 2023-01-28 18:32:42 +08:00
README.md feat: support config file 2023-01-28 01:50:21 +08:00

dae

dae, means goose, is a lightweight and high-performance transparent proxy solution.

In order to improve the traffic diversion performance as much as possible, dae runs the transparent proxy and traffic diversion suite in the linux kernel by eBPF. Therefore, we have the opportunity to make the direct traffic bypass the forwarding by proxy application and achieve true direct traffic through. Under such a magic trick, there is almost no performance loss and additional resource consumption for direct traffic.

As a successor of v2rayA, dae abandoned v2ray-core to meet the needs of users more freely. In the initial conception, dae will serve soft router users first, and may also serve desktop users later.

Usage

Build:

git clone https://github.com/v2rayA/dae.git
cd dae
make

Run:

./dae run -c example.conf

See example.conf.

TODO

  1. Check dns upstream and source loop (whether upstream is also a client of us) and remind the user to add sip rule.
  2. Domain routing performance optimization.
  3. Support not operator for RoutingA rule.
  4. DisableL4Checksum by link.
  5. Handle the case that nodes do not support UDP.
  6. ...