Apple OSX devices getting no internet while connected to Ruckus APs

  • 6
  • Question
  • Updated 4 months ago
  • Answered
We have an environment with 36 R510 APs spread among 12 floors with 2 ZD1200's on the back end. We notice on a daily basis that random set of Wifi users cannot browse the internet or get disconnected in the middle of a video call even though they have full bars for Wifi.  This is an issue because the building is 100% wireless. We have turned off DFS channels, and tweaked power levels accordingly to minimize overlap. It seems that only Apple users are effected. Are there any known issues with Ruckus and Apple devices?
Photo of AO

AO

  • 7 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 6
Photo of murimig

murimig

  • 12 Posts
  • 1 Reply Like
David,

Are your macbooks 2018 and newer? And do you mind if i ask what radius implementation you are using?
Photo of murimig

murimig

  • 12 Posts
  • 1 Reply Like
Hi Kevin,

Are you also on Enterprise authentication?
Photo of Kevin

Kevin

  • 29 Posts
  • 7 Reply Likes
Yes
Photo of David Henderson

David Henderson

  • 114 Posts
  • 31 Reply Likes
Our Cloudpath server acts as our Radius server. We are using EAP-TLS and we have Macbooks that are between 1 and 5 years old all running High Sierra or Mojave
Photo of Liliia

Liliia

  • 20 Posts
  • 2 Reply Likes
Thanks for sharing your experience David! I wonder whether any of your users have Catalina OS and what is their experience? We use as well 802.1X EAP, WPA2, AES and Cloudpath Radius onboard database for authentication, vSZ and R510 APs. I have High Sierra and do not experience disconnections on site, although specifically users with Catalina 10.15.2 OS and previously 10.15.1 experience disconnections twice a day as a rule. This is the difference. Catalina is a key point here:)
Photo of murimig

murimig

  • 12 Posts
  • 1 Reply Like
This is good information David and Kevin, let me see how i can use it for our environment. Thanks
Photo of John

John

  • 1 Post
  • 0 Reply Likes
Hi, I'm also experiencing this problem.

The WiFi works flawless for every device except Apple OSX devices (diagnostics performed on Catalina OS 10.15.3). We are experiencing poor roaming and random disconnects with no automatically reconnect on MacBook OSX devices.

We run R500/R510 APs on vSZ 3.6.2.0.222

It feels like I have tried every config there is and with no results whatsoever.
Photo of Erik Weiss

Erik Weiss

  • 2 Posts
  • 0 Reply Likes
We are having similar problems with a fleet of R700s, R710s, R720s connected back to redundant ZD3000s.

What we have discovered is that standard PSK networks operate fine with Catalina.  We use DPSKs on our main client network and have the exact issues described here.  Multiple disconnects throughout the day.  

Computers with a fresh install of Catalina seem to have less issues, though some still do have issues.  Computers upgraded to Catalina from Mojave or earlier seem to be our biggest issues.

I have an open support case with an engineer that seems interested in the issue, he has been looking into it for 2 months now.

Photo of Michael Brado

Michael Brado, Official Rep

  • 3288 Posts
  • 520 Reply Likes
Hi Erik,

And you're also using CloudPath or not?  Only Apple's latest 'Catalina' version?  Do you have MacBooks, iPhones, iPads and see the same?
(Edited)
Photo of Erik Weiss

Erik Weiss

  • 2 Posts
  • 0 Reply Likes
Sorry, should have been more specific.  Support case with Ruckus, not Apple.

The network that is having issues is only Macbooks.  Some iPads, but we haven't seen any issues with the iPads, though they might not be up to date.
Photo of murimig

murimig

  • 12 Posts
  • 1 Reply Like
So we went ahead and tested WPA2-Enterprise (MSCHAP) on 2019 macbook models and no disconnections at all, zero! Reverted to an older 2017 model and the issue returned. 

Also tested radius on cisco ISE, issue persisted (both MSCHAP and EAP-TLS)

We are about to test cloudpath (EAP-TLS), I will revert with findings.

But for our production environment we had to roll out zeroIT SSIDs (riding on WPA2 since we knew that WPA2 is not affected by this issue) which allowed us to continue using SSO (which was one of the reasons for WPA2 Enterprise to begin with). This is until we can find a lasting solution for this issue.