Network Changelog: September–October 2026
Five weeks of work on the lab: closing the last DNS bypass routes, ending a camera retry storm for good, an A+ bufferbloat grade, and a full UI-vs-kernel firewall audit after two surprise config migrations.
Five weeks of work on the lab: closing the last DNS bypass routes, ending a camera retry storm for good, an A+ bufferbloat grade, and a full UI-vs-kernel firewall audit after two surprise config migrations.
I microsegmented everything on the network, then quietly ran a public Next.js app on the same kernel as the resolver every VLAN depends on. Here's the blast-radius problem — and why a second Pi only helps if it lands in the right zone.
An unused file share and a desktop GUI on a headless server are just attack surface with extra steps. How I stripped both off a live resolver without paging myself or dropping the network.
A Cloudflare Worker fails my self-hosted site over to a managed standby and back. It needs no KV namespace — the failure counter lives in the DNS record's comment field.
The instinct is to give gaming its own segment with its own speed limits. But latency isn't a bandwidth problem, and a new VLAN buys you firewall surface, not frames.
Locking down parked domains with SPF hard-fail and DMARC reject, wiring Cloudflare Bot Fight Mode and AI Labyrinth, adding Turnstile to the contact form, scrubbing internal network details from public pages, and upgrading to Next.js 15.
A completely isolated guest VLAN with captive portal + voucher authentication, per-device speed limits, and no fallback DNS — designed to be welcoming but not a liability.
Daily backups from the Pi to R2 via rclone, scheduled with systemd timers. Common pitfalls: /tmp sizing, scoped token permissions, and S3 ACL incompatibilities with R2.
Configuring Fail2Ban jails for Samba authentication failures on the Pi, with ntfy integration for ban notifications.