Home › Knowledgebase › KB-366

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.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

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:

Gather Your Information

For each VLAN you plan to create, write down:

If you are unsure which VLAN IDs to use, start with IDs in the 10–100 range. Many networking professionals reserve IDs 1 for management, 10 for staff, 20 for voice, 30 for guest Wi-Fi, and 40 for IoT devices.

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:

  1. Log in to your router's admin interface (typically http://192.168.1.1 or http://192.168.0.1).
  2. Navigate to LAN > VLAN or Network > VLAN Settings.
  3. Create VLAN ID 30 named "Guest" with subnet 192.168.30.0/24.
  4. Assign your guest Wi-Fi SSID to VLAN 30.
  5. Save and apply the configuration.
  6. 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.

Incorrect VLAN changes can lock you out of your router. Always keep a backup and, if possible, perform the configuration during a maintenance window when you have local console access.

Step 2: Log In to the Router

  1. Connect your computer directly to the router with an Ethernet cable where possible.
  2. Open a browser and enter the router's management address (commonly 192.168.1.1, 192.168.0.1, or 10.0.0.1).
  3. 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

  1. 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).
  2. Click Add New VLAN or Create.
  3. Enter the VLAN ID, Name, and assign a Subnet with its gateway address.
  4. Repeat for each VLAN you planned.
  5. Click Save after each entry.

Step 3b: Configure DHCP for Each VLAN

  1. Navigate to DHCP > DHCP Server or Network > DHCP.
  2. Enable a separate DHCP pool for each new VLAN subnet.
  3. Set the lease range and default gateway to match the VLAN's subnet (e.g., 192.168.30.10 to 192.168.30.254 for VLAN 30).
  4. Save the DHCP configuration.
Without a DHCP pool for a VLAN, devices connected to that VLAN will not receive an IP address automatically and will lose network connectivity.

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.

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.

  1. Go to Firewall > Rules or Routing > Inter-VLAN Routing (e.g., Firewall > Traffic Rules on Ubiquiti UniFi, IP > Firewall on MikroTik).
  2. Add a rule permitting traffic from the source VLAN to the destination VLAN.
  3. Explicitly deny traffic from the guest VLAN to all internal VLANs.
  4. Save and apply.
A common mistake is allowing "any to any" between VLANs. Always use the principle of least privilege: only allow the specific traffic required, and deny everything else.

Step 6: Save and Apply

  1. Review all your changes carefully.
  2. Click Save and then Apply or Commit. Some routers reboot automatically; others apply changes live.
  3. 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

  1. On your router, set the uplink port to your managed switch as a tagged or trunk member for all relevant VLAN IDs.
  2. On the managed switch, configure the corresponding uplink port as a trunk port and tag the same VLAN IDs.
  3. Set downstream ports connected to access points or end devices as untagged access ports for their assigned VLAN ID.
  4. Ensure the native VLAN (usually VLAN 1) is consistent across all trunk links to avoid VLAN hopping or mismatched tagging.
If you connect an access point to a trunk port but do not tag the SSID-to-VLAN mapping correctly, wireless clients may fail to connect or may be placed in the wrong VLAN.

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

  1. 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".
  2. Run tracert 192.168.10.10 on Windows or traceroute 192.168.10.10 on macOS/Linux. The trace should not complete successfully to the staff VLAN.
  3. 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

No Internet Access on a Specific VLAN

Cannot Access Shared Printer or Server Across VLANs

VoIP Quality Issues on the Voice VLAN

VLAN Tagging Mismatches on Trunk Links

If you continue to experience issues after working through these steps, Open a Ticket with our support team for further assistance.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket