Apple OSX devices getting no internet while connected to Ruckus APs

  • 1
  • Question
  • Updated 3 months ago
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 7 months ago

  • 1
Photo of Edward Newman

Edward Newman

  • 7 Posts
  • 2 Reply Likes
We see this issue too. Would love to understand a good set of techniques to diagnose such issues.
Photo of Aleksandar Radivojsa

Aleksandar Radivojsa

  • 10 Posts
  • 0 Reply Likes
Hi, I had similar issue in the past and found out that problem was caused by situation that there was many DHCP servers in the network. In that situation, Android devices worked normally, but iOS devices couldn't connect. You mentioned that you have two ZDs, so it reminded me to that case.
Photo of Michel Rougemont

Michel Rougemont

  • 2 Posts
  • 0 Reply Likes
I have the same issue, with only 1 ZD1200 managing my WiFi network...
Photo of AO

AO

  • 7 Posts
  • 0 Reply Likes
Bump to this issue. We identified that this affects Mac clients and not Windows clients.

Turning off roaming between APs and removing "dashes" in SSID temporarily solves the issues.

Do Macs handle roaming poorly with Ruckus? Can symbols in SSIDs affect Macs?
Photo of Antonio Sanchez

Antonio Sanchez

  • 5 Posts
  • 0 Reply Likes
Hello, I had the same problem, Windows users ran smoothly and Apple devices connected and disconnected randomly.
   I solved this by changing the encryption options, choosing only AES instead of TKIP+AES in the Wlans configuration. He hasn't given me any more trouble since then.

greetings.

Antonio
Photo of Simon Bryan

Simon Bryan

  • 2 Posts
  • 0 Reply Likes
Just posted a similar problem, we already use just AES. Our quick fix is to reboot the affected AP as it seems to suddenly impact on just one. Wondered whether it was some kind of attack from the user devices which are BYOD but the logs seem remarkably empty of any useful info, all I see is the reboot we trigger.
Photo of AO

AO

  • 7 Posts
  • 0 Reply Likes
Bump on this, seems like there are issues with Macs in particular. Has nothing to do with symbols in WiFi but roaming features intended to move devices to best coverage seems to “stall” Mac devices instead. What we observed are Macs that are connected at full strength (5 bars), will time out (stay connected), and either re-associate after a few minutes or user has to disconnect and reconnect manually to get internet again. Only Macs though, any idea why?
Photo of itdept_head me

itdept_head me

  • 21 Posts
  • 2 Reply Likes
We had MASSIVE problems with this , specifically macs & the WIFI chips and R500 /510 

we updated all macs to the latest os & then the  rucus to the latest firmwares.
turned off 2.4 and now we can roam over 3 floors.

We found that sometimes the macs  WILL NOT let go of a distant  AP, they fight to maintain the shitty signal even if a new ap is closer, so you might be stuck tied to a 50% sig and there is a 97% sitting over u.
cleaning out all the stupid "remembered" connections in the mac control panel goes a long way to helping.

it seems more of an issue with badly placed wifi points.
Then you get the nonsense with "dual points" where the mac  swaps between 2.4 & 5 depending on how it feels, seems swapping frequency AND AP does not cleanly maintain the connection.

then there is the issue of "sleep", if you are in a meeting room and tied to a WIFI & sleep, tehn come out of the room and relocate AP's... the mac just swallows packets,   turning the wifi on/off fixes it.

oh and YES .. symbols in the names WILL affect the mac, mac follows the RFC exactly.
strange chars, may not pass the unicode values correctly  "_-#[email protected]" etc
you will see the same with naming macs & DNS/ DHCP names.
(Edited)
Photo of AO

AO

  • 7 Posts
  • 0 Reply Likes
Wow this relates to our circumstances to a tee.
I am just dumbfounded how others , perhaps in bigger environments (schools, stadiums, etc.) that’s use Ruckus devices and support Mac users tolerate such poor interoperability.
Photo of RS

RS

  • 7 Posts
  • 0 Reply Likes
ditto on our corporate environment. This problem started from zone directors and now we still have it in Smartzone 100. Impossible to replicate but obviously everyone having the issue. All Ruckus has been recommending is controller upgrades and minor tweaks like ofdm only turn on and bss min tage adjustments which also changes with the change in Rep everytime. Now sure what else to do at this point. Even when the issue was happening we got on the call, but if there is no traffic passing, there is gonna be nothing on the capture obviously. But again, turn wifi on/off problem is fixed.
Photo of itdept_head me

itdept_head me

  • 21 Posts
  • 2 Reply Likes
Yep...
I spent 4 months on this back it 2016, initially i was sorry I purchased ruckus, but then it sort of came together.

I got really angry with apple, becasue if you go to "sys-info" ->wifi
and make a note of the : (they stripped a lot of the info out....), 

Card Type: AirPort Extreme  (0x14E4, 0x134)
Firmware Version: Broadcom BCM43xx 1.0 (7.21.95.178.1a2)

you will find macs from EXACTLY the same family with specific revisions of the BC chipset
BUT with different FW versions!!!!!, ESP. if they are from different years of production.

when you update a mac it DOES NOT update everything at a system level, apple DOES NOT keep the internal FW's updated and in sync. (no FW is NOT available)

So you might have two 'identical'   "MacBook Pro (Retina, 15-inch, Late 2013)"
but the damned  BC FW is NOT the same!!!, how the hell can any system be reliable & stable , using such poor attitudes.

We....   me .. apple.. ruckus, identified a specific issue with sleep, where RCs was "closed out" due to time out, but since the mac was woken from sleep, it still considered the "link" to be alive..
we clearly saw packets going out from apple kit and disappearing into the "ether"
Much of this should have been fixed in later  os updates of both sides.


Now my kit in factory location is fine over 3 floors of production area  (110M long)& passes off nicely as long as it cannot see distant WIFI points it tied to previously & moved whilst sleeping.
but now users just toggle the wifi if it gets "stuck" (we have seen AP hand off stuck with other brands of kit as well)

as long as my mac does not sleep... i can freely wander about our sites and no handover issues.
and  currently i have about 160 devices on WIFI... in this 1 location.
I think it is tolerated  because:
1. the mix of devices is less legacy
2. Due to pixel masterbation... kit does not sleep so much.
(Edited)
Photo of Craig Caruso

Craig Caruso

  • 2 Posts
  • 0 Reply Likes
So the outcome is to turn off 2.4 Ghz on the AP's and/or Zone Director?
Photo of izagatsky

izagatsky

  • 2 Posts
  • 0 Reply Likes
Turning off 2.4 GHz helps but doesn't fully solve the issue. We turned off 2.4 GHz last summer and have had less complaints about slowness (from connections to distant APs), but still sometimes have to have mac laptops turn airport off and back on to re-connect. iPads and iPhones support 802.11r and don't seem to have the same issues.