
What is a VLAN, and how to keep guests, tills, cameras and printers apart
A VLAN splits one physical network into separate networks: the guest on the Wi-Fi no longer sees your server, and the camera only talks to its recorder. Separating is the easy part. Whether it achieves anything depends on the rules between those VLANs and the order in which you move over, and that is what this piece is about.
A VLAN separates devices on the same network into groups that cannot see each other. An office rarely needs more than six to eight, and splitting by department is usually the wrong choice.
The security is not in the VLAN itself but in the rules between VLANs. If everything is allowed there, all you have done is make the network more complicated.
What breaks first after separating is printers, wireless presenting and DHCP. Take an inventory first, move one group at a time and tighten the rules afterwards.
What is a VLAN, and what it is not
A VLAN (virtual LAN) is a separate network running on the same switches and the same cabling. Devices in VLAN 20 cannot see devices in VLAN 30, even when they are plugged into the same switch. Technically this is done with a label on every network frame, the 802.1Q tag, which says which VLAN it belongs to.
You will meet two terms as soon as you configure one:
- Access port (untagged). A port that belongs to exactly one VLAN. You plug a PC, printer or camera into it; the device knows nothing about the VLAN.
- Trunk port (tagged). A port that carries several VLANs at once, with labels. You use it between switches, to an access point and to the firewall.
What a VLAN is not is a firewall. It separates traffic, but as soon as a router or firewall between the VLANs lets everything through, the separation is gone. In practice each VLAN is also its own IP subnet, and traffic between subnets passes a device that routes. That device is where you decide what is allowed.
A VLAN layout for an ordinary office
The most common mistake is one VLAN per department. Sales and finance use the same applications and the same printers; splitting them produces rules without any benefit. Split by type of device and risk, not by org chart. A layout that fits most offices:
- Management. The admin interfaces of switches, access points and firewall. Only reachable from the IT team’s machines.
- Workstations. Staff laptops and PCs, wired and on the corporate Wi-Fi.
- Servers. Whatever still runs on site: file server, backup, an application server.
- Voice. Desk IP phones, so speech can be given priority.
- Printers and multifunction devices. Devices that are rarely updated and last for years.
- Cameras and access control. With the recorder, and with no route to the internet.
- Guests. Internet only, nothing else.
- Tills and card terminals, or building and IoT. Only if you have them: a shop needs the first, an office building with smart climate control or digital signage the second.
Agree a numbering scheme and stick to it. A common one makes the VLAN number equal to the third number of the subnet: VLAN 20 is 192.168.20.0/24, VLAN 30 is 192.168.30.0/24. It sounds like a detail, but an outage at three in the morning gets much shorter when everyone can tell from an IP address which VLAN it is in.
Traffic between VLANs: that is where the security is
For an SME office, the firewall usually routes between VLANs. A layer 3 switch can do it too, and faster, but with coarser rules and less logging. Where it happens matters less than having a decision for every pair of VLANs. Start from “nothing is allowed” and open what is needed:
- Workstations to printers: only the print ports, plus the web interface for IT, not everything.
- Printers to workstations or servers: only if scan to folder has to work, and then to that one server.
- Cameras: only to the recorder. No internet, not even “for updates”; remote viewing goes over the VPN, not through an open port.
- Guests: to the internet, nowhere else, and ideally not to each other either (client isolation).
- Tills and card terminals: only to the services they need, and nothing from other VLANs coming in.
- Management: reachable only from IT machines or the VPN.
Write those rules down as a table, VLAN against VLAN, with what is allowed in each cell and why. That table is your documentation, your check and your answer when an auditor or insurer asks how the network is segmented. Whether the rules currently in your firewall still match it is exactly the question a firewall review answers.
Wi-Fi and VLANs: one network name per VLAN, not per department
On the Wi-Fi you map each network name (SSID) to a VLAN: the corporate Wi-Fi to workstations, the guest Wi-Fi to guests. The access point sits on a trunk port and puts the traffic of each SSID into the right VLAN.
Keep the number of SSIDs small. Every network name sends its own beacons, and with five or six names a noticeable share of airtime goes on that instead of on users. Three is enough for most offices: corporate, guest and possibly one for devices that cannot do a corporate login.
If you want to go further, let the VLAN follow from who logs in rather than from the network name: one SSID, and through 802.1X and a RADIUS server an employee lands in the workstation VLAN and an administrator in the management VLAN. It is tidier, but it needs an identity integration that also has to be maintained. For an office of twenty people it is rarely the first step.
What breaks first after you separate
Almost every VLAN rollout produces the same tickets on Monday morning. All of them can be avoided if you know them:
- Printers and screens that disappear. Devices that announce themselves on the network (mDNS) only do so inside their own VLAN. A printer or presentation screen in another VLAN drops out of the list while it is working perfectly. The fix is an mDNS gateway on the firewall or controller, or adding the printer manually by IP address.
- No IP address. Every VLAN needs its own DHCP scope. If the DHCP server lives in the server VLAN, the gateway has to forward the requests (DHCP relay). Forget it and a whole VLAN gets no address.
- Phones in the wrong VLAN. IP phones should learn their voice VLAN from the switch (LLDP-MED) or from DHCP. If a PC is connected behind the phone, it stays untagged in the workstation VLAN. When that goes wrong, the phone works but the audio breaks up, or the PC drops off.
- Scan to folder. The multifunction device scans to a share on the server and that path is closed. It belongs in the rules table.
- Time. Cameras and recorders that can no longer reach their time server drift apart over a few weeks, and you only notice when you need the footage.
Rolling it out without stopping the office
Putting a VLAN layout on an existing network is mostly preparation. An order that works:
- Inventory. Which device is connected where, with which IP and MAC address. Without that list you do not know what you are moving.
- The layout and the rules table on paper. VLANs, subnets, DHCP scopes and who may talk to whom. Have someone who uses the network every day read it; they know the connection nobody ever wrote down.
- Create the VLANs and rules, loose at first and with logging. That shows which traffic really flows between groups before you close it.
- Move one group at a time, outside office hours. Guests and cameras first, as they affect the fewest people; workstations last. After each group, test a fixed list: print, scan, call, open a file, join the Wi-Fi.
- Tighten. After a week or two, put the logs next to the rules table and close what is not used.
Two hygiene rules belong with it straight away: do not put user traffic in VLAN 1, the default VLAN on every switch, and disable unused ports or put them in a VLAN that leads nowhere. Otherwise a spare network socket in the meeting room is an open door to whatever happens to be on the default.
Where it goes wrong
- VLANs without rules. Neatly separated, with an “allow all” rule between them because something did not work. This is the most common one, and you cannot see it from outside.
- Management reachable from guest Wi-Fi. The login page of the firewall or switch should not even load from the guest network.
- Every VLAN everywhere. Making every port a trunk with all VLANs on it is easy during setup and hard to defend afterwards. A trunk carries only the VLANs needed on the other side.
- A little unmanaged switch in between. A box under a desk knows nothing about VLAN tags. Everything behind it ends up in one VLAN, or does nothing at all.
- No documentation. The layout lives in the head of whoever built it. Record VLANs, subnets, port assignments and the rules table somewhere your successor will find them.
Where our work stops
What we do. We design the VLAN layout and the rules table, configure switches, access points and firewall, carry out the move one group at a time and manage the network afterwards, with the documentation in the client’s name. We lay the data cabling and mount the equipment.
What we do not do. We are not a payment service provider and do not process payments: the card terminal comes from the client’s own payment provider and sits under that contract; we make sure the network path to it stays separate and open. Nor are we a QSA. A dedicated till VLAN can reduce the part of the network that falls under PCI DSS, but which scope applies and which questionnaire you complete is settled with your payment provider or a qualified assessor; see our page on PCI DSS. And for cameras: we segment and manage the network, we do not sit in the monitoring centre.
Questions we get about this
The five that come up most often.
What is a VLAN?
A VLAN is a separate network on the same switches and cabling. Devices in one VLAN cannot see those in another, even on the same switch. It lets you keep guests, cameras and workstations apart on a single physical network.
What is the difference between a VLAN and a subnet?
A VLAN separates traffic on the switch; a subnet is a range of IP addresses. In practice each VLAN gets its own subnet, and traffic between them passes a router or firewall. That combination is what makes the separation useful.
Is a VLAN a security measure?
Only together with rules. The VLAN separates the groups, but the firewall or switch routing between them decides what still gets through. If everything is allowed there, the VLAN adds no security; start from allowing nothing and open only what is needed.
Do you need a managed switch for VLANs?
Yes. A switch has to read VLAN tags and assign a VLAN per port, and an unmanaged switch cannot do that. The access points and firewall also need VLAN support, which is standard on business equipment.
Do you also handle the card terminal and the PCI DSS scope?
No. The card terminal comes from your payment provider and sits under their contract, and we are not a QSA. We put the till and terminal in their own VLAN with an open path out. Which scope applies and which questionnaire you complete is settled with your payment provider or a qualified assessor.
Further reading
What a VLAN layout connects to.
Shall we lay out your network?
Send us what is connected to your network today. We will come back with a VLAN layout, a rules table and an order for moving over without stopping the office.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.