Q: OSX Yosemite Wifi issues

I made no personal attacks on you, I'm unsure why you feel you have the right to make them on me, never mind to go so far as suggest that I'm someone you can't wait to die, because you mistakenly believe me to not share the same operating system preference to you.  Are you really that low?

I spent several hours on the phone with Apple, and emailing packet traces to engineers, not because I can't follow simple instructions, and not because of narcissm, but because this issue cannot be fixed for all of us, unless some of us can provide engineering with low-level data with which they can triage and fix the issue.  I escalated through the support tiers, not because I demanded to speak to a supervisor, but because at each level of support, with Apple's best (and I have to say, the support staff on chat, email and phone have been talented individuals, and above the bar for a typical technical support organization) looking at the problem, they were baffled why the fixes weren't working, and so need to escalate to someone with more experience than them. Now we have actual OSX engineers trying to understand what is wrong, with data that is useful to them, and hopefully that will accelerate a fix for all of us.  Thousands of people in a forum saying "Yosemite broke my wifi" may be interesting, but it's not actionable without more information.

While it's great that the osxdaily fix worked for you, it's naive at best and arrogant at worst, for you to assume that because it doesn't work for 60,000+ more of us, that it's because of our own personal failings, rather than because we tried it, and it actually doesn't work for us. 

As for your judgement on me; apart from it being totally out of line, it's also totally wrong.  Like many many others in this forum, I spend my time equally in the Apple and Microsoft ecosystems, on Apple and non-Apple hardware.  What a ridiculous comment to make.  I am glad you get such enjoyment working with Adobe software -- I led a team of designers and engineers there for close to 10 years, up until only a few years ago, and we all worked on and with both the PC and Mac versions of the software that you enjoy using each day.

No need for a response.; there's no recovering from looking like a child here, unless you have the humility to offer an apology.

And if you make any more ad hominem attacks, or suggestions about harm coming to me or others on this forum, I will report it accordingly.

Through my testing I have found the same issue as you Ikester. Keep in mind this is from a clean install, I didn't upgrade or migrate data. All apps were installed fresh and documents transferred from an external after the clean install. I have never had a use for bluetooth until OS X 10.10 with handoff and continuity with my iPhone. I have made the same observation, but I have some more details about my specific system. If I shutdown and reboot the system with bluetooth on, then my speeds are drastically reduced to less than 1mbps downloads. If I do the same with bluetooth off before shutdown, on reboot I get my normal full wifi speeds. If I turn bluetooth on after this reboot then the speeds are cut in half. Turning bluetooth off doesn't seem to restore the speeds to the original speeds until a full reboot. I don't have any of the wifi drops just the reduced speeds.

Like everyone else in this thread i'm completely annoyed that this bug exists in Yosemite and it's a big fail on Apple for releasing it with a flaw of this magnitude.  I think i've tired every fix in the thread but the issue still persists with my Asus RT-AC87R router on the 5ghz band.  I did an upgrade from Mavericks (for what it's worth).

I finally just renamed the 5GHz wifi network to a new name (just append 5ghz or what you want to the end of the SSID) and only have my Macbook Pro connecting to the 2.4GHz signal and the wifi works as expected.

Is it ideal... nope its a work around but i'm no longer wanting to throw the Mac out the window and I guess i'll sit and wait for a fix from Apple to come ASAP.

Just my 2 cents.

I could not connect to my Airport Extreme anymore after updating my MacBook Pro 13" early 2011 from Mavericks to Mac OS X 10.10 Yosemite.

1. and 2. from the following link: http://osxdaily.com/2014/10/25/fix-wi-fi-problems-os-x-yosemite/ helped me.

Apple need to fix that....

I had the same issue with my iMac.

Started yesterday and spent about an hour on the phone with Apple support trying out about ten different things.

The support guy was very friendly but clearly steered me to issues with the router, my service provider etc.

I kept telling him that all my other iDevices connected without any issues and are able to get on the web.

This evening I kept trying other stuff while going through some blogs. One of them finally spoke about issues with the SMC (system management controller)

The procedure is very simple and documented on Apple support webpage Intel-based Macs: Resetting the System Management Controller (SMC)

I could not believe it after having done the next 5 steps my iMac connected to my WiFi network as if nothing happened ....

1. Shut down the computer.
2. Unplug the computer's power cord.
3. Wait fifteen seconds.
4. Attach the computer's power cord.
5. Wait five seconds, then press the power button to turn on the computer.

Hope it works for you as well (the support page has also instructions for MacBooks with batteries)

Edit: one thing I did as well, is turning off the continuity feature from my iPhones (not sure it is related) The French blog that guided me to the solution said that this bluetooth feature might interfere with the WiFi connectivity . . . I am reluctant to turn the feature back on. I guess I'll wait till Apple comes out with a point update stating "solving WiFi related issues" :-)

