I have recently deployed BlueSocket APs on a customer prem. They are an exclusive Mac user office. It appears that after a random amount of time they just stop being able to connect to the internet. We are unable to ping to the gateway from the Computers and vWLAN still shows it as an active client. ANother tecnician and myself are running Windows PCs and have had no problems. Has anyone else run into this problem? Below is our layout, I can give you anymore details you may need
1 Netvanta 3140 Router/Firewall
1 1531P Switch
2 BSAP 2020 aps (firmware 3.2.0-HA-65047)
1 BSAP 2030 aps (firmware 3.2.0-HA-65047)
vWlan version 3.2.0.HA Build 650478
Dual SSIDS Customer network and a "guest" network.
Same issue here. Additional facts:
1. It happens to iPhones too.
2. Our office previously had BSAP 1920s and issue only happened after upgrade to BSAP 2020s.
3. Computer seems to lose all connectivity to the internet, but if you do a sustained PING to the gateway and do a packet capture on the computer, you can see sporadic replies delayed by as much as 20 seconds.
4. Another computer side by side on the same channel has perfect connectivity
5. Turning wi-fi on/off on the computer resolves the issue immediately
Not sure if we should give up on the 2020s and go back to our trusty 1920s or what. This has me stumped.
Have you tried to capture at the APs?
You would do a wired capture type on the radio interface, and compare that to a capture on the client. I would also suggest an 802.11 wireless capture to see if perhaps you have a lot of retries in the network or perhaps some odd behavior around power save. Mostly I would be skeptical that the 1920s behave better than the 2020s.
I will perform a simultaneous capture next time on the computer and AP as you describe. I am not very familiar with the 802.11 option though since it appears it will cut off service completely while it goes into Sensor Mode. Do I need to have an extra BSAP2020 to do the capture so everybody else isn't affected?
This post is about Macbooks, which have wireless capture capability built-in. Windows users might consider Windows Network Monitor or seeing if they can enable promiscuous mode on their NIC directly from Wireshark. Linux users typically have the ability to put their NIC into promiscuous mode as well. But if you don't have any other device capable of capturing 802.11 traffic, then yes you would need another BSAP to capture from.
Was there a resolution to this? I am experiencing the same issue with iPhones, Mac laptop, and Windows 10 laptop.
It is a random occurrence, but it seems to be more frequent when the client is generating more traffic. The client connection stalls out. The vWLAN doesn't show timeout, or anything wrong in the logs. Dropping the client in the vWLAN console, or cycling WiFi off/on on the device, resolves it immediately.
I'm on vWLAN version 3.3.0 build 656804. BSAP 2020 APs (firmware 3.3.0-656804)
5 SSIDs configured. This occurs on both the 2.4 and 5GHz radios, from what I can tell.
I have upgraded and have been running on the 3.5 release for a few days now. It has not resolved the issue. I also didn't see anything like this issue listed in the patch notes as resolved or as known outstanding.
Other troubleshooting I have tried that I forgot to list earlier: I thought maybe it was stopping the client session during Continuous RF events. So I set everything to fixed, and that didn't resolve it either. So the problem exists with static set channels and power levels, and on Continuous RF with client aware.
I have a feeling this is an issue with the 2020 APs. Unfortunately those are the only type I have, so I can't confirm. In the future, I would like to bring a 2030 in and test with that.