Q: OSX Yosemite Wifi issues

Hello there, I would like to share some workaround that I did yesterday playing with slow wifi connection on Yosemite. Don't know if it helps in general but for me everything works now perfectly and fast. Try to, maybe it will help you as it helped to me.

1) go to System Preferences - Network - Select your Wifi Adapter and Click Advanced

2) tab Wifi - uncheck "remember networks this computer has joined"

3) tab TCP/IP - Configure IPv6: - select "Link-local only"

4) tab DNS - add static record for DNS Servers: "8.8.8.8" (the google ones)

5) tab Proxies - check "Exclude simple hostnames"

6) tab Hardware - Configure - select "Manually" - MTU: "Custom" - and the number set to "1495"

This helped me, try your luck and leave some comments.

Stefci

BTW: running MacBook Pro, Retina 13", early 2013, OS X 10.10.1

No change for me either!  One minute I'm yelling at my Internet provider; the next I hunting for new Internet service; and then I'm considering purchasing a new Time Capsule because I'm sure it's the problem!

I was suspect when an update came down recently; wi-fi was on off the issues it addressed!

I thought I had mine stablised only for it to go into a right tizzy over the past few days and now I'm back to being angry to the point of exploding again.

One thing I categorically will not do to fix my problems with connectivity is buy another apple product.  If I have to put my hand in my pocket to sort this out there is no way I'm giving money to the people who caused it.

How long have you been running since without a disconnect?

Am trying now. Have tried EVERYTHING else which hasn't worked at all.

I've been getting around 3 mins before my speeds go sub-100kps. I don't get disconnected. I get dial up speeds from 1979.

Best I've managed since 10.10.1 killed my wifi is 3 hours this morning by resetting EVERYTHING.  I was working fine with 10.10. It was 10.10.1 that did it to me. (MacBook Air 2012)

TO STEFCI.....

HOW LONG HAVE YOU BEEN RUNNING NOW WITH NO DISCONNECT?

Please give me a reading/screenshot of your System Preferences>Network. Or, as an experiment, chuck out all listed network devices but Airport, chuck out all listed networks but your home network and start up (indeed, no restart) in Safe Mode ("shift" on startup). Next, start up normally. Recheck if only Airport (EN0) is active as a listed network interface. Moreover, switch off all other iDevices (Phone, Pad, Pod) in the vicinity. Turn Bluetooth off as well. Remove all peripherals but a cabled keyboard and mouse if running a MacPro, Mac Mini or iMac. Next, see if the issue persists.

If not, step by step add the rest of the needed Ethernet and BT interfaces/ services/hardware/iDevices. Start cleanly again after each step.

If yes, try and restart your modem, next your router, next your Mac. With a few minutes in between. Good old troubleshooting...

There has been much whining in this thread, but little or no systematic testing/ troubleshooting, sorry.

Or get us an Etrecheck report. I've been following this thread from the beginning, but cannot recollect seeing more than 1 (sic) Etrecheck report. This is a sickening situation, meaning from the plaintiff's side as well as Apple's.

Sorry for my rant!

It is high time Engineers at Apple review the following:

http://en.wikipedia.org/wiki/IEEE_802.11

802.11 is a simple protocol...

OS X is a BSD unix descendant --no more no less... I guess next time I'll but quality laptop and run Linux.

I think this may be MTU related. I did some testing after tweaking my MTU and it seems better. I just put it in another post but am sharing it here since so many are impacted. I hope it helps some of you at least.

By default in Yosemite the MTU set on the wireless card (SystemPrefs->Network->Wifi->Advanced->Hardware) was set to 1500. If you change this to manual, custom and then set the MTU to 1400, the wireless seems a lot more stable, and as fast as it was before.

I have only been testing this for a few hours but so far so good.

You may be right, jfialkowski.

I know for a fact that Apple AVB is not Jumbo Frame compliant. But in this case, I think we are dealing with a different beast. Many of the plaintiffs here do not even have an AVB compatible Mac. Although with lots of complaints and little or no hardware profiles, there is little or nothing to go on here.

My suspicion, as has been stated, is that here is some confusion under Yosemite as to what Ethernet interface to use first (a.o.). And that Yosemite is swamping the system with Bonjour calls before even trying to resolve a legit DNS call. Or swamping the system with unanswered Bonjour calls in between DNS calls.

And there is always the question of Airdrop or Handoff trying to connect to iDevices. Might be better to switch to Airplay/ turn off Handoff and leave iOS Devices alone. At least for testing purposes.

To be continued... 

hexdiy wrote:

 

You may be right, jfialkowski.

I know for a fact that Apple AVB is not Jumbo Frame compliant. But in this case, I think we are dealing with a different beast. Many of the plaintiffs here do not even have an AVB compatible Mac. Although with lots of complaints and little or no hardware profiles, there is little or nothing to go on here.

My suspicion, as has been stated, is that here is some confusion under Yosemite as to what Ethernet interface to use first (a.o.). And that Yosemite is swamping the system with Bonjour calls before even trying to resolve a legit DNS call. Or swamping the system with unanswered Bonjour calls in between DNS calls.

And there is always the question of Airdrop or Handoff trying to connect to iDevices. Might be better to switch to Airplay/ turn off Handoff and leave iOS Devices alone. At least for testing purposes.

To be continued...

Whenever I am experiencing the Network outage... my console is overflowing with discoveryd & Handoff Messages...

When Network is running normally, I have little of those messages...

This I have reported to Apple along with system diagnostics and screen casts of the issue being at large...

If your underlying network at layer 2 is having (MTU) issues, you can see strange effects in protocols at a higher layer in the stack. So if your packets are being dropped or fragmented along the way because the MTU is too large, handoff, spotlight, browsing the web, etc can all be impacted. Going on 5 hours with my new MTU settings and I am happy to report it seems to have solved the issue for me.

Well, Morten James Carlsen, I'm glad you have a more open line to Apple than we all have.

But you know as well as I do that Discoveryd has replaced mDNSResponder under Yosemite, and that discoveryd going berserk probably means it is trying to find devices in vain or trying to resolve DNSes in vain.

Maybe query DNSServiceResolve. Saying more will possibly violate my NDA.

Hi Hex

I did try all that you listed/suggested. Things went bad. And in worse. But I rebooted, rebooted everything, and rebooted a few more times and I  finally ended up with the best 3 hours with my MacBook Air since Yosemite.

Then it all went down the pan again. It worked, kinda, for a while.

As a little experiment (just now) I reset everything and things were fine (I get a 3-min window usually) and I ran a speed check -- but then I opened AirDrop and turned that on. My speed dropped instantly to 5kbps. Yes 5. And stayed there.

EDIT: Can't connect to Ethernet. On MacBook Air.