dannydannydanny/dotfiles
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(clan): add internet networking instance for LAN reachability 🛣️

Browse source 
clan-cli preferred the zerotier networking export (priority 900, user
defaulted to root@) over our clan.core.networking.targetHost setting,
which broke \`clan machines update\` with "Host key verification failed"
against the ZT IPv6 address as root@. Declaring an inventory.instances
.internet instance with priority 2000 makes clan-cli prefer the LAN
hostname and explicit danny@ user, so updates go over the LAN (ZT
stays available for SSH aliases and service-level use).
This commit is contained in:
DannyDannyDanny 2026-04-19 21:09:37 +02:00
parent 84da9ed8f5
commit 32cb3b7510
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
flake-modules/clan.nix
View file

@ -37,6 +37,22 @@ in {
roles.peer.machines.sunken-ship = { };
};
# Direct SSH reachability on the LAN. Priority 2000 > ZT's 900, so
# `clan machines update` prefers LAN hostnames over ZT IPv6 — and uses
# the right user (ZT service defaults to root@).
inventory.instances.internet = {
module.name = "internet";
module.input = "clan-core";
roles.default.machines.sunken-ship.settings = {
host = "sunken-ship";
user = "danny";
};
roles.default.machines.phantom-ship.settings = {
host = "phantom-ship";
user = "danny";
};
};
# Preserve current network / init stack (no systemd-networkd/resolved,
# no boot.initrd.systemd, no extra debug packages). Revisit per-service
# in later stages rather than flipping this fleet-wide.