Enabling vlan tagging on physical ports eth1,2,3, breaks vlan tagging of wifi
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Enabling vlan tagging on physical ports eth1,2,3, breaks vlan tagging of wifi
When I enable vlan tagging on the physical ports, it stops tagging the WLAN SSIDs into their relevant vlans, and just bridges them on untagged. eg all those macs in vlan 200 should be spread over a few different vlans. 200 is the native vlan for the trunk port.
Also the higher DFS channels are not available in 5G. I have a eap245 as well and they are there, but i noticed they were not initially when the device was released. This was fixed with a firmware update. Hopefully this will happen with the eap235
Re:Enabling vlan tagging on physical ports eth1,2,3, breaks vlan tagging of wifi
Dear @cscott,
Please kindly note that the ETH Port on WALL AP is only an Access Port.
Based on your configuration, ETH 1/2/3 are all configured with VLAN70, they can only communicate with the devices in VLAN70.
>> Omada EAP Firmware Trial Available Here <<
*Try filtering posts on each forum by Label of [Early Access]*