I still have an issue getting "Client was disconnected because could not assign vlan" even after setting ft-preserve-vlanid=no.
My devices: hAP AX3, cAP AC, and 2 wAP AC. I have configured CAPsMAN with an hAP AX3 as a manager. What am I missing?
Search found 4 matches
- Mon Jun 03, 2024 11:59 am
- Forum: Wireless Networking
- Topic: Client was disconnected because could not assign vlan
- Replies: 11
- Views: 5041
- Tue May 14, 2024 12:17 pm
- Forum: Wireless Networking
- Topic: 7.13 WiFi-CAPsMAN, Access list to assign VLANs and FT issue [SOLVED]
- Replies: 9
- Views: 13797
Re: 7.13 WiFi-CAPsMAN, Access list to assign VLANs and FT issue [SOLVED]
At this point all about VLAN assignment works fine using Access list and single SSID (which was my main goal with this setup); I mitigated the roaming issue on that single iPhone by applying the RSSI threshold to it within the Access list, so that AP kicks it out when no longer in range. However is...
- Fri Mar 10, 2023 1:57 pm
- Forum: Wireless Networking
- Topic: wifiwave2 - CAPsMAN and manage "old" deviceses as well.
- Replies: 2
- Views: 2004
Re: wifiwave2 - CAPsMAN and manage "old" deviceses as well.
Hi @MartinsG, I have the same issue with CAPsMAN ax3 and "old" cAPs. Do you have any luck with this?
- Thu Mar 09, 2023 7:08 pm
- Forum: Wireless Networking
- Topic: WifiWave2 CAPsMAN with older CAPs
- Replies: 12
- Views: 4483
WifiWave2 CAPsMAN with older CAPs
Hi All, Just received my Mikrotik hAP ax3 as a replacement for my hAP ac2 and found that it is running RouterOS 7.8 and WifiWave2 with new CAPsMAN which does not support legacy CAPsMAN. But I have a few MikroTiks cAP ac that are running on RouterOS 6.49.7 and they are managed by CAPsMAN (hAP ac2 as ...