cbs20, I haven't seen the issue you're having with the reboots. In my case, just turning Bluetooth OFF is enough to restore the WiFi bandwidth. But I would encourage you to write on that other thread I linked and also to contact Apple with your details.

Thanks for a dose of sanity...and reality. 

Hi,

I've been caught up in the Upgrade issues with Yosemite. Instead of expressing how stressful things got, here is what worked for me.

I simply followed the instructions to remove and reinstall the Wifi interface. Checked the channels on the router and rebooted everything.

Boom!!! My troublesome connection went from 3/5 MB and stalling to a rocket speed off 65+ MB.

Thank god, I can get get back to work now. :-)

Colin

Turning off bluetooth did not work for me.  Interestingly, I'm only having this issue with my macbook air, not my iMac (both upgraded to Yosemite).  AND, I only have connectivity issues when using Apple TV with MacBook air.  Trying to pair with Apple TV causes the entire wireless system in my house to crash.. When I reboot the modem and Apple router, turn off Apple TV, shut down and restart my Macbook Air, everything is fine.  But I cannot use the MacBook Air with Apple TV without a complete wifi crash.

Fun times...keeping the faith that Apple will fix soon.  Pretty please.

Well it helped for 24 hours!   Now back to dropping out  frequently.

Final Solution

Hi Guys,

i've tried all solution, but not working all time... i finally find a post explaining how to processed to clean instal. It seems that the problem comes from some macbook under Mavericks moving to Yosemite.

i followed the steps on http://osxdaily.com/2014/10/18/clean-install-os-x-yosemite/ and i'm happy to find again my laptop working fine.

hope this can help, but before, plz make a backup, in my case, i used 2 partitions, and run the update from flash usb storage.( http://osxdaily.com/2014/10/16/make-os-x-yosemite-boot-install-drive/)

regards

I have a 2012 MBP Retina. Updated to Yosemite on update date (silly me). Wifi died right away. Since then - it has been on and off. Tried all the fixes, none of them seem permanent. Wifi works fine from other mavericks macs. The only thing that seems to help is keeping VPN on.

On a related note : Apple is now editing negative posts on this forum (my message got pulled twice due to rather innocuous comments about having to use a competing OS). Way to go Apple !

Okay, I don't know if it's the solution (sounds so crazy..) but it did work for me.

I did not try any of the other solutions presented on the thread.

I use a mid 2014 rMBP (1 month old), 13" with Yosemite.

I had a VERY bad ping of my wifi router (Apple Extreme), more than 500ms (next to me)

I have an iPhone 5 with iOS 8.1.

I turned off wifi and bluetooth on my iPhone, then on again.

I can ping my wifi router now with acceptable ping

64 bytes from 192.168.0.20: icmp_seq=402 ttl=255 time=1.802 ms

64 bytes from 192.168.0.20: icmp_seq=403 ttl=255 time=7.184 ms

64 bytes from 192.168.0.20: icmp_seq=404 ttl=255 time=2.079 ms

64 bytes from 192.168.0.20: icmp_seq=405 ttl=255 time=1.729 ms

64 bytes from 192.168.0.20: icmp_seq=406 ttl=255 time=1.914 ms

64 bytes from 192.168.0.20: icmp_seq=407 ttl=255 time=2.440 ms

64 bytes from 192.168.0.20: icmp_seq=408 ttl=255 time=3.052 ms

64 bytes from 192.168.0.20: icmp_seq=409 ttl=255 time=3.991 ms

64 bytes from 192.168.0.20: icmp_seq=410 ttl=255 time=1.666 ms

64 bytes from 192.168.0.20: icmp_seq=411 ttl=255 time=4.072 ms

64 bytes from 192.168.0.20: icmp_seq=412 ttl=255 time=1.540 ms

64 bytes from 192.168.0.20: icmp_seq=413 ttl=255 time=1.593 ms

64 bytes from 192.168.0.20: icmp_seq=414 ttl=255 time=6.553 ms

64 bytes from 192.168.0.20: icmp_seq=415 ttl=255 time=1.589 ms

64 bytes from 192.168.0.20: icmp_seq=416 ttl=255 time=29.574 ms

Worth a try.

regards

Brice

That's interesting - I have noticed that my mac Wifi was faring better when I was away from my home desk. I thought this was because of a bunch of BT devices that sit there (the BT/Wifi negative interaction being well documented). But that is usually where my OS8.1 Ipad sits. Will try to see if there is a correlation (although keeping my Ipad & mac in separate rooms or with wireless interfaces off is not a great fix )

still drops. and still not working. and still very annoying

apple, you must stop doing this ****, get it fixed ASAP