Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Some OS X Yosemite Users Plagued With Wi-Fi Connection Issues

Priorities

I'm sure that Apple and it's $155 billion in cash would like to thank each and every one of their unpaid beta testers for bug detection. Keep it up, because this money saved by Apple can be used in their continuing efforts to design new color and case combinations for the Apple Watch and ever more fashionable icon design for OS/X. A company just has to have its priorities, and you ain't one of them.
 
What is it with Apple and their wifi problems? Almost everytime they release a new version of iOS, there are tons of wifi issues. Now they can't even get OSX right without wifi issues??
 
derek4484 said:
What is it with Apple and their wifi problems? Almost everytime they release a new version of iOS, there are tons of wifi issues. Now they can't even get OSX right without wifi issues??
Click to expand...

And yet, everyone says that it's "fine" for them and that it's never a big problem.

And that their Apple stuff works 100% properly all the time.
 
Apple just can't do Wi-Fi. It's some kind of mystery that will never be solved.

Seriously. These wifi issues have been going on since the beginning of time. All my windows machines and OS version since Win95 through 8.1 have never had problems.
 
No clean install for me just installed over maverick. I wonder if it's something to do with the built in wifi module in the hardware? I know under windows this would more then likely a bad driver or corupted ver of the driver. Seems like if that's
 
I'm a it technician at a school (exclusively Mac only) and can confirm this is a pretty widespread problem. Luckily, not that many have updated yet, but it is quite tedious to remove network and certificates to fix the issue.

The network just drops and tries to reconnect over and over again. Then they show up at my desk.
 
Percentages of Yosemite users

Anyone, please: which post(s), in particular, imply the pretence described below?

(Have I been steered to the wrong topic?)​

grahamperrin said:
Maybe the most ridiculous assessment, to date, of relevant topics:

n-evo said:
… The anti-OS X Yosemite camp likes to pretend they're the vast majority …
Click to expand...

Which post(s), in particular, imply that majority?
Click to expand...

n-evo said:
…I'm positive the search engine works just as well on your side as it does on mine. Or are you perhaps suffering from those Wi-Fi connection issues? …
Click to expand...

----------​

n-evo: you're fairly familiar with the 'looks terrible!' topic. I tried to make my rejection of Yosemite fairly clear – twice before its release, twice afterwards – 14th, 15th, 25th and 25th October.

My pre-release tests were limited to a single home environment, I don't recall problems, I gave no thought to networking in Yosemite. (The overwhelming trouble, ultimately the showstopper, was the appearance of the operating system, but that's off-topic here.)

Please know that I truly did reject Yosemite. I have the released installer, but no desire to install or test the released build.

I have no observable issues with Wi-Fi with Mavericks, OS X 10.9.5. eduroam in the mix, and so on.
 
CRL checking

The problems we're seeing seem to be a combination of two issues.

There seems to be some indication that dual band (802.11n & 802.11ac) APs are involved - the idea being that if the client can see a poor quality 802.11ac AP *and* a good quality 802.11n AP, it will constantly flap between them.

That in itself might not be so bad, but the extra problem is that it can take several seconds to roam to a new AP since the WPA supplicant tries to check AP certificates for revocation *before* bringing the network up (think about it). It ends up sitting there for a few seconds before timing out and connecting anyway.

The workaround for the first problem seems to be to pick either 802.11n *or* 802.11ac - i.e. don't mix APs that only do 802.11n with ones that do both 802.11n and 802.11ac on the same SSID (at least, not in the same building).

Apple's suggested workaround (at http://support.apple.com/kb/TS5258) for the second problem is to mark the AP certificates as trusted. You also have to mark any intermediate certificates as trusted, since it tries to check the whole certificate chain against the CRL/OCSP. This is pretty annoying since you have to do it on each client.
 
It's not just Yosemite. For some, iOS8 is having all kinds of WiFi problems now as well (clean install & persistent, even after 8.1)
 
mordac said:
The problems we're seeing seem to be a combination of two issues.

There seems to be some indication that dual band (802.11n & 802.11ac) APs are involved - the idea being that if the client can see a poor quality 802.11ac AP *and* a good quality 802.11n AP, it will constantly flap between them.

That in itself might not be so bad, but the extra problem is that it can take several seconds to roam to a new AP since the WPA supplicant tries to check AP certificates for revocation *before* bringing the network up (think about it). It ends up sitting there for a few seconds before timing out and connecting anyway.

The workaround for the first problem seems to be to pick either 802.11n *or* 802.11ac - i.e. don't mix APs that only do 802.11n with ones that do both 802.11n and 802.11ac on the same SSID (at least, not in the same building).

Apple's suggested workaround (at http://support.apple.com/kb/TS5258) for the second problem is to mark the AP certificates as trusted. You also have to mark any intermediate certificates as trusted, since it tries to check the whole certificate chain against the CRL/OCSP. This is pretty annoying since you have to do it on each client.
Click to expand...

