Hi all,
Basically long story short - i have the need to replace my company’s APs with other ones, i chose cAP AC since it looks great on paper but, setting up a test device proved to be a challenge as everything seems to work up until i create a virtual AP, i used wlan1 (2.4Ghz) as it’s master interface and the connection has been very unstable since, with lots of drops and unconsitent performance across both interfaces the master and virtual.
Then after a short while it decided to stop working with just throwing Unicast key timeout messages for each attempt to connect a device on both the virtual and the master interfaces.
I have looked around the forums and i can see loads of people having performance problems with these devices but none of them have replied not being able to connect with any device at all when adding a virtual ap to a wireless interface.
I can replicate this by just adding a virtual AP ( wlan3 ) to one of the wireless interfaces ( wlan1 ), as the moment i do this no wireless connection will be possible and on trying to connect i can see the messages Uncast key timeout for every connecting device but not sure why is this happening only
Moreover if i disable the VirtualAP devices start reconnecting to wlan1 just fine.
So has anyone encountered such a behavior ?
Wireless Interface stats:
0 R name="wlan1" mtu=1500 l2mtu=1600 mac-address=CC:2D:E0:02:C1:FA arp=enabled interface-type=IPQ4019 mode=ap-bridge ssid="Company-MK" frequency=auto band=2ghz-b/g/n channel-width=20mhz secondary-channel="" scan-list=default
wireless-protocol=802.11 vlan-mode=no-tag vlan-id=1 wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no
security-profile=profile-local compression=no
1 R name="wlan2" mtu=1500 l2mtu=1600 mac-address=CC:2D:E0:02:C1:FB arp=enabled interface-type=IPQ4019 mode=ap-bridge ssid="Company-MK5" frequency=auto band=5ghz-a/n/ac channel-width=20/40mhz-Ce secondary-channel="" scan-list=default
wireless-protocol=any vlan-mode=no-tag vlan-id=1 wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no
security-profile=profile-local compression=no
2 X name="wlan3" mtu=1500 l2mtu=1600 mac-address=CE:2D:F0:02:C1:BA arp=enabled interface-type=virtual master-interface=wlan1 mode=ap-bridge ssid="Company-GUEST" vlan-mode=no-tag vlan-id=1 wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no
bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no security-profile=profile-guests
Update:
I was thinking maybe i got a faulty radio module in my AP so i ordered another one just to test, same behavior and it’s not a complex setup, it’s literally just wlan1 and 2 in bridge receiving IPs from a router and a separate bridge with an assigned DHCP server for wlan3 used as guest network.
That’s all, so why this strange behavior - do i do smth wrong ? Cause it doesn’t look like it from where i stand.
Attached a screenshot of how it loogs in the logs, observe the consistent triest to connect and the device just won’t accept the connection.
It worked for about 2 hours then it starts doing this.
Anyone with more expertise in setting these up can help ?
Also forgot to mention that both devices tested are running ROS 6.42 Stable also tried going to 6.42.53 RC with the same results.
