Kristoffer Dalby bca6e6334d integration: add custom subnet support and fix exit node tests ...

Add NetworkSpec struct with optional Subnet field to ScenarioSpec.Networks.
When Subnet is set, the Docker network is created with that specific CIDR
instead of Docker's auto-assigned RFC1918 range.

Fix all exit node integration tests to use curl + traceroute. Tailscale
exit nodes strip locally-connected subnets from their forwarding filter
(shrinkDefaultRoute + localInterfaceRoutes), so exit nodes cannot
forward to IPs on their Docker network via the default route alone.
This is by design: exit nodes provide internet access, not LAN access.
To also get LAN access, the subnet must be explicitly advertised as a
route — matching real-world Tailscale deployment requirements.

- TestSubnetRouterMultiNetworkExitNode: advertise usernet1 subnet
  alongside exit route, upgraded from ping to curl + traceroute
- TestGrantViaExitNodeSteering: usernet1 subnet in via grants and
  auto-approvers alongside autogroup:internet
- TestGrantViaMixedSteering: externet subnet in auto-approvers and
  route advertisement for exit traffic

Updates #2180

2026-04-01 14:10:42 +01:00

..

build.go

cmd/hi: improve test cleanup to reduce CI disk usage (#2881)

2025-11-28 16:59:54 +01:00

config.go

all: fix golangci-lint issues (#3064)

2026-02-06 21:45:32 +01:00

execute.go

integration: make docker execute and ping timeouts CI-aware

2026-03-31 22:06:25 +02:00

logs.go

all: fix golangci-lint issues (#3064)

2026-02-06 21:45:32 +01:00

network.go

integration: add custom subnet support and fix exit node tests

2026-04-01 14:10:42 +01:00