Skip to content

Network Overview ​

The UDM-SE is the gateway for my home and homelab. UniFi Network manages routing, DHCP, firewall policies, and the wireless networks broadcast by the U7 Pro Max access point. Separate VLANs group devices by their role, keeping everyday devices, IoT, guests, printers, servers, and management interfaces on distinct networks.

For the physical equipment, connections, and rack photo, see Networking Hardware.

Networks ​

Each network uses a /24 IPv4 subnet, with the UDM-SE at .1 as its gateway. The UDM-SE runs the DHCP server for all seven networks.

Addressing convention

I've chosen 10.120 as the common prefix for all of my local subnets. The third octet matches the VLAN ID, giving each network the pattern 10.120.<VLAN ID>.0/24. For example, Home Lab uses VLAN 40 and subnet 10.120.40.0/24, with 10.120.40.1 as its gateway. This keeps addresses consistent and makes it easy to identify which network a device belongs to.

NetworkVLANSubnetGatewayRole
Default110.120.1.0/2410.120.1.1Unused default LAN; internet access disabled.
Primary510.120.5.0/2410.120.5.1Everyday trusted devices and the Tailscale subnet router.
IoT1010.120.10.0/2410.120.10.1Smart-home and other connected devices.
Guests2010.120.20.0/2410.120.20.1Visitor devices.
Printers3010.120.30.0/2410.120.30.1Network printers.
Home Lab4010.120.40.0/2410.120.40.1Servers, virtual machines, containers, and NAS storage.
Management5010.120.50.0/2410.120.50.1Infrastructure management, including the AP, UPS, and PDU.

Default network is not intended for use

The Default network (VLAN 1) is not intended for client devices or homelab services. All internet access from this network is disabled. Assign devices to the appropriate network above instead.

VLANs separate broadcast domains. Access between networks is controlled by firewall policies on the UDM-SE; a network's role does not imply unrestricted access to another VLAN.

SSIDs ​

All four wireless networks are assigned to all APs. Each SSID maps to a single VLAN, so wireless clients join the same routed network as wired devices assigned to that VLAN.

SSIDRadio bandsSecurity
StackTrace ⚡2.4, 5, and 6 GHzWPA3
Facade2.4 and 5 GHzWPA2/WPA3
sudo askForWifi()2.4, 5, and 6 GHzWPA3
Spooler2.4 GHzWPA2/WPA3

Captive Portal ​

The guest SSID, sudo askForWifi(), uses a captive portal. After connecting to the wireless network, guests are directed to a welcome page where they accept the terms before receiving internet access. WPA3 secures the wireless connection, while the portal handles guest authorization. Guest devices remain on the Guests network (VLAN 20), with access to other local networks controlled by the UDM-SE's firewall policies.

Guest and IoT Isolation ​

Guests and IoT devices have different access needs, so I keep them in separate VLANs and firewall zones. Primary, Home Lab, and Management belong to the Trusted zone, IoT and Printers belong to Unsecure, and Guests belongs to Hotspot. The UDM-SE controls connections between these zones, with explicit exceptions for shared services.

Guests: The guest network provides internet access after captive portal authorization, while restricting access to other local networks. Exceptions allow guests to reach the captive portal and the designated Canon printer on its permitted printing ports. Completing the portal does not grant general access to trusted devices or homelab services. The guest SSID also has Client Device Isolation enabled to prevent direct communication between wireless guest clients through the AP. This wireless setting does not provide isolation between wired guest devices.

IoT: Smart-home and media devices can reach the internet, but cannot freely initiate connections into the Trusted zone. Exceptions allow DNS queries to Pi-hole, selected Jellyfin clients to reach the media server and reverse proxy, and designated trusted IoT clients to access NAS shares over SMB. Primary devices can initiate connections to the Unsecure zone, with return traffic allowed, so trusted devices can control IoT equipment without giving that equipment unrestricted access back into Primary.

IoT access to gateway administration over HTTP, HTTPS, and SSH is blocked. Separate DNS rules block other DNS destinations on port 53 and DNS-over-TLS on port 853 across routed paths; these port rules do not cover DNS-over-HTTPS. Unlike the guest SSID, Facade has wireless client isolation disabled, allowing devices on the IoT subnet to communicate locally. Traffic within the same subnet does not pass through the gateway's inter-VLAN firewall.

SSID to Network Diagram ​

StackTrace ⚡
→
PrimaryVLAN 5
Facade
→
IoTVLAN 10
sudo askForWifi()
→
GuestsVLAN 20
Spooler
→
PrintersVLAN 30
U7 Pro Max · Wireless access   /   UDM-SE · Routing and firewall

The arrows show network membership. Traffic between VLANs passes through the UDM-SE and its firewall policies. Default, Home Lab, and Management have no dedicated SSID in this configuration; the access point itself is managed on Management VLAN 50.

See DNS Resolution for DHCP resolver settings, service records, and troubleshooting.

Core Network Services ​

ServiceSystemRole
Routing and DHCPUDM-SEProvides each network's gateway, address leases, reservations, and inter-VLAN firewall policies.
DNSPi-hole · 10.120.40.103Provides local DNS and DNS filtering. UniFi's DNS Servers network list points to this host.
Reverse proxyNginx Proxy Manager · 10.120.40.101Routes application hostnames to homelab services and handles HTTPS.
Remote accessTailscale · 10.120.5.9Provides a subnet router and optional exit node for remote devices.

Server addresses use static host configuration and UniFi reservations. See Servers for the hosts and guests, and Services for the applications they run.

How Everything Connects ​

The internet connection enters the UDM-SE through WAN1. Its built-in switch connects the access point and rack equipment, and a 10 Gb SFP+ direct attach cable links the NAS to the gateway. Wireless clients join their SSID's VLAN through the access point, while wired devices use the network assigned to their switch port or virtual interface.

Home Lab VLAN 40 contains the Proxmox host, media server, NAS, and most infrastructure services. Management VLAN 50 keeps equipment management interfaces separate from those workloads. DNS, remote access, and other services that cross VLAN boundaries depend on the gateway and the relevant firewall rules remaining available.

Docker-only media network ​

The media server reserves 10.120.6.0/24 for its Servarr Docker bridge. This is separate from the UniFi VLANs above; it is not a LAN/VLAN allocation or a Tailscale-advertised subnet. Keep the range free of other LAN, VPN, and Docker networks. Clients access media services through the host's published ports or Nginx Proxy Manager, while containers use service names on their shared bridge.