jochen e80a4b1642 Prove a machine joins through the tunnel in a bed of its own ...

Two machines: the anchor raises the foundation, joins over its own
loopback and becomes the hub; the joiner makes its tunnel key, is issued
a token for it and enrols with the bus's port closed to its own address,
so the enrolment can arrive only over the tunnel (novox/hq ADR 0169). The
check that had been added to the two-node walk moves here, closing the
port the bundle publishes the bus on rather than the bus's own.

And the uplink's range may be named: behind a VPN client that routes
every private range, incus had none left to pick and no scenario could
be raised.

2026-10-08 01:52:58 +02:00

..

a-provider.yml

Scenarios: egress where images are needed, and images: cut to what is ours

2026-09-10 23:16:23 +02:00

a-public-name.yml

Scenarios: egress where images are needed, and images: cut to what is ours

2026-09-10 23:16:23 +02:00

adopted-store-cross-node.yml

A two-node bed: a joined node opening the adopted broker over the overlay (055)

2026-09-17 01:01:54 +02:00

adoption.yml

Adoption bed (in progress): a machine in use raised adopted, held, opened through its firewall, taken and converged (hq ADR 0100-0103)

2026-09-22 18:19:36 +02:00

an-object-store.yml

Scenarios: egress where images are needed, and images: cut to what is ours

2026-09-10 23:16:23 +02:00

anthropic-bed.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

audit-node.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

behind-nat.yml

The home segment moves off 192.168.1.0/24

2026-09-11 00:00:19 +02:00

bootstrap-single.yml

place: the host — the lab acquires a consumer

2026-08-26 00:41:25 +02:00

built-store-cross-node.yml

The no-fake multi-node bed: two machines, everything built by the mesh itself

2026-09-17 22:15:34 +02:00

catalogue-apps.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

catalogue-media.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

catalogue-mqtt.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

catalogue-small.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

first-node.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

fresh-mesh.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

genesis-single.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

grafana-node.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

growing-mesh.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

joins-through-the-tunnel.yml

Prove a machine joins through the tunnel in a bed of its own

2026-10-08 01:52:58 +02:00

lavinmq-bed.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

local-model-bed.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

model-usage-bed.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

one-node-mesh.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

openai-bed.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

redis-node.yml

Six beds retired: their coverage lives in the catalogue beds and the whole-mesh beds now

2026-09-21 21:53:11 +02:00

route-forwarding.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

schedule-tick.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

segmented-and-unforwardable.yml

The home segment moves off 192.168.1.0/24

2026-09-11 00:00:19 +02:00

store-window.yml

A bed that takes the store away while a machine enrols, and holds the enrolment to completing on its own (novox/hq issue 083)

2026-09-22 14:08:45 +02:00

the-ordinary-shape.yml

The home segment moves off 192.168.1.0/24

2026-09-11 00:00:19 +02:00

tools-confluence.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

tools-gitlab.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

trust-anchor.yml

A bed for the trust anchor, and the bundle rewrite its foundation needs

2026-09-29 15:26:05 +02:00

two-node-db.yml

Review of 081: the bed asserts baserow chose its own cache and it challenges for its password; the check reads only what a module hands its software; stale comments

2026-09-22 12:34:59 +02:00

two-nodes.yml

Prove a machine joins through the tunnel in a bed of its own

2026-10-08 01:52:58 +02:00

two-on-a-segment.yml

Scenario lifecycle: raise, exec, snapshot, restore, destroy

2026-08-24 01:12:49 +02:00

vault-node.yml

A bed for the vault: redis's password as a secret it provides, rotated

2026-09-21 00:01:50 +02:00

whole-mesh-ace.yml

Review of 081: the bed asserts baserow chose its own cache and it challenges for its password; the check reads only what a module hands its software; stale comments

2026-09-22 12:34:59 +02:00

whole-mesh-full.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

whole-mesh-novox.yml

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00