Q: OSX Yosemite Wifi issues

For those who are new on the topic, here are some fairy tales that I've tried:

• fresh install Yosemite
• defaults write com.apple.NetworkBrowser DisableAirDrop -bool YES
• disable bluetooth
• change wifi to WPA2 Enterprise
• sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
• Kext Utility IO80211Family.kext
• Change MTU number to 1453 (or any other number)
• Resetting PRAM

all ********

Macbook Pro on asus rt-ac87r 5ghz wifi

LOL!  Yep, tried them all, and more.  Couldn't agree more with you. This is BS from Apple.

Ivan Gotti wrote:

 

For those who are new on the topic, here are some fairy tales that I've tried:

 

• fresh install Yosemite
• defaults write com.apple.NetworkBrowser DisableAirDrop -bool YES
• disable bluetooth
• change wifi to WPA2 Enterprise
• sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
• Kext Utility IO80211Family.kext
• Change MTU number to 1453 (or any other number)
• Resetting PRAM

 

all ********

 

Macbook Pro on asus rt-ac87r 5ghz wifi

Cubism: Did you press the enter key after inputting your password? You should see a reply in terminal after you attempt to execute a command.

Doug

Yes, I pressed the enter key after entering password.  I just get the normal line returned to me after pressing enter:   MacBook-Air:~ cubism$

Is that the reply? As in no real reply?

DougGJoseph wrote:

 

Cubism: Did you press the enter key after inputting your password? You should see a reply in terminal after you attempt to execute a command.

SUCCESS!!!    So far... 12 hours and counting with solid WiFi.  I haven't mentioned earlier as too many of us think we have succeeded only to fail soon after. But since I have 12 hours of WiFI (previous bests in order were 3 hours and then 3 minutes x 1000 times) it's time to share my RIDICULOUS solution that I fluked. This has worked for me, but I don't dare restart my MacBook Air, or shift position in my seat. I hope I don't jinx things now.

What I did:

