How daeuniverse/dae works
dae is a Linux transparent proxy that splits traffic using eBPF and userspace forwarding. The principal workflow is configuration loading, policy construction, packet interception and routing, then direct or proxy egress; DNS has its own request, upstream, response, and cache stages. Runtime reloads replace policy generations while the session manager preserves established flows. The README documents process/MAC rules, automatic node selection, DNS, and proxy protocols. Some subsystem links are documented rather than verified in sampled callers; those are marked dashed.
Main entry points: dns_controller_handle.go DNS controller · control_plane.go Control plane · main.go CLI entry · run_reload_worker.go Reload worker
Components 21
Runtime lifecycle
- CLI entry
main.go - Config parser
config/parser.go - Reload manager
cmd/reload_manager.go - Reload worker
cmd/run_reload_worker.go - Control plane
control/control_plane.go - Flow sessions
control/session_manager.go
Policy and routing
- Traffic policy
component/routing/ir.go
Traffic forwarding
- Outbound groups
component/outbound/dialer_group.go - Proxy dialers
component/outbound/dialer/dialer.go - Node health checks
component/outbound/dialer/connectivity_check.go - Protocol sniffing
component/sniffing/sniffer.go
DNS services
- DNS controller
control/dns_controller_handle.go - DNS cache
control/dns_controller_cache.go - Request routing
component/dns/request_routing.go - Response routing
component/dns/response_routing.go - DNS upstream router
component/daedns/router.go - DNS client
component/daedns/client.go - DNS transports
component/dnstransport/wire.go
Kernel datapath
- eBPF datapath
control/kern/tproxy.c - Kernel tracing
trace/trace.go
Other components
- Operator
Connections 21
- Operator → CLI entry: runs
main.go - CLI entry → Config parser: loads config
- CLI entry → Reload manager: starts runtime
- Reload manager → Reload worker: queues reload
cmd/reload_manager.go - Reload worker → Config parser: loads config
cmd/run_reload_worker.go - Reload worker → Control plane: prepares generation
cmd/run_reload_worker.go - Control plane → Flow sessions: uses sessions
- Config parser → Traffic policy: defines rules
- Control plane → eBPF datapath: installs datapath
- Control plane → DNS controller: configures DNS
- Traffic policy → Outbound groups: selects egress
- Outbound groups → Proxy dialers: dispatches
component/outbound/dialer_group.go - Node health checks → Outbound groups: informs selection
- Protocol sniffing → Traffic policy: supplies traffic metadata
- DNS controller → DNS cache: reads and writes
control/dns_controller_handle.go - DNS controller → Request routing: routes queries
- DNS controller → Response routing: routes replies
- DNS controller → DNS upstream router: resolves upstream
control/dns_controller_handle.go - DNS upstream router → DNS client: queries upstream
component/daedns/client.go - DNS client → DNS transports: sends DNS
component/daedns/client.go - eBPF datapath → Kernel tracing: supports tracing