cancel
Showing results for 
Search instead for 
Did you mean: 

OSX Clients Connected to AP, but not passing traffic

jason_davis_793
Contributor
Anyone else experiencing issues with OSX clients connecting to APs, then randomly not being able to pass traffic/browse the internet?

We're seeing this primarily with OSX 10.11 clients. We have ZD1200s and R710s running 9.13.1

Ruckus support's latest fix was enabling Proxy ARP or upgrading to Sierra. But we just experienced the same issue with a Sierra device.
59 REPLIES 59

james_buckey
New Contributor
ZD3000 130 APs (88 R710 and 42 R700). Brocade ICX 7250 switching.  I have experienced this same issue but only recently after switching from various EOL HP switches to Brocade.  My issue is with all Apple devices, iOS and OSX.

dtsblake_588878
Contributor II
Since you are using ALL infrastructure Brocade products you may hear something from tech support.   I have an open ruckus case for this problem that has now been set to a status of "DEFECT."  Our techie said next support level was "blaming" Apple.

geoff_anderson_
New Contributor
Our ticket was also marked as a defect and they mentioned its an issue with Apple's code. I'll mention we're not using Brocade.

jason_davis_793
Contributor
Our ticket was also marked as a defect and Ruckus mentioned its an issue with Apple's code. I can't confirm how true that is though. I'll mention we're not using Brocade.

I can believe that a portion of the blame is with Apple, "Think different, do different". However, this was not an issue before my network overhaul.

Previously, I had a badly designed network. A 10.32.0.1/16 network, VLAN 1, no other config. It was a large subnet under no management but it worked. Now I have 60 VLANs each building in a seperate OSFP area each SSID on its own VLAN within each building. I have quad checked all switch configs against DHCP scopes. I fixed a few fat-finger mistakes but they were issues with mistyped router IPs per VLAN which wasnt allowing DHCP requests to reach the server. Unrelated.

Being this is only Apple devices affected, the problem is obviously Apple under a Ruckus environment, undeniably. That said, I am not necessarily convinced the root cause is a non-standard way of Apple devices communicating vs an oddity in Ruckus code that clashes with something proper in Apple's.