Johnathan Corgan be5deee814 Make the gateway integration suite safe for concurrent CI runs ...

gateway-lan pinned 172.20.1.0/24 and fd02::/64, so two concurrent local CI
runs collided on "Pool overlaps" at network creation. The IPv4 subnet has no
consumer -- the whole gateway LAN path is IPv6 -- so drop it and let docker
auto-assign. The IPv6 side cannot float, because the LAN clients' resolv.conf
pins the gateway's address as their nameserver and that must be a literal
known before they start, so claim a free /64 per run and thread the prefix
through the compose address pins, a generated resolv.conf, and the test via a
single exported variable.

The claim and the external network ship as a harness-only compose overlay
applied by run_gateway; the base compose keeps a normal gateway-lan network,
so the GitHub matrix and any standalone bring-up are unaffected. With no claim
every address renders exactly as before.

2026-07-23 19:50:17 +00:00

..

admission-cap-test.sh

Let the static test network float so concurrent CI runs cannot collide

2026-07-23 02:05:56 +00:00

bench-multirun.sh

Teach the trailing-log gate to see command-substitution call sites

2026-07-23 15:45:37 +00:00

gateway-test.sh

Make the gateway integration suite safe for concurrent CI runs

2026-07-23 19:50:17 +00:00

generate-configs.sh

Make the gateway integration suite safe for concurrent CI runs

2026-07-23 19:50:17 +00:00

iperf-compare-refs.sh

testing: add boringtun throughput benchmark and iperf ref-compare harness

2026-05-15 18:03:42 +00:00

iperf-test.sh

Let the static test network float so concurrent CI runs cannot collide

2026-07-23 02:05:56 +00:00

netem.sh

Teach the trailing-log gate to see command-substitution call sites

2026-07-23 15:45:37 +00:00

ping-test.sh

Fail the ping test on an unknown topology profile

2026-07-23 07:13:32 +00:00

rekey-test.sh

Stop a node whose logs cannot be read from counting as a clean node

2026-07-23 15:30:01 +00:00