A friend came over and I vented a major hissy fit about Apple at him. He suggested I try using my mobile as a modem as a quick temp fix to send a big email, then he flicked out his Samsung Galaxy Note 2 and said, "Here, I'll do it."  So I tried to connect to his phone by WiFi and then he said "Why not try Bluetooth instead?" So I had both Wifi and Bluetooth enabled and then I just went "Feck it" since I was so hissed off and just closed the lid (as in slammed) and suggested we get a drink instead. (I did turn off Bluetooth first since I know that's a culprit) Geeze, long story...sorry.

So this morning I wake up and begrudgingly open the MacBook Air. And it works normally. For an hour. And I'm like wondering why. Eventually I look in the Network Preferences and on the left there under WIFi (but above Thunderbridgewhatever and Bluetooth) is this new thing with a TELEPHONE SYMBOL saying SAMSUNG MODEM, with "not configured" written underneath. The modem being my friend's mobile who is now 100 miles away.

That is the ONLY change to my laptop. Somehow THAT has interfered with whatever the problem is and I have a rock solid connection. Just ran a speedcheck--yep, 100% good.

Go figure. The moral of the story is invite you mate with a Samsung over for a drink and all will be good. Well, it was with me.

Good luck!

I'll let you know what happens when I restart the machine. If I dare!!! LOL

Is the system answer blank? I just get a blank new line.

cubism wrote:

 

Is the system answer blank? I just get a blank new line.

 

hexdiy wrote:

 

Sorry, Cubism, just back from work. yes, this is normal in Terminal: you get no feedback at all and the cursor is not moving while entering your password. You get a system answer, though.

Welcome to command line computing...

Indeed, you get a dollar sign (= prompt) and a blinking cursor.

Ha! Beats the old "turn it off, turn it on" mantra: just slam the f**cking lid!  

Having compiled a few wireless diagnostic reports does anybody know how I send these to Apple? The feedback section of Support doesn't allow me to upload a file

Cubism:

Below is a copy and paste from a Terminal transcript in which I issued a command, entered my password, and then got the system's reply before it returned me to a waiting command prompt. The first bold part is the command I gave. The second bold line is the system's reply. The last line is the command prompt. I am not 100% positive that the successful implementation of taking down of AWDL would give a reply in confirmation, but I'm reasonably sure there should be some type of reply.

Last login: Mon Nov 24 17:12:18 on console

Doug-i7-MBP:~ dougjoseph$ sudo ifconfig awdl0 down

WARNING: Improper use of the sudo command could lead to data loss

or the deletion of important system files. Please double-check your

typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:

ifconfig: interface awdl0 does not exist

Doug-i7-MBP:~ dougjoseph$

Thanks Doug, but I'm not touching anything else for now since I got a full day of normal WiFi performance yesterday without a glitch (I believe).

UPDATE  TO  MY  RIDICULOUS  WI-FI  FIX:

I'm happy to report that my "fix" (higher up on this page; re: using Samsung phone as modem) is still working like it should after restarting my laptop.

I admit it's a stupid and ridiculous method that makes no sense, but it did do something which has affected Wi-Fi transmission. I did NOT alter anything else. It's worth a try, because if you're like me, you tried everything else, so why not? You've got nothing to lose.

I'll update on things in another 24 hours, or unless things change, but so far (jinx, touch wood) all is good it seems. I have a workable laptop.

thanks man

With almost 1,500 replies to this thread, it is nearly impossible to comb through it all and sort out possible helps.

Is there someone knowledgeable who has a handle on what is likely to help, that could offer a summary of reasonable things to try? Perhaps a new thread of just solutions instead of affirmations of the problem?

After switching my router from channel 11 to 10, I can stay connected to the router, but the eternal "resolving host" issue and degraded performance are making for horrendous problems. Furthermore, those problems happen even when tethered via ethernet cable.

Note: I'm on a Macbook Pro (early 2011) and I went from Mavericks straight to 10.10.1

NEW UPDATE:

My WiFi was 100% yesterday for 12+ hours. Today I managed 11 hours before it had a brainfart and borked itself. I'm back enjoying 10-100 kbps again.

I knew it was too good to be true...and too flukey. BUT I've had a normal laptop for 24 hours, rather than a pathetic one that would only work for 3-min stretches.

Time for a gin. Double. Or three.

cubism wrote:

 

Thanks Doug, but I'm not touching anything else for now since I got a full day of normal WiFi performance yesterday without a glitch (I believe).

 

 

UPDATE  TO  MY  RIDICULOUS  WI-FI  FIX:

 

I'm happy to report that my "fix" (higher up on this page; re: using Samsung phone as modem) is still working like it should after restarting my laptop.

 

I admit it's a stupid and ridiculous method that makes no sense, but it did do something which has affected Wi-Fi transmission. I did NOT alter anything else. It's worth a try, because if you're like me, you tried everything else, so why not? You've got nothing to lose.

 

I'll update on things in another 24 hours, or unless things change, but so far (jinx, touch wood) all is good it seems. I have a workable laptop.

For what it's worth I have tried the fixes and no longer have a wifi problem. Unfortunately although I seem to get a good connection downloading periodically hangs. It restarts if I turn off and turn on my wifi. I now realise I have always had this problem. I have a 2011 iMac previously connected by Ethernet to 3 different routers and with 3 different ISPs.  Ethernet, wifi: Airport,  Netgear: Sky, talk talk: Mountain Lion, Mavericks, Yosemit. It just keeps getting worse and it seems to be something to do with DNS problems.

I'm getting by but  I think more and more that this may not be Apple's problem at all.  After all my Windowe Machine at work does exactly the same thing quite frequently. We all moan and blame our IT people!

I am like many who instantly saw what used to work perfectly before installing Yosemite, immediately stop working afterward.