Viktor Liu 4b298fb53c Fix legacy dynamic route NAT missing v6 duplicate ...

The v6 NAT duplication only triggered for DomainSet destinations
(modern DNS path). Legacy dynamic routes use a 0.0.0.0/0 prefix
destination, so the v6 NAT rule was never created.

Add a Dynamic field to RouterPair so the firewall manager can
distinguish dynamic routes from exit nodes (both use /0 prefixes).
Set it from route.IsDynamic() in routeToRouterPair and propagate
through GetInversePair. Both nftables and iptables managers check
pair.Dynamic instead of destination shape.

Also accumulate errors in RemoveNatRule so v6 cleanup is attempted
even if v4 removal fails.

2026-04-10 13:09:15 +02:00

..

iptables

Fix legacy dynamic route NAT missing v6 duplicate

2026-04-10 13:09:15 +02:00

manager

Fix legacy dynamic route NAT missing v6 duplicate

2026-04-10 13:09:15 +02:00

nftables

Fix legacy dynamic route NAT missing v6 duplicate

2026-04-10 13:09:15 +02:00

test

[client] Set up firewall rules for dns routes dynamically based on dns response (#3702)

2025-04-24 17:37:28 +02:00

uspfilter

Add IPv6 dispatch for OutputDNAT, fix v6 guard pattern, rename DNAT params

2026-04-10 12:32:41 +02:00

create_linux.go

[client] Use native firewall for peer ACLs in userspace WireGuard mode (#5668)

2026-04-10 09:12:13 +08:00

create.go

[client] Clamp MSS on outbound traffic (#4735)

2025-11-04 17:18:51 +01:00

iface.go

[client] Use native firewall for peer ACLs in userspace WireGuard mode (#5668)

2026-04-10 09:12:13 +08:00