You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tailscale/net/tstun
Maisem Ali 3ae7140690 net/tstun: handle exit nodes in NAT configs
In the case where the exit node requires SNAT, we would SNAT all traffic not just the
traffic meant to go through the exit node. This was a result of the default route being
added to the routing table which would match basically everything.

In this case, we need to account for all peers in the routing table not just the ones
that require NAT.

Fix and add a test.

Updates tailscale/corp#8020

Signed-off-by: Maisem Ali <maisem@tailscale.com>
2 years ago
..
table net/tstun/table: add initial RoutingTable implementation 2 years ago
fake.go all: update copyright and license headers 2 years ago
ifstatus_noop.go all: update copyright and license headers 2 years ago
ifstatus_windows.go all: update copyright and license headers 2 years ago
linkattrs_linux.go all: update copyright and license headers 2 years ago
linkattrs_notlinux.go all: update copyright and license headers 2 years ago
mtu.go envknob,net/tstun,wgengine: use TS_DEBUG_MTU consistently 2 years ago
mtu_test.go envknob,net/tstun,wgengine: use TS_DEBUG_MTU consistently 2 years ago
tap_linux.go all: update copyright and license headers 2 years ago
tap_unsupported.go all: update copyright and license headers 2 years ago
tun.go envknob,net/tstun,wgengine: use TS_DEBUG_MTU consistently 2 years ago
tun_linux.go all: update copyright and license headers 2 years ago
tun_macos.go all: update copyright and license headers 2 years ago
tun_notwindows.go all: update copyright and license headers 2 years ago
tun_windows.go all: update copyright and license headers 2 years ago
wrap.go net/tstun: handle exit nodes in NAT configs 2 years ago
wrap_test.go net/tstun: handle exit nodes in NAT configs 2 years ago