jochen
e80a4b1642
mesh/delivery delivered
mesh/delivery-group group feat/a-machine-joins-through-the-tunnel delivered: every member is delivered
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go)
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.
11 lines
523 B
TypeScript
11 lines
523 B
TypeScript
import { test } from "node:test";
|
|
import assert from "node:assert/strict";
|
|
import { uplinkAddress } from "../src/lifecycle/raise.ts";
|
|
|
|
// A workstation behind a VPN client that routes every private range leaves incus nothing to pick, so
|
|
// the uplink's range may be named; otherwise incus picks it.
|
|
test("the uplink's range is incus's to pick unless the host names one", () => {
|
|
assert.equal(uplinkAddress({}), "auto");
|
|
assert.equal(uplinkAddress({ MESH_LAB_UPLINK_V4: " 192.168.231.1/24 " }), "192.168.231.1/24");
|
|
});
|