Indeed, many of them seem to have proclaimed success very quickly after making the change, so they may have spoken too soon. “Fixes” that I’ve seen include: forgetting all your Wi-Fi networks and entering your password again using the 2.4GHz range only and avoiding 5GHz turning off Bluetooth and even wiping your disk and reinstalling Yosemite afresh from a USB key.īut removing all my networks and starting over was my first reaction (it didn’t help), I never have Bluetooth turned on, I’m not using 5GHz on my access point, and others have done complete reinstalls to no avail.Ī few people have reported, “Hey, that fixed it for me” in each case, but almost none of them mentioned how long they waited to see if the trouble would return.
No such symptoms were observed before updating to Yosemite. You rarely get more than about three minutes between meltdowns. Meltdowns don’t seem to recover on their own. Wi-Fi network meltdowns happen repeatedly. What we knowĪll we know is that for those of us who are affected: That’s Latin for “X happened after Y, therefore Y caused X,” and put in those terms, it’s clearly a misleading and risky form of reasoning. So far, many of us seem to be grasping at straws, following a support technician’s worse nightmare of logic: post hoc ergo propter hoc. The problem with these fixes is that it’s hard to be scientific when you don’t have any information about what has changed, and what might be the cause. User forums and Apple’s own Support Community have plenty of discussion of this issue, and numerous proposed “fixes”. So you can’t use DNS (the Domain Name System that tells you is actually at 31.222.175.174), and even if you knew Sophos’s IP number already, you wouldn’t be able to connect to it anyway. The network shows up as active, and low-level packets such as PINGs can be sent and received as normal.īut traffic such as UDP and TCP just doesn’t get through. Your network works fine for a while, typically between about 30 seconds and five minutes, and then fairly abruptly begins to suffer almost total traffic loss. The symptoms are varied, but the most commonly reported problem is pretty much what I’ve experienced since first rebooting into OS X 10.10 and going online wirelessly. Yosemite itself could have introduced a bug or your hardware might be affected by a reliability problem that simply didn’t show up before or some third-party software might be revealing a latent flaw. 
No-one seems to know what’s wrong, and without a scientific explanation it’s hard to know where to lay the blame.
In fact, many of you will have updated already.īut even if you don’t have a Mac, or are sticking with the five-year-old Snow Leopard release (OS X 10.6) for legacy reasons, you may have seen or heard the growing disquiet about Yosemite and Wi-Fi. If you’re a Mac user, you’re probably thinking of updating to OS X 10.10, better known as Yosemite.
0 kommentar(er)
