d8239fcd32732fa4b9bb5f96bee170ffe6bff6e0
The mesh-only accept rules used 'ip46tables ... -s 100.x/16'. ip46tables runs every rule through iptables AND ip6tables; ip6tables cannot parse an IPv4 CIDR and aborts with 'host/network not found', failing the whole firewall.service (status 2). Consequence beyond the unit failure: the firewall-start script aborted at the first such rule, so the trailing default-reject rules were never applied — the input filter was effectively OPEN (only SSH/established rules had been added). This also explains why the mesh services were reachable although the previous 100.64.0.0/16 source rule never matched any peer. Fix: match on the NetBird interface (-i wt0) instead of a source range — family-agnostic, survives NetBird range changes, and matches the idiom the generated script already uses for NetBird service ports. Applied to ai-memory, hermes-dashboard and t3code rules (add + stop-commands). After deploying: firewall.service completes, default-reject applies, and 49374/9119/8642/3773 become reachable from the mesh ONLY (previously open to everyone). Anything that silently relied on the open filter will start failing — that is the intended posture.
Languages
Nix
87.5%
JavaScript
6.7%
Shell
5.8%