How to separate customer traffic from network management traffic
Purpose: Prevent subscribers or guest users from discovering, pinging, or attempting logins against routers, switches, sector APs, and CPE radios.
Prerequisites
- 802.1Q VLAN-capable core router, switches, and wireless radios.
Step-by-Step Configuration
Configure every switch, backhaul radio, sector AP, and CPE to obtain its management IP strictly on tagged VLAN 10 (e.g., 10.10.99.0/24).
Carry subscriber PPPoE/DHCP traffic on dedicated customer VLANs (e.g., VLAN 200) and untag only the customer VLAN on the CPE Ethernet handoff port.
Drop all Layer-3 traffic from Customer/Guest subnets to 10.10.99.0/24 on the MikroTik forward chain, allowing management access only via encrypted admin VPN.
Running an IP scan from a customer router shows zero ISP routers, radios, or switches, while NOC engineers manage every device directly over VPN.
Troubleshooting Matrix
Combine Management VLAN isolation with SNMPv3 / restricted IP allowlists and HTTPS-only web GUIs.
Document Management VLAN IDs and subnet allocations across every POP.
Manages daily NOC telemetry, subscriber ticket queues, and on-site client turn-ups across corporate and residential estates in Nairobi.