a2f3410e42
Add per-site and per-box inventories, consolidate shared network design, and relocate the switch and access-point references under the home site.
1.8 KiB
1.8 KiB
qclk
A WireGuard management appliance for the qclk network — it terminates the management
tunnel and routes/NATs the qclk prefix. No service daemon is currently defined in the config;
the container provides the network plumbing and opens the API port.
- Source:
shill/containers/qclk/(default.nix) - Host: NixOS container on
shill - nixpkgs:
mine
Role
- WireGuard
managementinterface — listens on UDP51821(lib.my.c.colony.qclk.wgPort, allowed through the firewall;estuaryport-forwards it here) with the private key from theqclk/wg.keyage secret. Managed devices are static peers, each pinned to its own address in theqclkprefix; the peer list currently has a single entry. - Routing/NAT —
shillroutes theqclkprefix to this container, and outbound traffic fromhost0intomanagementis SNATed to the container'sqclkaddress. Forwarding intomanagementis accepted from the AS211024 trusted IPv4 ranges (lib.my.c.as211024.trusted.v4). - API port — TCP
8080is accepted on themanagementinterface (apiPort), but noteservices = { }: whatever serves the qclk API is not defined in this configuration today.
Network assignments
See the consolidated network assignments table (this box: qclk).
Two assignments: internal on the ctrs network like the other containers, and qclk on the
management WireGuard interface (IPv4 only, no DNS name).
Notable config files
nixos/boxes/colony/vms/shill/containers/qclk/default.nix— container definition: WireGuard netdev, peer list and firewall rules