Some checks failed
validate / lint (push) Failing after 1s
Found live on the first deployment of the auto-recovery controller (2026-09-22): pia-gateway register correctly refused with "FORWARD jump to kill-switch chain is not first". Root cause confirmed on minisforum via iptables -S FORWARD/-S KUBE-ROUTER-FORWARD/-S DOCKER-USER/-S DOCKER-FORWARD: the PIA-VLAN50 jump was 4th, behind kube-router's and dockerd's own jumps, which each independently reassert position 1 on their own resyncs/restarts (kube-router had even left a duplicate of its own rule behind). pia-killswitch.sh.j2 only checked whether its jump existed (iptables -C) before deciding not to touch anything — existence isn't proof of position, so once pushed down it stayed down. Confirmed safe to reposition unconditionally by reading the actual content of what's ahead of it rather than assuming: KUBE-ROUTER-FORWARD only matches specific pod /32 addresses, DOCKER-USER was empty, and DOCKER-FORWARD's one direct rule is scoped to -i docker0 (VLAN 50 arrives via enp1s0) - none can intercept VLAN 50 traffic regardless of order. Fixed the script itself (delete + reinsert at position 1 if the current first rule isn't ours) rather than loosening the Python controller's forward_jump_first safety check, which was working correctly when it refused to register against the drifted state. Verified offline: rendered template passes bash -n, and the exact live topology (rule present but 4th) reproduced against a bash mock of iptables, confirming reposition-when-drifted, idempotency when already first, and insert-when-absent all behave correctly. No real iptables/wg/ip on this dev machine to test further; not yet re-applied or re-verified against minisforum. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>