I have observed the same, only in my network where I have mix of AX and AC devices (hAP AX2, hAP ac2, cAP ac, controler is a CHR).
Tested with 7.14, 7.14.1 and 7.15beta[46], behaves the same.
Both AC devices reset to CAP mode, then applied VLAN config like this:
I did not have to add Wifi interfaces to bridge because they are added automagicaly, and with correct VLANS.
I know, this is not the same as in MT Documentation, but it works the same, tested.
Message "Client was disconnected because could not assign vlan" appears only after some time, and it seems that once it appears noone can attach to the particular SSID.
It does not appear on 4 other networks where I have AC devices only, 4-8 of them per network, with the same VLAN configuration.
Tested with 7.14, 7.14.1 and 7.15beta[46], behaves the same.
Both AC devices reset to CAP mode, then applied VLAN config like this:
Code:
/interface wifiadd configuration.mode=ap datapath=capdp datapath.vlan-id=222 master-interface=wifi1 name=wifi1pubadd configuration.mode=ap datapath=capdp datapath.vlan-id=222 master-interface=wifi2 name=wifi2pubset [ find default-name=wifi1 ] configuration.manager=capsman .mode=ap datapath=capdpset [ find default-name=wifi2 ] configuration.manager=capsman .mode=ap datapath=capdp/interface bridge vlanadd bridge=bridgeLocal tagged=ether1,ether2,ether3,ether4,ether5 untagged=wifi1pub,wifi2pub vlan-ids=222/interface wifi capset discovery-interfaces=bridgeLocal enabled=yes slaves-datapath=capdp slaves-static=yesI know, this is not the same as in MT Documentation, but it works the same, tested.
Message "Client was disconnected because could not assign vlan" appears only after some time, and it seems that once it appears noone can attach to the particular SSID.
It does not appear on 4 other networks where I have AC devices only, 4-8 of them per network, with the same VLAN configuration.
Statistics: Posted by sinisa — Thu Mar 14, 2024 1:15 pm