Omada SSID VLAN Troubleshooting: Check Gateway, Switch Profile and AP Together

Compatible adopted Omada gateway, switch and EAP; UI paths below are scoped to the cited controller documentation.

Applies to: Compatible adopted Omada gateway, switch and EAP; UI paths below are scoped to the cited controller documentation.

Build a path, not just an SSID

A client SSID with a VLAN tag still needs that VLAN carried through the switches to its gateway and DHCP service. A new VLAN is not automatically an inter-VLAN firewall rule.

Configuration/check sequence

1. In the documented controller UI, open Settings > Wired Networks > LAN > Create New LAN. Choose an Interface when the adopted gateway should provide Layer-3/DHCP service; a Layer-2 VLAN object alone is different.
2. Carry the intended VLAN through the switch-to-AP and switch-to-gateway links using the appropriate port profiles. Preserve the management/native VLAN rather than replacing every PVID.
3. Set the wireless network's VLAN to the same intended ID. Check the actual controller version before applying a menu screenshot from older documentation.
4. For gateway-port PVID changes in the v5.8+ example, inspect Devices > gateway > Ports > Edit. Do not copy an ISP's WAN VLAN into the LAN design without justification.

Verify / undo

Reconnect one test client. Confirm its subnet, DHCP server, DNS and intended access policy; test blocked cross-VLAN access explicitly. On failure, restore the saved port profile and SSID assignment before broadening firewall rules.

Official evidence

• Omada controller port VLAN configuration (v5.8+) — rf2-omada-port-vlan
• Omada gateway LAN/WAN VLAN behavior — rf2-omada-vlan
• Omada controller LAN profiles and SSID VLANs — rf2-omada-sdn

Editorial boundary: No hands-on testing was performed. Confirm the device label, current firmware and live official instructions before making changes. Never send passwords, VPN keys or complete configuration backups to RouterFix.

Referenced models

Try the right tool