Q: OSX Yosemite Wifi issues

Seems that someone has actually analyzed what's going wrong and has a fix for both IOS as well as OSX:

https://medium.com/@mariociabarra/wifried-ios-8-wifi-performance-issues-3029a164 ce94

Not tried this yet but this guy seems to know what he's doing.

If this is true... oh Apple what you've done..

Nope that didn't work, see page 93. Plus he's a bit off, that is not the root of the issue because none of those features are new, and disabling them doesn't fix the problem.

If i had to guess, I would guess it is related to something attempting to manage power consumption. I would theorize that syncing email and things like that do not really require the full power of a broadband connection to do, so if the computer was programmed to throttle wifi to save power, it should work. But, if that throttling interferes with other internet usage, it could create this problem.

Also, this problem is not isolated to wifi connection, it is an internet/DNS problem, so that ruins the AWDS idea.

Or, mostly likely, Yosemite is a pile of salty garbage and has no single particular issue, but rather, tons of system-breaking issues that were known prerelease and released anyways. between this and the U2 debacle, Apple has done irreparable harm to reputation for trustworthiness.

I ran the suggested command in terminal:

• sudo ifconfig awdl0 down

However, on my early 2011 MacBook Pro, the reply was:

• ifconfig: interface awdl0 does not exist

So, if my system is not even using AWDL, then that cannot be the root of the problem as it manifests on my system. (I am guessing the reason for no AWDL on my MacBook Pro is because it not so new.)

Earlier I wrote that switching my router from channel 11 to channel 10 helped, but I later realized it only helped with the more obvious issue of losing connection to the router.

Later another issue (also serious) became obvious: even while still connected to the router, the "resolving host" issue and degraded performance problem. Furthermore, those problems happen even when tethered via ethernet cable.

Note: I went from Mavericks straight to 10.10.1.

IF this matter was one which was directly attributable to Apple's profits, they would fix it in a heartbeat.

The problem is they are so good at marketing, and coupled with their legal side, they virtually control the media outlets by stopping them saying anything negative about them or their products.

The Verge is a good example, as is that German outlet who Apple "banned for life" for reporting on "bendgate." The problem arises that there is little pressure on them to fix problems like this.

Apple never used to be like this in the day.

I'm guessing my comment will be banned.

I upgraded to Yosemite, and the problem persists even after the Mac OS X 10.10.1 update last week.  It actually seems to be worse, but I cannot determine that scientifically. At a minimum, it's no better.

That ad hoc fix posted by that web page involves disabling AirDrop and AWDL, which the author of that article claims fixes the Wifi issues.  It involves typing the following into the terminal:

sudo ifconfig awdl0 down

The third part is "a w d l (lowercase L) (number zero)"

I've tested several other "fixes" out there on the Internet and none of them have worked.  I hope this one does.  If not, I'll be getting myself a 50 foot Ethernet cable until Apple finally resolves this inexcusable problem.

I have some of the network issues detailed. Today, I noticed that the green light, indicating my webcam on my MacBook Pro is on, flashes on momentarily and occassionally when swapping between Apps. This is a worrying development. Yosemite is causing me grief.

Just adding my voice to the howl in the wilderness: Yosemite 10.10.1 has not fixed my wifi disconnection issues.

The problem seems to affect me when ever I stop actively using my internet connection - as if being idle is what makes it disconnect; pausing between browsing or perhaps not having my browser window active. Difficult to tell.

Don't see how Apple can seriously address this if there is no crash report associated with the problem and no other way to let them know what my configuration is or anything.

On all versions of OSX up to the last version of Mavericks wifi worked seamlessly.

MacBook Pro (15-inch, Mid 2012)

Processor: 2.3 GHz Intel Core i7

Memory: 16 GB 1600 MHz DDR3

Graphics: NVIDIA GeForce GT 650M 512 MB

PS: hilariously wifi cut off while I was posting this, nearly lost the message

