Give agents their own kernel, Nix daemon and disk for workloads that
need root. Put the VM on the `untrusted` VLAN with MAC spoof
checking on VF 5.
Export a dedicated partition from `cellar` and connect it on
`palace`. Give the VM its own SSH host key and age secrets for Paseo
and Gitea. Keep the agent home and Paseo identity on persistent
storage and provide `slop-pair` for pairing clients.
Retire the container, restore `sfh` to 8 cores and 32 GiB, and rekey
the shared password secret. Document the VM and its operating
procedures on the relevant box pages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An absent webcam made the nspawn bind mount fail before Home
Assistant could start. Give the container an always-present
directory and bind the video device into it when it is available.
Point go2rtc at the device in that directory.
Restore the bubblewrap diagnostic expected by Codex so its existing
container fallback handles nspawn procfs restrictions.
Verified workspace writes succeed and outside writes are denied.
`check-system slop-cannon` passes.
Serve the web app from the Paseo package on `paseo.nul.ie` and point
the daemon's pairing links there, so browsers no longer load Paseo's
hosted app. It connects through our relay, so the daemon stays on
loopback.
Move the patched Paseo package into the shared overlay so `middleman`
and `slop-cannon` use the same build.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A container on `sfh` for coding agents driven remotely through Paseo,
using our relay on `middleman`. Agents run as the unprivileged
`slop-cannon` user; Claude managed settings disable bypass mode and
deny raw deploy and `ssh-machine` access.
Move the Claude Code and Codex configuration out of `gui` into a
shared `my.agents` home-manager module.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Give `river` a dedicated RDMA VF and two RSTP trunk attachments.
Keep client services on the router VIPs and carry Digiweb VLANs
over both switch paths.
Set VF trust, multicast reception, bridge MAC and ARP behavior for
local switching. Wait for Kea interface readiness and apply RSTP
costs through `mstpd` despite port-registration and rename races.
Load `palace`'s RAID module in the initrd. Record RouterOS and
RouterBOOT upgrades and validate port, carrier and switch outages.
Document the deployed architecture, interface handoffs and recovery
procedures. Add physical socket maps, NIC capacities and cable
connections alongside the logical topology and failover checks.
Rebase the fork branches and refresh nixpkgs, home-manager, and the
approved ancillary inputs. Update kernel and release metadata, adapt
removed package and Home Assistant options, and keep Determinate Nix
on its tested nixpkgs revision to avoid duplicate Boost patches.
Retire Sharry and its public endpoint because copyparty replaces it.
Document the GitHub mirror gate and require real devshell and system
builds in the upgrade validation workflow.
Statically-addressed home servers on hi run no DHCP, so they learned a
resolver only from the v6 RA RDNSS and lost DNS whenever v6 (and thus
the RA) was absent. Factor the fix castle/palace applied inline into a
shared lib.my.c.home.vlanDns helper that points resolved at the VLAN's
VRRP VIPs (always-present static v4, plus v6 when up) and sets the
advertised search domains, then apply it to every statically-addressed
hi client: castle, palace, cellar, sfh and the sfh hass/unifi
containers. Document it under the router client DNS section.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>