How to Create a Virtual LAN in your Ubiquiti Unifi Network
A Virtual LAN is a private network that runs on the same physical network as your other computers, but is separate and protected.How-To
You don’t want your work data to get mixed in with your personal media. A Virtual Local Area Network (VLAN) can make sure the two never meet, while they both run on the same piece of wire or Wi-Fi network. It’s like a network within a network, all controlled by your router. Here’s how to create a VLAN on your Unifi network.
I test a lot of computer products, and I have a separate VLAN for new devices that are being tested: that’s what I have created in this example. This VLAN lets them talk to each other and provides basic Internet access, but they can’t access my personal devices.
Why Would You Need a VLAN?
Imagine that you are working from home, and you have a work-issued laptop. You connect that to your Wi-Fi, but now your work laptop can now see everything happening on your home network. Or perhaps you want the kids to be disconnected from the Internet after 10pm, while you are still free to browse. Or you just like to be organized: all of these are good reasons to create a VLAN and keep things separate and tidy.
One thing to note: a VLAN is not the same as a Virtual Private Network (VPN), which protects your web browsing from casual snoopers on the Internet. The VLAN separates your local network, but It doesn’t encrypt or hide your browsing or other Internet traffic.
How To Create a VLAN
There are three steps to the process: create the VLAN, set the rules on what it can (and can’t) do, and finally assign who gets put into the VLAN. For Ubiquiti networks, each of these is done in the UniFi web interface, which they call the control plane. Log into this at the address you used when you set up your home network.
First, we create the VLAN itself. In the UniFi network interface, go to Settings>Networks. This shows you the details of all of the Wi-Fi, VLAN and other networks. To create a new VLAN, click on Create New and give it a name. I called mine TEST because that’s what it is for.

I selected the following options:
- Zone: Internal. This makes it an internal network, not a Hotspot guest network or a DMZ, a network for servers accessible from the Internet.
- Manual Settings: I want to tweak the rest of the options a bit, so I selected the manual option.
- Isolate Network: On. This is the critical bit: this means the VLAN is isolated from all the others, so it can’t poke around the network.
- Access Internet: On. I want the devices I am testing to be able to access the Interwebs.
I left all of the other options on the default settings.
Once I click create, the network is born. Now, I can connect a new Wi-Fi network to that VLAN. Click on Wi-Fi, then click on create new. Because I lacked imagination, I called the WI-Fi network TESTING. I gave it a nice long password, and assigned it to the TEST VLAN from the drop-down menu for Network. I left all of the other options on default, but you can do all sorts of clever stuff if you want, like limit how much bandwidth the VLAN devices can use, restrict them to certain frequency bands or use a different level of Wi-Fi security. Click create and I’ve added a new Wi-Fi network to test devices on.

I don’t just test Wi-Fi devices, though: I also test desktop computers that use wired ethernet. So, I also set up a port on my router for them. To do this, I selected Ports from the left menu, then selected my router (called Sid) from the drop-down menu. I picked a port (#6 in this example), clicked on it and then selected the TEST VLAN from the network drop-down.
And that is it! Once this is all done, any device that connects to the TESTING Wi-Fi network or is plugged into port #6 on my router will be connected to the TEST VLAN.
That’s really just the beginning, though. If I wanted to, I could configure this VLAN to restrict the amount of data it can send or receive from the Internet, simulating a slower Internet connection. I can also block the Internet completely, restrict it to certain times, or block some apps from connecting.
How Do You Make Sure The VLAN is Working?
Once you have created the VLAN, how do you make sure that it is working? The easiest way is to connect a device to it, then run an app such as Fing or Net Analyzer that scans the network. If it is working, this will show that there are no other devices on the same network. If you try to access a device like a security camera or home media server, you should get no response. That’s because the router is spotting these requests and blocking them.
In my example, I created a separate Wi-Fi network for the VLAN, but you don’t have to do that. Instead, you can set the VLAN up so that selected devices are automatically connected to the VLAN whenever they connect. They use the same Wi-Fi network, but they are partitioned into the VLAN once they connect.
VLANs are an incredibly flexible tool that can be wielded like a scalpel to block certain things, or like a hammer to squish a device that’s overstepping what you are comfortable with.
More from MC News
- Run AI Locally: The Best LLMs for 8GB, 16GB, 32GB Memory and Beyond
- How to Use Local AI With Your Own Files: A Beginner's Guide to RAG
- Reading vs. Answering: The Two Hardware Bottlenecks Behind Local AI Performance
- How to Use a Local LLM in Visual Studio Code
- Hands-On with the AMD Ryzen AI Halo
- Quantization Explained: Why the Same LLM Gives Better Results on High-End Hardware
- Why Context Length, Not AI Model Size, Is Your Biggest VRAM Problem
- How to Use LM Studio to turn your PC into an AI Server
- Why VRAM and Memory Bandwidth are Key for Powering Local AI
- Keyboard 101: Intro to Computer Keyboards
- Fix It Yourself: Talking to iFixit on Why Repairable Tech Matters
- The Local LLM Your Laptop's Been Waiting For
- Gemma vs Qwen: Which Local AI is Best?
Richard Baguley is a seasoned technology journalist and editor passionate about unraveling the complexities of the digital world. With over three decades of experience, he has established himself as a leading authority on consumer electronics, emerging technologies, and the intersection of tech and society. Richard has contributed to numerous prestigious publications, including PC World, Wired, CNET, T3, Fast Company and many others.
