Q: OSX Yosemite Wifi issues

But my connection work with others routers... Only with this one.

With a brand new MBP retina (2015) I was experiencing the problem of wifi drastically slowing when my bluetooth mouse was connected (bluetooth itself seemed not to be the problem, since I could run a speaker without the slowdown).  However, 10.10.3 appears to have totally solved my problem.  I installed as an upgrade yesterday, have put the machine through sleep and restart, and everything is solid.

How very right, WiFiGuru: the later I read reports in this thread, the more I get the impression right now it all has to do with network configuration in these latter days.

For WiFi, possibly some users have to update their (3rd party) router firmware (probably has to do with the Greenfield-Broadcom WiFi N preamble). Very probably some router manufacturers' firmware/drivers are not up to par yet.

For Bluetooth, there is no more excuse: either switch it off altogether or:

sudo defaults write /Library/Preferences/com.apple.airport.bt.plist bluetoothCoexMgmt Hybrid

As to wired Ethernet: there never has been an issue.

Hope this sums it up. Right now, 10.10.3, not before. 

I Found a solution - I reverted back to Mountain Lion ! No problems here. Guess ill wait for 10.11 - Apples 'California Dreaming' OS which will hopefully be as good as Snow Leopard / Tiger

Following up to  my own post here, because it seems most responders don't get the implications of 'penalty box'ing name servers.

Apple's discoveryd appears to be (almost) silently refusing to use any name server that is configured for only IPV4.  I have a very constrained home network where I only run IPV4, not IPV6, with a private V4-only dns service.   My private network name server, by design, does not answer AAAA requests since I don't support IPV6 on my NAT.  (I also don't do SRV records). This is all by design.

discoveryd/airportd connects to my network wifi bridge just fine, but then after a few IPV6 name queries puts my network DNS server in the "penalty box", I think this is because it doesn't see the answers IPV6 name records (AAAA queries in DNS-speak).

In other words, discoveryd will just STOP EVEN ASKING to resolve V4 names after a minute or two in an IPV4-only name service environment, because the V6 names it wants don't get answered.  With reference to other 'workarounds' that you might have seen; when you 'sudo killall -9 discoveryd' you get another timeslice before your name server gets thrown into the oven again.  Same thing happens when you turn the wifi off and then back on.   You get a new instance and a little more 'grace time'.  Other folks have mentioned 'turning off icloud'  as a work-around -- that might also be relevant here since the AAAA queries that seem to trigger the penalty box all end with 'icould.com'.

This, I believe, also explains why "updating your router to the latest firmware"  makes things better for some users -- if your old router firmware had poor or limited IPV6 capability an update can quite often improve that functionality.

This is moot in my case since I don't have a WiFi 'router' -- my network has a recent model wifi bridge with up-to-date firmware.

This discoveryd behavior is probably why some see random disconnects too.  I believe that discoveryd and airportd conspire to try and reconnect to a different network when they decide that "you aren't letting us do IPV6, so we have decided to penalize you."  I believe the wifi disconnects and starts going through every other SSID it sees when you don't have 'Ask to join new networks' checked, it just pretty much stalls when you do have that  option checked and it can't reach one of your other preferred networks.

You can argue that this is autoswitching is desirable behavior for the 'coffeehouse wifi' crowd -- I'll admit that.  I get very nervous when my equipment actively tries to escape my desired config and use some other potentially unknown and unpredictable network.

Is the the failure to provide an IPV4-only fallback behavior in discoveryd just a serious compatibility problem with discoveryd or a deliberate strategy by Apple to coerce use of IPV6, or both?  I think at the least it is disenfranchising a significant population of wifi users.

Wired networks work fine because, well, you can't unplug the wire, so you have to support fallback to IPV4 operation or just make the customer's link go dark.

SOME users yes. But the likes of me are using all Apple routers and all up-to-date. The main router is also brand new.

To those slandering Apple over this; think before you type. I have had this issue with every iteration Public Beta and Public Release since I first signed up for Beta which was when they started it. It originally Felt as though the Beta program was related to the cause. Specifically that the beta was flawed; how wrong I was. Although I find their lack of communication insulting you have to consider some things from their angle.

1. It's not in their interest to have this issue lingering like this. No benefit from deliberately causing or neglecting it. After all it's happening to new routers of their design and new computers of their design running their current OS. If anything it would look more like internal sabotage than conspiracy. This is a fault and that's that.

2. Just look at the huge range of side-effects and fixes. Things work for one and not another. The issue resides in a wide range of hardware and now OS and router firmware. This can't be an easy thing to fix. They might not even be able to reproduce the problem in-house and rely on us telling them if their "Fixes" worked or not.

3. They are not going to be able to do much with the information we provide here. This forum is for our use, not theirs. Presumably the forum is just a source of detection, toe in the water stuff. They will be relying on the logs we supply when we submit network feedback report. So send em in. Keep sending em in. Those entries will go into job lists, these won't.

I've never owned a mac before, only iPhone and iPad.. however last week i bought a new 27" imac.. im new to OSX but my first experiences havent been great and its mainly due to these two issues:

My iMac goes into sleep mode but i cant wake it up! i have to turn it off every time (i have now removed the sleep mode setting but this isnt ideal)

My Wifi seems to drop all the time, even though the mac can see my network at full strength?

I'm on a brand new mac, it's running yosemite 10.10.2

Should i return it? OR upgrade to 10.10.3?

Someone mentioned that i should get free support from apple with my new purchase, is this true?

I love the mac but these two issues alone make it unusable for me

Hi,

You have so many days to return it for a full refund. That return period depends on the retailer you bought your Mac from. You do have free Apple Care. Apple Care Plan gives you the free protection/support and lasts for a period of time. I believe it is 90 days or so, unless you purchased one of the extended Apple Care Plans. Cheers!

Andymaltby, CALL APPLECARE!  You will be amazed at how helpful and patient and knowledgeable they are!  I have been struggling with wifi issues and spent so many hours trying to sort it out. I should have called AppleCare. The advisor worked with me for an hour until we finally got it figured out. He even called me back a couple of hours later to make sure that our fix "stuck."  It is a marvelous service snd part of what you pay for when you buy Apple.

Just an update on my situation. The latest update (public release) did not fix my issue. I also tried turning BT off. That didn't help me. Not that I could bare to be without my BT mouse. Hmm. one of these days i'l have to unbolt my iMac from the wall and test it in the house instead of in my office.

I would respect this view if it was applied to Microsoft, as their OS has to support hundreds of hardware variants...Apple's doesn't.  Everything their OS supports they have manufactured themselves.  Checking that your new stuff doesn't break old stuff is called 'Regression Testing - perhaps Apple's doesn't extend beyond making sure that Tim Cook's and Jonny Ive's kit doesn't break.

And that is only what partly galls me about a issue that has existed for 6 months.

The other is, as you say, the insulting lack of communication from Apple on this issue - you'd think we had all asked for an iPhone 7 schematic, rather than an idea of when, perhaps, they may get to getting their software.

I am having the same problem with a brand new MBP 13". I thought that was the bluetooth but after testing removing the thunderbolts, the bluetooth and a usb hub it seems that the problem was caused by the USB Hub. So try to remove any usb devices and check if this is fixing the issue.

Great theory Trailsloth. I'll have to check out my router config to see if I set it for IPv4 way back when I originally configured it.

My Wifi has been faultless for over a day now except for one hiccup that lasted a minute or two. Perhaps my initial problems with it not functioning under 10.10.3 were due to disk encryption being underway?

Note I still cannot use Bluetooth and WiFi simultaneously though.

rMBP 15" Mid 2012

Aircard 760S set to default settings