Just wondering what the various workarounds people have tried with any success at all to this issue? The first patch doesn't appear to have done the job, and who knows when the final fix will come. I seem to remember it took Intel the best part of a year to resolve 802.11n issues in their 5000 series cards.
We had one user who was getting dropouts every couple of minutes with sometimes an almost instant re-connect to minutes. This was after installing the update patch. The device has no such issues however on a WPA2/AES-PSK network. This has been good to provide a solution there, however PSK's are not overly scalable for a campus. Another user reports that disabling v6 & some sleep settings have helped the situation somewhat. I'm hoping to get more information on that sometime today. I see Travis mentioned below an idrequest time-out increase from 5-30 seconds on Aruba. I'm doing a bit of research now and considering little session of testing later in the week so was interested to see what people have tried and how much it's helped. Either client or network side. -- Jason Cook Technology Services The University of Adelaide, AUSTRALIA 5005 Ph : +61 8 8313 4800 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Shandon Bates Sent: Saturday, 20 July 2013 10:19 AM To: [email protected] Subject: Re: [WIRELESS-LAN] Problems with new Apple Laptops Should be patch issued... Sent from my iPhone On Jul 19, 2013, at 5:10 PM, "Shandon Bates" <[email protected]<mailto:[email protected]>> wrote: Patch issues for air issues. http://mashable.com/2013/07/19/macbook-air-wifi-fix/ Sent from my iPhone On Jul 19, 2013, at 4:53 PM, "Travis Schick" <[email protected]<mailto:[email protected]>> wrote: I've been getting reports of issues with macbooks on our wpa2-enterprise ssid - then I finally got one and was able to do some hands on troubleshooting. It appeared the mac would decide to roam - but then would fail to auth - and get stuck in authentication step - wifi menu icon just cycling like no connection. Worked with our vendor (aruba) and decided to increase the default idrequest timeout from 5 sec to 30sec. I think there's something going on when reauthenticating to another AP on the same ssid. tunnel setup takes a while on the macbook - I think it may be related to the cert - using the incommon cert - so have server cert incommon intermediate and addtrust root ca... this is a chunk of data that gets fragmented... not sure if the mac doesn't like reassembling it - takes exception to it comming from a new bssid or what. But it does look like increasing the timeout helps... still a few second without connectivity - but sure as heck beats the macbook getting stuck in its authentication step and staying offline until user intervenes. so still looking into it, but perhaps that info might prove helpful to others. macbook is running 10.8.4 - and I was running that prior to changing my timer settings. Travis Schick UCDavis Network Operations Center . ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
