Post
The VLAN weekend
The servers stay on VLAN 10, and phones, laptops and the TV moved to VLAN 20. From there only Jellyfin and DNS are reachable.
2 min
Shares the house and runs its network: the router, the switch, the Wi-Fi and the Pi that answers DNS. Writes the entries about the parts with cables.
Post
The servers stay on VLAN 10, and phones, laptops and the TV moved to VLAN 20. From there only Jellyfin and DNS are reachable.
2 min
TIL
ip -br a prints one line per interface: name, state and addresses. On a Proxmox node with a bridge and a tap device per guest, plain ip a fills three screens.
$ ip -br a
lo UNKNOWN 127.0.0.1/8 ::1/128
enp1s0 UP
vmbr0 UP 10.0.10.11/24
tap101i0 UNKNOWN
fwbr101i0 UPip -c -br a adds colour, so a DOWN stands out in red.
Incident
A power cut of three seconds rebooted the Pi that answers DNS, and its SD card came back read-only. Every device in the house depended on it.
Resolved
Critical
Nothing in the house could resolve a name for 98 minutes on Saturday evening. A power cut of about three seconds rebooted We put the rack on a UPS at the end of August and forgot the Pi, which hangs on the wall beside it with its own power supply. One DNS server was fine for as long as it never rebooted at a bad moment, and an SD card makes every reboot a bad moment.pi-dns, the only machine in the loft that is not on the UPS, and its SD card came back read-only. Unbound could not start, and the router handed out pi-dns as the only DNS server.Timeline
pi-dns reboots.ping 9.9.9.9 works, so the line is fine.pi-dns fails to start. The root file system is mounted read-only after errors on the SD card.What went wrong
What changed
pi-dns is on the UPS.pi-dns first and the router second.
Post
DNS for the house moved off the cluster onto a Raspberry Pi with Unbound. An update in the rack no longer takes the internet away from everyone downstairs.
1 min