docs: two live-hit gotchas - stale WireGuard nodes, iptables-legacy #224

Merged
mysticalsoap merged 1 commit from docs/wg-stale-node-and-iptables-legacy into trunk 2026-09-17 01:05:47 -04:00
Owner

Two README one-liners from the WireGuard bypass verification rounds, each of which cost a diagnosis pass:

  • WireGuard section: a server that comes up but never completes a handshake is stale imported peer data (key or address rotated since the last import) - WireGuard ignores an unknown key silently. Update the provider.
  • Firewall section: on nf_tables systems aqomui writes through iptables-legacy; plain iptables -L shows a different table and mislead the first capture.

Docs only.

🤖 Generated with Claude Code

Two README one-liners from the WireGuard bypass verification rounds, each of which cost a diagnosis pass: - **WireGuard section**: a server that comes up but never completes a handshake is stale imported peer data (key or address rotated since the last import) - WireGuard ignores an unknown key silently. Update the provider. - **Firewall section**: on nf_tables systems aqomui writes through `iptables-legacy`; plain `iptables -L` shows a different table and mislead the first capture. Docs only. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
docs: two live-hit gotchas - stale WireGuard nodes, iptables-legacy
All checks were successful
ci / test (pull_request) Successful in 24s
8756861138
Both cost a diagnosis round during the WireGuard bypass verification:
a node that connects but never handshakes is stale imported peer
data (WireGuard drops unknown keys silently), and aqomui's rules live
in the legacy backend on nf_tables systems, where plain iptables
shows another table.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mysticalsoap deleted branch docs/wg-stale-node-and-iptables-legacy 2026-09-17 01:05:47 -04:00
Sign in to join this conversation.
No description provided.