Back to Blog
Firewall 2 min read

Zero-Trust VLAN Microsegmentation on UniFi — A Practitioner's Guide

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.

Zero trust isn't a product. It's a posture. The core axiom is simple: no traffic is trusted by default, regardless of which segment it came from. Every flow must be explicitly permitted.

My network runs six VLANs — MGMT, Admin, IPTV, Users, Skynet (IoT), and Guest — each in its own UniFi zone. The gateway is a UCG Fiber running UniFi OS 5.1.11 with Network 10.4.57.

The DEFAULT DROP rule sits at the bottom of every inter-zone policy. Anything not explicitly whitelisted is silently dropped. No logging noise on well-known blocked ports — just silence.

Why Skynet Gets Its Own Zone#

IoT devices are adversarial by design. They phone home, they probe for open ports, they run unpatched firmware. Isolating them in the Skynet VLAN with no inter-VLAN routing access means a compromised Wyze camera can't pivot to anything meaningful.

The only outbound Skynet permits are DNS (redirected to the Pi) and HTTPS to the internet. No LAN access. No admin panel reachability from Skynet. Full stop.

The Config Migration Bug#

UniFi OS 5.1.11 has a silent config migration issue. Zone-based rules can appear correct in the UI but not be pushed to kernel iptables. I verify every rule change with a direct SSH session to check iptables -L output. Always verify the kernel, not the UI.