Parity test harness: golden-file diffs against shorewall + netns integration tests #12
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem. Commit
8d9a76cclaims coverage of all major shorewall featureswith 49 unit tests, but parity is asserted, not demonstrated. iptables→nftables
is not a clean mapping for policy first-match ordering, implicit intra-zone
accept, zone nesting, or ipsec zones — exactly the places subtle divergence
hides.
Proposal.
docs' worked examples) with the expected compiled nftables ruleset checked
in; CI diffs compiler output against them.
actual connectivity (accept/drop/dnat/masquerade paths) with real packets.
DNAT+masquerade interaction, nested zones, negated addresses, rate limiting.
Acceptance. CI fails when compiler output for any golden config changes
without the golden file being updated in the same PR.