A carried peer is nameable, and the mesh answers for it (hq 112) #73

2026-09-26T18:09:53Z

jschoubben commented

2026-09-26 18:09:53 +00:00

Issue 112's first open question, answered as the operator directed: yes, a carried peer is nameable. overlay name <address> <name> records the operator's statement on tunnel_peer.named (migration 0033); namesInTheMesh answers for named not-yet-enrolled peers — one reading, so the hosts fact, a container's hosts and the resolver cannot disagree. Enrolment verifies the word: a machine enrolling under a named peer's key with a different name is refused legibly, the stated name keeps the carried address, an enrolled peer cannot be renamed. Three tests against real postgres cover the statement, every refusal, and both enrolment paths. Unblocks the resolver cutover: the mesh's dnsmasq will answer for all four machines the moment the peers are named.

Issue 112's first open question, answered as the operator directed: yes, a carried peer is nameable. `overlay name <address> <name>` records the operator's statement on `tunnel_peer.named` (migration 0033); `namesInTheMesh` answers for named not-yet-enrolled peers — one reading, so the hosts fact, a container's hosts and the resolver cannot disagree. Enrolment verifies the word: a machine enrolling under a named peer's key with a different name is refused legibly, the stated name keeps the carried address, an enrolled peer cannot be renamed. Three tests against real postgres cover the statement, every refusal, and both enrolment paths. Unblocks the resolver cutover: the mesh's dnsmasq will answer for all four machines the moment the peers are named.

jschoubben added 1 commit 2026-09-26 18:09:53 +00:00

A carried peer is nameable, and the mesh answers for it (hq 112) 952092ccb3

The tunnel the hub took over routes to machines the predecessor knows
by name and the mesh knew only by address — taking the resolver in that
state silences three machines at once. Now the operator states which
machine a carried address is (overlay name <address> <name>), the
statement rides tunnel_peer.named, and namesInTheMesh answers for named
not-yet-enrolled peers — one reading, so the hosts fact, a container's
hosts and the resolver cannot disagree. Enrolment verifies the word:
a machine enrolling under a named peer's key with a different name is
refused where the operator can read it, the stated name keeps the
carried address, and an enrolled peer's name is the node's — naming it
again refuses. The issue's rule holds: a name the predecessor answers
for keeps resolving until the machine behind it is a node.

jschoubben merged commit 2f7b407000 into main

2026-09-26 18:10:00 +00:00

jschoubben deleted branch feat/112-a-carried-peer-is-nameable

2026-09-26 18:10:00 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#73