I don't think it's a AP (if by that you mean basestations?) problem, I believe it's more related to the certificates you mentioned. We have Cisco equipment and still loads of problems.
 
we need a study; we really could help.

all good over here. would like to see who was on the developer runs; who was on the public beta runs; and who was on none of the above either mavericks or earlier and out of those who is experiencing the wifi issue after installing the 14A389.


start responding back with what you were using before the yosemite we all downloaded on 10/16 came out either a)DP b)PB c)10.9 or earlier. And then are you experiencing wifi issues after installing 14A389 and what is your machine



example;----me------ A)---Early 2013 MBPro 15" Retina, No Wifi issues after installing 14A389.
---Pops-------C)---Mid2008 IMAC 21", No Wifi issues after installing 14A389.
 
Last edited:
How did Apple ever get the reputation that It Just Works, ever since being on this forum it sounds more like It Just Doesn't Works.

Anyway I don't have the WiFi problems on my Mac Mini, could be that Ethernet cable hanging out the back.
 
currentinterest said:
Me: 15 inch Early 2011 MBP, no problems (no graphics problems either)
Wife: 13 inch MBA 2012, no problems
Son1: 15 inch rMBP 2013, no problems
Son2: 13 inch MBA, 2012, no problems
Friend: 27 inch iMac 2013, no problems
Click to expand...

thank you. see if we can get more answers! how ever i think its gonna be just as important in terms of US figuring out the problem BEFORE a FIX is released (because we are awesome like that) if you guys respond back with were you running the Developer Preview before you installed, the Public Beta or, 10.9 or earlier + your machine
 
Been terrible on my 09 MBP completely random drop outs, sometimes connection lasts a few minutes sometimes a few hours very frustrating if in middle of watching something on netflix.
Only way to resolve is to restart computer turning on/off wi-fi doesn't fix, however during drop out still able to access router settings via 192.168.0.1 but no apps able to connect to internet.
Last time I update to a .0 release.
 
FatMax said:
I don't think it's a AP (if by that you mean basestations?) problem, I believe it's more related to the certificates you mentioned. We have Cisco equipment and still loads of problems.
Click to expand...

Yes AP=Access Point=basestation.
What difference does a Cisco badge make? We use Cisco equipment too.
I didn't say that it was a problem with an access point itself. I said it was the client flapping between two (or more) available access points: one has better signal, the other has better bandwidth. Each time it connects to one it has a reason to switch to the other.
 
Add me too: iMac with Yosemite AND iPad Air 2 with iOS 8.1. Losing wifi randomly. Older pads, w7 PC fine. Older iPads running iOS 8.1 also.
 
I've been fortunate with my 2012 cMBP and a 2nd generation AEBS - no WiFi issues for me on Yosemite.

All of my other computers are connected over Ethernet.
 
Ditto, but I've "fixed" my problems for now.

As with every OSX upgrade I had wifi problems with this upgrade.

It was not isolated to just one machine, and it seemed to affect my whole network.

I performed a hard reset on all of my network kit (Airport Extreme-ac, AirPort Extreme-n, and Airport Express), rebuilt the network from scratch, and did not turn on the 5GHz band, so I am running 2.4 GHz only, and so far everything is happy.

I am also glad I rebuilt everything from scratch, as now I have IPv6 working everywhere it should be, and my internet speed tests are actually showing about a 20% improvement.

Once Apple releases an update to fix networking I'll turn on 5GHz at that point.
 
WiFi is Fine, sound is an issue though

I've had no problems with Wifi on my rMBP, but the sound on my nMP is inactive after the computer goes to sleep. Unplugging and plugging my headphones in again fixes it temporarily however.
 
My understanding is that this is caused by how the OS is managing the power saving features of the WiFi antenna. When it puts it into power saving mode, this causes incompatibilities with quite a few WiFi access points that causes the connection to drop. Reselecting the WiFi network will solve it for a minute or two at most but gets annoying really quick.

The temporary work around is this: Create an Automator script to ping your WiFi AP every 2 seconds.

This works for me and I've not dropped my WiFi connection since. But it's a pain and a lot of overhead to ping your gateway all the time but it'll have to do until Apple can fix this. In Windows and Linux, you have the option of disabling power saving on your WiFi adapter but not on OS X. A shame...
 
Just to let you all know...

My 1990 Mac Classic is working just fine on system 7.0.

Cheers.
 
My guess is that they are using the same wi-fi software in iOS (8.x) and Yosemite - transferring iOS's wi-fi brokeneness to OS/X.

The most annoying (no, in truth, PISSING-OFF) thing is the abject refusal to acknowledge that there is even a problem compounded by doing nothing about it for over a month - working instead on releases/patches that only add money making features rather than fixing anything.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back