Home network segmentation: VLANs, guest networks, and isolating IoT
Most home networks are one big space where a hacked smart device can reach your laptop. This guide separates them, from a simple guest network to VLANs for IoT.

Home network segmentation: VLANs, guest networks, and isolating IoT
Most home networks are one big space where a hacked smart device can reach your laptop. This guide separates them, from a simple guest network to VLANs for IoT.
Who this guide is for: People with IoT devices, smart TVs, or frequent guests on the home network. You do not need to be a network expert to start — even a guest network is already a meaningful step.
Your home network is probably one big flat network: router → everything connected to it. Laptop, phone, smart TV, IP camera, smart bulbs, and your guest’s phone all share the same space. If one device is compromised, it can see and attack everything else.
Network segmentation fixes this by dividing devices into separate zones that can’t reach each other unless you allow it.
What you gain, and what it costs
You gain containment. A smart bulb, camera, or visitor on your Wi-Fi no longer automatically gets visibility into your laptop, NAS, or work environment. This is one of the few home-network measures that can genuinely limit the damage caused by a compromised device.
The cost is complexity. Devices that used to talk to each other automatically may stop working without extra rules. Printers, Chromecast, AirPlay, Sonos, and device-management interfaces are often exactly where that friction shows up.
When this is overkill
Full VLAN design is not the first step for every household. If your router offers a decent guest network and your main risk comes from guests and cheap IoT devices, start there. Deeper segmentation becomes worth it once you have many devices, work-from-home needs, NAS storage, or genuinely sensitive data on the same network.
The problem: one network for everything
Suppose your smart TV is compromised — through a vulnerable firmware update or a malicious app. On a flat network, that TV can:
- Scan your NAS and read anything not behind a password
- Try to intercept traffic from your laptop
- Attempt to log into your router
- Use your phone as an attack target
This sounds theoretical, but smart TVs, IP cameras, and other IoT devices often run outdated software without regular updates. They are the weakest links in your network.
The solutions: three options
Option 1: guest network (simplest)
A guest network is a separate Wi-Fi network alongside your main network. Devices on the guest network:
- Have internet access
- Should not be able to reach devices on the main network; how well this is done differs per router, so test it (see step 1 below for how)
- Cannot reach each other either (if client isolation is enabled)
When to use: smart TV, streaming sticks, IoT devices, visitors.
Limitation: guest networks are binary — you have one main network and one guest network. You cannot create multiple separate zones with different rules.
Setup: many routers support this. Look for Guest Network in your router settings.
Option 2: VLAN (more flexible)
VLAN stands for Virtual Local Area Network. It is a way to split one physical network into multiple logically separate networks, each with its own rules.
The difference from a guest network:
- A guest network is one fixed extra zone
- With VLANs you create as many zones as you want, each with its own access rules
Example home setup:
| VLAN | Devices | Internet access? | Access to other VLANs? |
|---|---|---|---|
| VLAN 10 — Home | Laptop, phone | Yes | No |
| VLAN 20 — IoT | Smart TV, bulbs, camera | Yes | No |
| VLAN 30 — Guests | Visitor phones | Yes | No |
| VLAN 40 — NAS | Storage, backup | No (optional) | VLAN 10 only |
Each VLAN has its own Wi-Fi name (SSID) or cable port. A VLAN separates traffic on the network itself, but traffic between VLANs goes through the router, so the router’s firewall decides whether VLAN 20 can reach VLAN 10. GL.iNet’s panel blocks that for you (below). On UniFi you switch on Network Isolation or set firewall rules; on OPNsense and pfSense you write the rules. The numbers in this table are only an example.
When to use: when you want more control than a guest network provides, or need multiple zones (work, IoT, guests, NAS).
Option 3: physically separate network (maximum isolation)
The TV or IoT device gets a completely separate router with its own internet connection. No shared hardware, no shared software layer. A second router behind your existing one is not this: see Block WAN Subnet below.
When to use: for devices you absolutely do not trust, or for high-risk users. Overkill for most home situations.
What do you need for VLANs?
Most standard ISP routers support home VLANs only partially or not at all; check yours. For real segmentation, you usually need a router that does:
| Router | VLAN support | Difficulty |
|---|---|---|
| GL.iNet (Beryl AX, Flint 2/3, Slate 7) | Yes, in the admin panel since firmware 4.10/4.11 | Low–Medium |
| OPNsense / pfSense | Full | Higher |
| Ubiquiti UniFi | Full | Medium–Higher |
| Standard ISP router | None or limited | — |
For most home users, a GL.iNet router is the practical choice: its own admin panel now handles VLANs, OpenWrt sits underneath for anything more, and the hardware is affordable. One caveat: the firmware we read builds on OpenWrt 21.02 (Beryl AX, 4.11.0) and 23.05 (Slate 7, 4.10.1), both End of Life according to OpenWrt. GL.iNet maintains its own firmware and publishes security advisories; we didn’t check which fixes it carries over, so keep the firmware up to date.
Setting up VLANs on GL.iNet
GL.iNet added native VLAN support to its own admin panel in firmware 4.10 (Wi-Fi 7 models such as Flint 3 and Slate 7) and 4.11 (Beryl AX, Flint 2), according to GL.iNet’s release notes. The steps below come from firmware 4.11.0 on the Beryl AX, compared with 4.10.1 on the Slate 7. On 4.10 the menu item LAN is called Subnet. Check your version under SYSTEM → Upgrade; models still on older firmware are covered at the end of this section.
The panel has three ready-made networks: Main Network (VLAN 1, 192.168.8.1), Guest Network (VLAN 9, 192.168.9.1) and IoT Network (VLAN 10, 192.168.10.1). Guest and IoT are switched off until you turn them on. Every network besides Main gets its own firewall zone: it gets DHCP and DNS from the router and internet access, nothing else. It can’t reach your main network or open the admin panel, and your main network can’t reach it; you don’t write firewall rules for that. Rules you added yourself under SECURITY → ACL can open this up again. Already using the router? Devices stay where they are until you connect them to the new network.
Step 1: an IoT Wi-Fi network (the quick route)
For smart TVs, bulbs and cameras on Wi-Fi this is usually all you need. It only protects devices on this router: a laptop still on your ISP router’s Wi-Fi or ports isn’t behind it.
- Go to WIRELESS and switch on the IoT Network Wi-Fi; give it its own name and set your own password, don’t keep what’s in the field. GL.iNet recommends the 2.4 GHz band for IoT devices, for compatibility.
- Under NETWORK → LAN, open IoT Network and set WAN Access Control to Block WAN Subnet. The default, Unrestricted, lets IoT devices reach the network your router itself hangs off, so everything on your ISP router if that’s where it’s connected. AP Isolation is already on here (IoT devices can’t see each other); leave it on unless they need to talk to each other.
- Test it: put your phone on the IoT Wi-Fi. The internet should work, but
192.168.8.1, your laptop’s or NAS’s address and your ISP router’s address shouldn’t open. Then go back to your main Wi-Fi: from the IoT network you can’t reach the admin panel.
The Guest Network works the same way for visitors, with the same defaults.
Casting and apps: a phone on Main can’t find a TV or speaker on IoT, because nothing passes discovery between networks. AirPlay wants both on the same Wi-Fi, Sonos the same subnet. Put the device you cast from on that network too (with AP Isolation off, which lets those devices reach each other again), or leave a TV or speaker you cast to on Main and accept that risk. Don’t open IoT towards Main for this.
Step 2: more zones, or zones on a cable
Want a separate zone for work or a wired device? Add your own network:
- Go to NETWORK → LAN → Add A New Network.
- Give it a Name, a free VLAN ID (9 to 4000; Guest and IoT already use 9 and 10) and a Gateway in its own subnet, e.g.
192.168.20.1. The DHCP server hands out addresses in that subnet. AP Isolation is off here unless you switch it on. - Under WAN Access Control, choose Block WAN Subnet (internet only, not the network your router itself hangs off) unless you have a reason not to. Unrestricted also allows that upstream network; Block Internet Access allows nothing outside, for a device that needs no internet.
A device on its own network can only be reached from that same network. A NAS there is out of reach for your laptop on Main, so keep a NAS on Main unless you want to work out the exceptions yourself (GL.iNet’s ACL page lists the zones LAN, Guest, IoT and WAN, not your own networks).
A network you add yourself has no Wi-Fi name of its own; Wi-Fi only offers Main, Guest and IoT. You connect it to devices by cable:
Lockout risk: do this from the main Wi-Fi or another port, not over the cable you are changing. Once your own port leaves Main you lose the admin panel, and we found no warning for it in the panel’s code. If that happens, join the main Wi-Fi and set the port back; otherwise use the reset button, which erases your settings.
- Go to NETWORK → Ethernet Port and pick the LAN port.
- Under VLAN, set Mode (4.10: VLAN Mode). Standard puts one network on the port, untagged (choose it under Native Network; 4.10: Access Network), for a single device such as a TV. Multiple VLANs sends several networks tagged over one cable (Allowed Tagged Networks), for a managed switch or an access point that understands VLANs; Native Network then handles untagged traffic, and Drop Untagged Packets cuts off a plain laptop on that port.
Older firmware
Below 4.10/4.11 the panel has no VLANs. From firmware 4.9 it has a separate IoT network (NETWORK → IoT Network, with its own subnet, AP Isolation and Block WAN Subnets, plus an IoT Wi-Fi under WIRELESS); before that only the guest network (GL.iNet docs: IoT Network). For more you build VLANs yourself in LuCI, the OpenWrt interface underneath: SYSTEM → Advanced Settings → Go To LuCI, then follow OpenWrt’s own VLAN tutorial. That is real network administration; if the guest network covers your devices, it is the better choice.
Practical device assignment for home use
Main network (trusted): Laptop, desktop, phone, tablet, NAS
Guest network / VLAN: Smart TV, streaming sticks, smart bulbs, IP camera, doorbell, games console, visitor phones (with an IoT network, as on GL.iNet: devices there, visitors on Guest)
Never on the same network as trusted devices:
- Smart TV (ACR, trackers) — see Smart TV privacy guide
- IP cameras (often poor firmware)
- Smart bulbs and plugs (many depend on the maker’s cloud platform to work and send it data)
- Games consoles (large attack surface, connect to external servers)
Summary
| Solution | Required hardware | Difficulty | Good for |
|---|---|---|---|
| Guest network | Any modern router | Low | Smart TV, IoT, guests |
| VLAN | Router with VLAN support (table above) | Medium | Multiple zones, more control |
| Physically separate network | Second router and second internet connection | Low–Medium | Maximum isolation |
Start with a guest network for IoT devices — that already tackles the biggest problem. VLANs are the next step when you want finer control.
Next step
Go further
- Setting up OPNsense VLAN segmentation — finer-grained zones beyond guest-network or GL.iNet level
- GL.iNet travel router setup — guest network and VPN on GL.iNet
- Privacy DNS guide — combine DNS filtering with network segmentation
- Tailscale mesh VPN guide — reach your home network safely without opening ports
Decide first
- Network profile guide — what level of protection actually suits your situation
Smart home
- Smart TV privacy: disable ACR — why your TV belongs on a separate network