Update - all still ok after 9 hours & 2 sleeps (apart from occasionally having to switch from a BT wifi free connection back to my wifi.

Pez

When I upgraded to Mavericks originally, there were major Wifi issues that persisted forever. I ended up plugging in forever, which was fine because I was on an iMac then.

But now I'm on a MackBook Air, I'm up the creek.

With Apple, it seems that if you upgrade your software, you WILL have Wifi problems, so always stick to the original version your hardware came with.

I really hope this isn't done on purpose to "encourage" us to upgrade our hardware. Guess we'll know soon, whether they fix this or not. Can't be that difficult to fix surely?

I cannot believe that i spend 2500 to buy Macbook Pro and i cannot use the Internet for more than 1 minute. I have to disconnect and connect again to have one more minute. When I was using Maverick everything was Ok. Since I updated to Yosemite my WiFi became useless.

What a shame for a company who has $159.000.000.000 cash money, but they are not able to come up with a good operating system.

Apple are aware that 90% oh their customer don't know the existence of this forum.

So, why doing something.

So, maybe it's time to publish our frustration in Facebook, tweeter and other network.

I dont want to read some complicated solution in a forum, I want a solution from Apple. And a working solution.

I'm aware that making this post is completely pointless, but it feels like the only vaguely proactive thing I can do, so here goes: since upgrading to Yosemite, my 2012 MBP cannot maintain a stable WIFi connection for longer than 20 minutes. I've tried every "fix" reported anywhere and nothing has helped.  The 10.10.1 update actually made it worse. If Apple would even acknowledge the problem, I'd be (a little) less upset.  Their silence is frankly insulting.

Right. Again to no one in particular. Seems this here thread is kind of a mixed bag/ garbage can of all problems WiFi and some network issues thrown in too, under Yosemite.

Lots of workarounds seem to be useful, but only as useful as they were under former versions of OSX, so not 10.10.0 or 10.10.1 system specific. Known issues not specific to Yosemite are a.o. BT interference on the 2,4 GHz band, USB 3 broadband interference, especially on the 2,4 GHz band in particular with Mac Minis, simple bad WiFi connection due to the proliferation of users in your vicinity et al.

This thread appears to be about WiFi issues. Although it has repeatedly been stated the issues here are actually general networking problems. In particular: DNS resolving problems.

Could we please start searching along Yosemite specific clues here?

So lets try again: what exactly has changed under Yosemite? Could we try and think along these guidelines?

- Bonjour is running over AWDL now (with the latest hardware , even over 3 simultaneous network interfaces on iOS 8:

en0 — primary WiFi interface

ap1 — access point interface used for WiFi tethering

awdl0 — Apple Wireless Direct Link interface (since iOS 7?)

and who knows on Yosemite. Stopping AWDL services may be a relief to some, according to mariociabarra: https://medium.com/@mariociabarra/wifried-ios-8-wifi-performance-issues-3029a164 ce94

However, this is not a permanent fix, just a shrewd workaround for some. Beside the point for others.

- Airdrop Yosemite appears to be the first OSX app to have the same code kernel as Airdrop IOS. Check for errors here is called upon.

@rpetrich mentioned AirDrop used to be two incompatible, but identically named protocols until Yosemite/iOS 8. Perhaps this and the changes for continuity introduced bugs in this area.

- Some 3rd party routers may be better served with a separate network/SSID name for the 2.4 and 5 GHz bands, again according to Mariociabarra. On the other hand, some gear, including older Airport Expresses, may not. This is not Yosemite specific.

- ipV6 may not be properly implemented by your ISP. However, this is not Yosemite specific.

- DNSsec may not be properly implemented by your ISP. However, this is not Yosemite specific.

- Bonjour wake-up call seems to precede any DNS call under Yosemite, whereas before it was the inverse. To be investigated.

- Discoveryd has apparently replaced mDNSResponder. There seems to be a way of correcting this via command line by a white hat, please give him the benefit of the doubt; never mind his foul-mouthing either: IT people will be IT people. Thanx, Joedj, in the meantime go and wash your mouth with soap :-)

https://github.com/joedj/yosemite_dnsfix

just found this thread. Bought the Airport Extreme Time Capsule 2TB thinking I just needed a new router... I am getting crippling 1996 dial-up speeds on all our latest Mac and IOS equipment. After spending more than 30k in Apple products over the past year, I find it outrageous that such issues exist and are not fixed by Apple. PLEASE FIX !!!!!

I am in the same boat as you my friend.

I spent an hour on hold for a 10 minute phone chat with apple support regarding this issue.

Their ultimate position is that since it is reproducible on multiple devices, (MBP, iMac, iphone and Ipad) that it *must* be my brand new ASUS RT-AC87R router because by Apples definition any computer problem that is the result of something on their end would not be reproducible on multiple devices.

Even though ALL of my non apple devices (Ubuntu, Windows, Kindle, Android, Sony TV, Playstation, Xbox, D-link wifi camera and Yahmaha reciever) work just great with my router, it is apparently not an effect of anything on Apples end.

I love my MBP, but System76 makes just as good computers without having to deal with the suck factor of Apples arrogance.

I think my days in investing in Apple are about over.