How to set up VLANs on your business router to separate traffic and improve network security
Summary
This guide helps you troubleshoot and resolve: How to set up VLANs on your business router to separate traffic and improve network security. Follow the steps below to fix the issue.
Common Causes
Setting up Virtual Local Area Networks (VLANs) on your business router is one of the most effective ways to segment your office network, isolate sensitive devices like point-of-sale (POS) terminals or security cameras, and provide a separate network for guest Wi-Fi users. By dividing a single physical network into logical segments, VLANs reduce broadcast traffic, limit lateral movement by potential intruders, and make your network easier to manage. This guide walks you through planning, configuring, and verifying VLANs on a typical business-grade router.
Before You Begin
VLANs work by tagging network traffic with an identifier (a VLAN ID) so that devices in one VLAN cannot directly communicate with devices in another VLAN without a router or firewall permitting it. Before you start configuring, take some time to plan your network segments.
Identify Your Network Segments
Common VLAN groupings for small businesses include:
- Staff/Office VLAN — for workstations, printers, and shared resources
- POS or Payment VLAN — for eftpos terminals and POS systems, often with stricter firewall rules
- Security/IoT VLAN — for CCTV cameras, access control, and other smart devices
- Guest Wi-Fi VLAN — for visitors, isolated from your internal network
- Voice VLAN — for VoIP handsets, to prioritise call quality
Gather Your Information
For each VLAN you plan to create, write down:
- A VLAN ID (a number between 1 and 4094, excluding 1 which is usually the default)
- A name for the VLAN (e.g., "POS", "GuestWiFi")
- A unique subnet (e.g.,
192.168.10.0/24,192.168.20.0/24) - The gateway address (usually the first usable address, e.g.,
192.168.10.1) - Which physical ports or SSIDs will be assigned to each VLAN
Quick Fix: A Minimal Two-VLAN Setup
If you just need a quick separation between your office network and a guest Wi-Fi network, this condensed process will get you there:
- Log in to your router's admin interface (typically
http://192.168.1.1orhttp://192.168.0.1). - Navigate to LAN > VLAN or Network > VLAN Settings.
- Create VLAN ID 30 named "Guest" with subnet
192.168.30.0/24. - Assign your guest Wi-Fi SSID to VLAN 30.
- Save and apply the configuration.
- Enable the guest network firewall rule that blocks access to other VLANs.
Detailed Instructions: Configuring VLANs Step by Step
The exact menu names vary between router brands (DrayTek, Ubiquiti UniFi, TP-Link Omada, MikroTik, Cisco Meraki, and so on), but the underlying process is the same. The steps below use generic terminology that maps to most business router interfaces.
Step 1: Back Up Your Current Configuration
Before making any changes, save a backup of your router's current configuration. Look under System Tools > Backup & Restore or Administration > Config Backup. Store this file somewhere safe in case you need to roll back.
Step 2: Log In to the Router
- Connect your computer directly to the router with an Ethernet cable where possible.
- Open a browser and enter the router's management address (commonly
192.168.1.1,192.168.0.1, or10.0.0.1). - Enter your admin username and password. If you do not know these, check the label on the router or your original setup documentation.
Step 3: Create the VLANs
- Navigate to the VLAN section. This is usually under LAN, Switching, or Network (e.g., LAN > VLAN on DrayTek, Network > VLAN on TP-Link Omada).
- Click Add New VLAN or Create.
- Enter the VLAN ID, Name, and assign a Subnet with its gateway address.
- Repeat for each VLAN you planned.
- Click Save after each entry.
Step 3b: Configure DHCP for Each VLAN
- Navigate to DHCP > DHCP Server or Network > DHCP.
- Enable a separate DHCP pool for each new VLAN subnet.
- Set the lease range and default gateway to match the VLAN's subnet (e.g.,
192.168.30.10to192.168.30.254for VLAN 30). - Save the DHCP configuration.
Step 4: Assign Ports and SSIDs to VLANs
Once your VLANs exist, you need to tell the router which physical ports and wireless networks belong to each one.
- Wired ports: In the VLAN settings, edit each port and set its PVID (Port VLAN ID) and untagged membership. For example, set LAN Port 4 to PVID 20 for your POS devices.
- Wi-Fi SSIDs: In the wireless settings, edit each SSID and look for VLAN ID or Wireless VLAN. Assign your guest SSID to VLAN 30, your staff SSID to VLAN 10, and so on.
Step 5: Configure Inter-VLAN Routing (If Needed)
By default, VLANs cannot talk to each other. If you want certain VLANs to reach others (for example, staff needing access to a shared printer on the IoT VLAN), you need to enable inter-VLAN routing and create firewall rules.
- Go to Firewall > Rules or Routing > Inter-VLAN Routing (e.g., Firewall > Traffic Rules on Ubiquiti UniFi, IP > Firewall on MikroTik).
- Add a rule permitting traffic from the source VLAN to the destination VLAN.
- Explicitly deny traffic from the guest VLAN to all internal VLANs.
- Save and apply.
Step 6: Save and Apply
- Review all your changes carefully.
- Click Save and then Apply or Commit. Some routers reboot automatically; others apply changes live.
- Wait for the router to finish applying changes before testing.
802.1Q Trunking and Managed Switch Considerations
If your network uses managed switches between your router and access points, standard VLAN configuration on the router alone is not enough. You must configure 802.1Q trunking to carry tagged VLAN traffic across multiple switches.
Understanding Trunk Ports
A trunk port carries traffic for multiple VLANs simultaneously using 802.1Q tags. An access port carries traffic for only one VLAN and strips the tag before sending traffic to the end device.
Configuring a Trunk Link
- On your router, set the uplink port to your managed switch as a tagged or trunk member for all relevant VLAN IDs.
- On the managed switch, configure the corresponding uplink port as a trunk port and tag the same VLAN IDs.
- Set downstream ports connected to access points or end devices as untagged access ports for their assigned VLAN ID.
- Ensure the native VLAN (usually VLAN 1) is consistent across all trunk links to avoid VLAN hopping or mismatched tagging.
Verifying Your VLANs Are Working
After configuration, confirm that traffic is being separated correctly.
Check Device IP Addresses
Connect a device to each VLAN (via the appropriate port or SSID) and verify it receives an IP address from the correct subnet. On Windows, run ipconfig in Command Prompt. On macOS, run ifconfig in Terminal. On Linux, run ip a.
Test Isolation
From a device on the guest VLAN, try to ping or access a device on the staff VLAN. The request should fail. From the staff VLAN, confirm you can still reach the internet and any shared resources you intended to allow.
Test Inter-VLAN Blocking with ping and traceroute
- From a command prompt on a device in the guest VLAN, run
ping 192.168.10.10(replace with an address on the staff VLAN). The ping should time out or show "Destination host unreachable". - Run
tracert 192.168.10.10on Windows ortraceroute 192.168.10.10on macOS/Linux. The trace should not complete successfully to the staff VLAN. - Repeat from the staff VLAN to the guest VLAN to confirm bidirectional blocking where required.
Review the Router Logs
Check System Logs or Firewall Logs to see whether traffic is being routed and blocked as expected.
Troubleshooting
Devices Cannot Get an IP Address
- Confirm DHCP is enabled for the relevant VLAN.
- Check that the VLAN is assigned to the correct port or SSID.
- Verify the device is set to obtain an IP automatically (DHCP).
- Confirm the DHCP pool range covers the subnet you assigned to the VLAN.
No Internet Access on a Specific VLAN
- Verify the VLAN has a gateway address configured on the router.
- Check that a firewall rule allows traffic from that VLAN to the WAN interface.
- Ensure NAT or masquerading is enabled for the VLAN subnet so outbound traffic is translated correctly.
- Confirm the VLAN's DHCP pool is handing out the correct DNS server addresses.
Cannot Access Shared Printer or Server Across VLANs
- Check that an inter-VLAN firewall rule permits traffic from the source VLAN to the printer or server VLAN.
- Confirm the destination device allows inbound connections from other subnets (check its local firewall settings).
- Verify you are using the IP address rather than a computer name, as NetBIOS or mDNS discovery often does not cross VLAN boundaries without a relay.
VoIP Quality Issues on the Voice VLAN
- Ensure the Voice VLAN is tagged correctly on the switch port connected to the VoIP handset.
- Check that QoS or traffic prioritisation rules are applied to the Voice VLAN subnet.
- Verify that inter-VLAN rules are not throttling or dropping SIP or RTP traffic between the Voice VLAN and your PBX or VoIP provider.
VLAN Tagging Mismatches on Trunk Links
- Confirm the trunk port on the router and the managed switch are tagging the exact same VLAN IDs.
- Check that the native VLAN matches on both ends of the trunk link.
- Look for CRC errors or dropped packets on the trunk port, which often indicate an 802.1Q mismatch.
If you continue to experience issues after working through these steps, Open a Ticket with our support team for further assistance.
Still Having Issues?
💻 Open a Ticket