ADR 0186: a ban list never holds a neighbour, and the mesh's own bans are its own wherever they hang #299

2026-10-02T16:42:41Z

mesh-admin commented

2026-10-02 16:42:41 +00:00

Two faults the first public jails turned up within the hour, one mistake in two places: a rule written about the public internet, applied to everything that arrives.

The record also states plainly why the home server's found-firewall note is stale (its retirement step runs only after a clean apply, and that machine has an unrelated stuck module) and that the front end's removal record is now 0180.

Design 31 gains the lesson. records, cycle and index pass.

Two faults the first public jails turned up within the hour, one mistake in two places: a rule written about the public internet, applied to everything that arrives. The record also states plainly why the home server's found-firewall note is stale (its retirement step runs only after a clean apply, and that machine has an unrelated stuck module) and that the front end's removal record is now 0180. Design 31 gains the lesson. records, cycle and index pass.

mesh-admin added 1 commit 2026-10-02 16:42:41 +00:00

ADR 0186: a ban list never holds a neighbour, and the mesh's own bans are its own wherever they hang; design 31 d4a2f99ab5

mesh-admin merged commit d57289e049 into main

2026-10-02 16:43:33 +00:00

mesh-admin deleted branch fix/a-ban-list-never-holds-a-neighbour

2026-10-02 16:43:34 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#299