![]() The grep and cut commands extract some handy feedback (the time taken if the DNS request succeeds). ![]() ![]() The dig +tries=1 +time=3 command does the lookup, waiting 3 seconds for an answer.You can click on the image below for a text version to copy-and-paste to use yourself:Īll it does is try a DNS lookup every five seconds, and turn the Wi-Fi Network rapidly off and back on if no reply is received within three seconds. I’m a hacked-together shell script, run with root privilege using the sudo command. I’ll open the batting with my effort, which is by no means a fix, and isn’t even a workaround: it really is a bodge, plain and simple. We’re not going to blame Yosemite yet, but we are turning to the Naked Security community for fixes, workarounds or even bodges.īut not just any old bodge: you have to come up with a plausible explanation of why you think it works, and why other people should try it. ![]() Occasionally my network will stay up for close to 10 minutes, which feels like success if you’re used to getting cut off every three minutes or so.īut even if 10 minutes of uptime feels like a good result, it still counts as failure compared to how things were under Mavericks, with Wi-Fi connections lasting flawlessly all day (and night) long. 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.
0 Comments
Leave a Reply. |