kevinveenbirkenbachandClaude Opus 5.5 05135a7cee feat(svc-net-wireguard): let a compose deployment name a hub with roaming spokes ...

Without a swarm manager the mesh planner only built full meshes, whose
handshake gate waits for every peer, so laptops behind NAT could not join.
An inventory may now name a hub in networks.hub: the planner builds every
declared mesh around it, the hub forwards between its spokes, a spoke marked
networks.roaming gets no endpoint in the hub's peer list and dials the hub
with PersistentKeepalive, and the hub's gate skips roaming spokes while a
roaming spoke gates only on the hub. The mesh CLI takes the hub's public
address per host (--endpoint) and a vault password per host
(--host-vault-password-file). Full meshes and the swarm manager hub plan
exactly as before; NETWORK_MESH_POOL keeps the operator's subnet.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-22 10:56:50 +02:00

..

cli

feat(svc-net-wireguard): let a compose deployment name a hub with roaming spokes

2026-10-22 10:56:50 +02:00

group_vars

test(wireguard): the layer follows group membership

2026-10-16 21:26:17 +02:00

library

refactor(python): clear the open CodeQL code-quality alerts

2026-10-20 21:40:58 +02:00

plugins

refactor(python): clear the open CodeQL code-quality alerts

2026-10-20 21:40:58 +02:00

roles

feat(svc-net-wireguard): let a compose deployment name a hub with roaming spokes

2026-10-22 10:56:50 +02:00

scripts

fix(apparmor): keep docker-default loaded when tearing AppArmor down

2026-10-20 12:11:14 +02:00

utils

feat(svc-net-wireguard): let a compose deployment name a hub with roaming spokes

2026-10-22 10:56:50 +02:00

__init__.py

…