doc: FTTH migration — gateway is now 192.168.0.1

The Archer C7 at .2 is gone; the FTTH box at .1 is the gateway. Every
static holdout (nas host, nuc host, privoxy, transmission-bt) pointed at
the dead .2 and had no internet — the reported symptom was privoxy.

Also record two things the migration broke that were not obvious:

- DHCP reservations did not carry over. blocky held .254 by reservation
  on the C7; a lease renew on the FTTH box moved it and took LAN DNS
  down. It is static now. jellyfin-* are still DHCP on stale leases.
- The FTTH box advertises native IPv6. transmission-bt's tunnel is
  AllowedIPs = 0.0.0.0/0, so v6 egressed around the kill switch on the
  home address. IPv6 is now disabled in that container.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Julien Lutran
2026-09-16 10:08:42 +02:00
co-authored by Claude Opus 5
parent a5f63c7095
commit a7f1ac691e
4 changed files with 36 additions and 17 deletions
+28 -9
View File
@@ -12,7 +12,7 @@ How to rebuild the Incus host from scratch if `/dev/sda` (512 GB SSD,
`usb4t/media``/srv/media` (media library)
- USB: Pioneer USB audio (`08e4:0176`), Logitech Unifying receiver (K400),
CSCTEK USB Audio and HID
- NIC: `enp1s0` (static `192.168.0.3/24`, gw `192.168.0.2`)
- NIC: `enp1s0` (static `192.168.0.3/24`, gw `192.168.0.1`)
## ⚠️ What dies with sda
@@ -87,7 +87,7 @@ allow-hotplug enp1s0
iface enp1s0 inet static
address 192.168.0.3
netmask 255.255.255.0
gateway 192.168.0.2
gateway 192.168.0.1
dns-nameservers 1.1.1.1 9.9.9.9
```
@@ -165,13 +165,32 @@ hosts reach them normally. (So test a container's LAN service from inside
the container or from an external LAN host — never by pinging its IP from
the nuc or a sibling container; that always fails by design.)
LAN gateway note: the router/gateway is **`192.168.0.2`** (migrated from
`192.168.0.1`, 2026-08 `.1` is gone). DHCP-configured instances pick the
new gateway up automatically; **statically-configured ones must be updated
by hand.** Current static holdouts: privoxy
(`/etc/systemd/network/eth0.network`, `Gateway=`) and transmission-bt
(netplan `routes: via:` + the WG kill-switch `/32`). Symptom of a missed
one: the service is up and its port answers, but nothing it fetches works.
LAN gateway note: the router/gateway is **`192.168.0.1`** — the FTTH box,
since 2026-09 (it was `.2`, the Archer C7, from 2026-08; and `.1` before
that). **Every statically-configured host and instance must be updated by
hand**, and DHCP ones need a lease renew before they stop using the cached
old gateway. Symptom of a missed one: the service is up and its port
answers, but nothing it fetches works.
Static holdouts to update on any gateway change — the full list, verified
2026-09-16:
| Where | What to change |
|---|---|
| nas host | `/etc/network/interfaces`, `gateway` |
| nuc host | `/etc/network/interfaces`, `gateway` |
| blocky | `/etc/systemd/network/eth0.network`, `Gateway=` (static since 2026-09, see below) |
| privoxy | `/etc/systemd/network/eth0.network`, `Gateway=` |
| transmission-bt | netplan `routes: via:` (the WG kill-switch `/32`) |
| jellyfin-server/-client | DHCP — renew the lease, or they keep the old gateway |
⚠️ **DHCP reservations did not survive the FTTH migration.** blocky held
`192.168.0.254` via a reservation on the Archer C7; renewing its lease on
the FTTH box handed it a random address and took LAN DNS down with it. It
is now **statically configured** so it cannot move. `jellyfin-server`
(`.5`) and `jellyfin-client` (`.6`) are still DHCP with stale leases — set
reservations on the FTTH box or make them static before those leases
expire.
Let `julien` run harmless incus commands (list/info/config/show…)
without a password — mutating ones (`exec`, `start/stop`, `delete`)