superconfig/retiolum/ at 8476fd64554f0fc08648d930aba09d97ca51d5e9 · lass.pds.lassul.us/superconfig · Tangled

lass.pds.lassul.us / superconfig

0

This repository has no description

0

superconfig / retiolum

2 files

at 8476fd64554f0fc08648d930aba09d97ca51d5e9

lassulus machines/acheron: add gg23 router replacing styx 5w ago

machines/acheron: add gg23 router replacing styx Intel N355 mini PC, 2x I226-V, UEFI/NVMe disko, systemd-boot. Only 2configs + retiolum + gg23 for now; NIC naming matches styx (et0 uplink, int0 LAN). Retiolum card in retiolum/ (10.243.11.2), server tag.

1 month ago

flake-module.nix

retiolum: keep non-kartei peers in self.retiolum starkstrom stays out of the shared kartei registry but should still be reachable inside the fleet. Its card now lives in retiolum/ in the same nets.<net> layout kartei and krebs.hosts use, rendered by a copy of kartei modules/retiolum/hosts.nix, so the entry can move to kartei/lass unchanged if the rest of krebs should reach it too. Every superconfig machine injects that set into its tinc hosts: the NixOS nodes through nixpkgs services.tinc, barnacle through kartei tincr module (hosts is attrsOf lines, so the entries merge). Previously only starkstrom itself knew its card, so the fleet had no route to it; now all 16 machines do, and peers dial its static address directly instead of relaying. self.retiolum exposes hosts/tincHosts/own, the same interface as kartei, so both sources merge symmetrically. starkstrom krebs.hosts card is composed from it -- addresses, aliases and the ed25519 key have one source now; only the legacy RSA pubkey stockholm insists on stays local.

1 month ago