Setting up VLANs
Purpose: Segment Corporate Staff, Guest Wi-Fi, CCTV, and Network Management traffic onto isolated IEEE 802.1Q VLANs over a single trunk uplink.
Prerequisites
- Planned VLAN IDs (e.g., VLAN 10 Mgmt, VLAN 20 Staff, VLAN 30 Guest) and managed switch/AP support for 802.1Q tagging.
Step-by-Step Configuration
Under Interfaces -> VLAN, create vlan10-mgmt, vlan20-staff, and vlan30-guest attached to bridge-main.
Assign distinct IP subnets (10.10.10.1/24, 10.10.20.1/24, 10.10.30.1/24) and dedicated DHCP Servers to each VLAN interface.
Under Bridge -> VLANs, set Trunk ports (to switches/APs) as Tagged and Access ports as Untagged with matching PVID.
Enable WinBox Safe Mode first, then check VLAN Filtering on bridge-main and verify management connectivity.
CLI / Configuration Snippet
# RouterOS v7.x — Bridge VLAN Filtering Example (ether2 = Trunk, ether3 = Access VLAN 20) /interface vlan add interface=bridge-main name=vlan10-mgmt vlan-id=10 /interface vlan add interface=bridge-main name=vlan20-staff vlan-id=20 /interface bridge port add bridge=bridge-main interface=ether2 frame-types=admit-only-vlan-tagged /interface bridge port add bridge=bridge-main interface=ether3 pvid=20 frame-types=admit-only-untagged-and-priority-tagged /interface bridge vlan add bridge=bridge-main tagged=bridge-main,ether2 vlan-ids=10 /interface bridge vlan add bridge=bridge-main tagged=bridge-main,ether2 untagged=ether3 vlan-ids=20 /interface bridge set bridge-main vlan-filtering=yes
Devices on VLAN 20 and VLAN 30 receive separate subnet leases and trunk cleanly across ether2 to managed switches and UniFi/Cambium APs.
Troubleshooting Matrix
Add firewall forward-chain rules blocking inter-VLAN routing from Guest/CCTV VLANs into Staff and Management VLANs.
Keep a dedicated emergency non-VLAN management port (e.g., ether5) excluded from the bridge during complex VLAN deployments.
Manages daily NOC telemetry, subscriber ticket queues, and on-site client turn-ups across corporate and residential estates in Nairobi.