The proxy is told its routes and the mesh on the bus, and serves internal names to the mesh only (hq issue 191, ADR 0167) #207

2026-10-01T22:39:20Z

jschoubben commented

2026-10-01 22:39:20 +00:00

Fixes novox/hq issue 191, as decided in hq ADR 0167.

1. A route with only an internal name is served (first commit). Since ADR 0138, an endpoint that reaches only the private network gets an internal-name and no name. The proxy used to skip it.

2. Memberships carry what a module receives, and who the mesh is. Compose reports each module's received contributions: the same list its received file is written from, same-node port fix included. Push issues them in the membership as receives, together with mesh, every machine's private-network address. That's the list the filter's "from the mesh" is rendered from.

3. The proxy follows its membership. It connects with its bus account, reads mesh.assignment.<node>.route-proxy by direct get, and follows it live.

Routes come from receives.route.
Internal names are served only to the addresses in mesh and to loopback. Anyone else gets the same answer as for an unrouted name: in the request, in the TLS handshake, and in the 404's list of served names.
Until a membership with routes arrives, it serves the file, and internal names to its own machine alone.

Release order: mesh-catalog 211, issue the proxy's credential on each machine, then this PR, then push.

Tests:

received_on_the_bus_test.go: bus and file carry identical routes.
reach_test.go: who is served what, the handshake, membership application, and unreadable input.
Every access test fails with the check disabled.
go test -race ./... passes.

Fixes novox/hq issue 191, as decided in hq ADR 0167. **1. A route with only an internal name is served** (first commit). Since ADR 0138, an endpoint that reaches only the private network gets an `internal-name` and no `name`. The proxy used to skip it. **2. Memberships carry what a module receives, and who the mesh is.** `Compose` reports each module's received contributions: the same list its received file is written from, same-node port fix included. Push issues them in the membership as `receives`, together with `mesh`, every machine's private-network address. That's the list the filter's "from the mesh" is rendered from. **3. The proxy follows its membership.** It connects with its bus account, reads `mesh.assignment.<node>.route-proxy` by direct get, and follows it live. - Routes come from `receives.route`. - Internal names are served only to the addresses in `mesh` and to loopback. Anyone else gets the same answer as for an unrouted name: in the request, in the TLS handshake, and in the 404's list of served names. - Until a membership with routes arrives, it serves the file, and internal names to its own machine alone. **Release order:** mesh-catalog 211, issue the proxy's credential on each machine, then this PR, then push. Tests: - `received_on_the_bus_test.go`: bus and file carry identical routes. - `reach_test.go`: who is served what, the handshake, membership application, and unreadable input. - Every access test fails with the check disabled. - `go test -race ./...` passes.

jschoubben added 1 commit 2026-10-01 22:39:20 +00:00

route-proxy: serve a route that names only its internal host 9acb5f1292

Since ADR 0138 an endpoint that reaches only the private network gets an
internal-name and no name, and the proxy skipped it as naming nothing, so
every internal-only module was unreachable by name (novox/hq issue 191).

jschoubben added 1 commit 2026-10-01 23:48:19 +00:00

The proxy is told its routes and the mesh on the bus, and serves internal names to the mesh only 24f024dd74

The proxy answered every routed name to any request carrying it, so an
internal-only route would have been public under its internal name. Each
membership now carries what its module receives, from the same
composition as its received file, and every machine's private-network
address, the list the packet filter's "from the mesh" is. The proxy
follows its membership, serves internal names only to those machines and
itself, and keeps the file until the bus has spoken (novox/hq ADR 0167,
issue 191).

jschoubben force-pushed jschoubben/an-internal-only-route from 0fcea460da to 24f024dd74

2026-10-01 23:48:19 +00:00

Compare

mesh-admin changed title from ~~route-proxy: serve a route that names only its internal host (hq issue 191)~~ to The proxy is told its routes and the mesh on the bus, and serves internal names to the mesh only (hq issue 191, ADR 0167)

2026-10-01 23:48:38 +00:00

mesh-admin merged commit cf495e315f into main

2026-10-02 07:42:46 +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#207