Code: Select all
/caps-man datapath
add bridge=brLAN client-to-client-forwarding=yes comment="WIRELESS VLAN" local-forwarding=yes name=datapathWIRELESS \
vlan-id=40 vlan-mode=use-tag
add arp=enabled bridge=brLAN client-to-client-forwarding=yes comment="SMARTHOME VLAN" local-forwarding=yes name=\
datapathSMARTHOME vlan-id=41 vlan-mode=use-tag
add bridge=brLAN client-to-client-forwarding=yes comment="FON VLAN" local-forwarding=yes name=datapathFON vlan-id=42 \
vlan-mode=use-tag
add bridge=brLAN client-to-client-forwarding=yes comment="GUEST VLAN" local-forwarding=yes name=datapathGUEST vlan-id=50 \
vlan-mode=use-tag
Code: Select all
/interface wireless cap
set bridge=bridge1 certificate=request discovery-interfaces=vlanMGM enabled=yes interfaces=wlan2,wlan1 lock-to-caps-man=yes
On the cAP's i replaced the wireless package with the wifi-qcom-ac package. Unfortunately I later found out, that the documentation states that vlan assignment is currently not possible with the ac drivers:
Like it was mentioned in this documentation entry I've enabled vlan filtering on the bridge on the cAP and assigned wifi1 the corresponding vlan access port and removed the vlan id in the datapath configuration on the CAPsMAN. This setup worked very well but only with one master configuration. After enabling some secondary slave configurations in the CAPsMAN there were several slave wifi interfaces created in dynamic mode on the cAP. I was unable to assign those dynamic interfaces a fixed vlan, because after a reprovision of the cAP their names changed (numbers were increased).802.11ac chipsets do not support this type of VLAN tagging , but they can be configured as VLAN access ports in bridge settings.
So my questions here:
- Will the vlan assignment for wifi interfaces in the wifi-qcom-ac be supported at some time?
- If not, is there any workaround in this scenario I can apply? The mentioned approach with the vlan filtering on the bridge only works for the master configuration. So unfortunately I can use only one wifi with one vlan