@RAuser wrote:
We have a virtual AP profile setup in bridge mode with settings:-
VLAN:13-14, Forward mode:bridge
The controllers are on vlan 12
Do I need to define all the VLANs in each of the controllers- configuration/VLANs/VLAN ID to get it to work properly?
Vlan 12 has been defined in the controllers for the GE1/0 port, and APs are connected on the vlan 12. Do I need to associate vlan 13, vlan 14 to the controllers? It is working without vlan14 defined but is that right?
The APs are connected to network switches and those connected ports are with vlan 12 untagged and vlan 13-14 tagged.
Thanks in advance for any help.
RAuser,
Is there a reason why you are bridging user traffic? It is much more troublesome to have to configure trunk ports on access points than to tunnel the user traffic back to the controller and to just have the controller put the user traffic on the correct vlan.
If you need to bridge user traffic, Here is a shortcut:
When using bridge mode, just set Vlan in the Virtual AP to 1. Why? By default if you are using bridging, the access points will determine whether it puts an 802.1q tag on client traffic by comparing the VLAN in the Virtual AP to the VLAN in AP-Group> AP> System Profile> Native VLAN. If the Virtual AP VLAN matches that value, it will bridge the traffic out of the access point, but not tag it. If it does not match that value, it bridge the traffic, and tag it with the Virtual AP vlan. Since the Value in the Ap-Group> AP> System Profile> Native VLAN by default is 1, you will always get client traffic bridged without tagging if you make the Virtual AP 1. It will not matter what VLAN your access point is physically on: it will simply bridge the client traffic without issue.
When would you want to make the Virtual AP VLAN something other than 1? If your access points are physically on trunk ports and you always want to put the client traffic on that VLAN that is tagged.