A ban list never holds a neighbour (hq ADR 0186) #227

2026-10-02T16:42:40Z

mesh-admin commented

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

Within an hour of the first public jail, the home server had banned 192.168.1.1, the house's own router. The router reflects local traffic, so every client in the building reaches that machine as the gateway's address: one local request for a name the mesh does not serve, three times in a day, and the whole house is refused by the machine it was asking.

The never-ban list now holds every private range in both families alongside the mesh's own, which was already named rather than written. The address was released by hand when it was found.

Within an hour of the first public jail, the home server had banned `192.168.1.1`, the house's own router. The router reflects local traffic, so every client in the building reaches that machine as the gateway's address: one local request for a name the mesh does not serve, three times in a day, and the whole house is refused by the machine it was asking. The never-ban list now holds every private range in both families alongside the mesh's own, which was already named rather than written. The address was released by hand when it was found.

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

A ban list never holds a neighbour (hq ADR 0186) 304044da40

The home server banned the house's own router within an hour of the first public jail: the router
reflects local traffic, so every client in the building arrives as the gateway's address. Every
private range joins the mesh's own in the never-ban list.

mesh-admin merged commit 810c7fbac3 into main

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

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

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

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#227