GeoIP Region Blocking on the UCG Fiber — and Why iptables Shows Nothing
Eleven countries blocked at the WAN, inbound and outbound. The interesting part isn't the list. It's that the kernel tools I trust for every other rule can't see this one.
Deep dives into home lab network architecture, firewall design, DNS hardening, and zero-trust implementation on real hardware.
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.
Eleven countries blocked at the WAN, inbound and outbound. The interesting part isn't the list. It's that the kernel tools I trust for every other rule can't see this one.
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.
Blocking the cameras' Chinese cloud endpoints felt like good hygiene. It quietly broke remote viewing and triggered a one-query-per-second retry storm. The real culprit turned out to be the DNS truncation bit.
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.
Remote desktop to the Pi went sluggish. The firewall rules were correct and verified in the kernel. The culprit was the IPS quietly dropping STUN and forcing every session onto a slow relay path.
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.
UniFi OS 5.1.11 has a silent bug: enabling logging on DEFAULT DROP rules corrupts the iptables chain. The UI shows rules intact. The kernel shows nothing. The only way to find it is SSH.
iCSee cameras relay through cloud infrastructure. Block the API handshake and cameras go dark. Port-based rules fail. Source-IP segmentation is the only approach that works.
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.
IoT devices hardcode DNS resolvers. DNAT redirect rules intercept all port 53, 853, and 123 traffic and redirect to the Pi, regardless of the destination the device specified.
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.
How I designed six isolated VLANs with DEFAULT DROP inter-zone policies on a UCG Fiber gateway, and why every IoT bulb lives in its own cage.
Tailscale on the Pi with subnet routing. Direct connections via port forward offer speed but violate zero-trust posture. Relay accepts higher latency for security alignment.
Running authoritative DNS for internal zones while forwarding upstream over an encrypted channel — and forcing every device on the network to use it.
A reference guide to UniFi's iptables chain naming convention and how to verify firewall rules actually exist in the kernel, not just in the UI.
Capturing camera traffic, identifying relay ports, and building firewall rules that let cameras work without giving them LAN access.
CyberSecure Enhanced with Memory Optimized mode blocks botnets and exploit attempts. Performance overhead is real but acceptable on UCG Fiber hardware.
Configuring a minimal WireGuard VPN that gives remote access to the MGMT VLAN without routing all traffic through the tunnel.
Assign the .2 address on each VLAN as a honeypot. Nothing legitimate should ever talk to it. Any traffic triggers an alert and surfaces compromised or misconfigured devices.
Real-time system metrics and service uptime monitoring on a Pi 5, with ntfy push alerts for critical events.
ntfy is a simple HTTP-based notification service. Every service failure, every ban, every backup failure routes through ntfy to your phone immediately.
Configuring Fail2Ban jails for Samba authentication failures on the Pi, with ntfy integration for ban notifications.
Need a network security consultation?
VLAN design, DNS hardening, IoT isolation, WireGuard setup