-
All replies
-
Helpful answers
-
-
Nov 24, 2014 3:49 PM in response to cubismby cubism,UPDATE: Got to 90 mins and then wifi borked again. Streaming music from cloud at same time helps, but not forever.
-
Nov 24, 2014 4:06 PM in response to cubismby therealikt,Yeah I could see that, maybe it died at 90 minutes because the app requested a 90 minute inactivity timeout? Sirius does that.
However, this is a pathetic work around, and I cannot imagine what my ISP bill would look like. How would I explain that I streamed a terabyte in music I wasn't listening to, so I could get emails?!?
I don't mind a few bugs, but the problem here is that, even to the non IT type-it is clear that OSX Yosemite was either:
a) not thoroughly tested
b) intentionally released with an insane amount of bugs, to the point that the computer becomes unable to function, in order to release as promised to shareholders for 2015
c) Apple is incompetent.
Given that option "a" is not likely, and option "C" is certainly not true, it looks like option "B" is the culprit.
I think a lot of the consumer rage is tied to the fact that our computers have been wrecked so that billionaires can make more money off of Apple stocks and hitting the release dates.
-
Nov 24, 2014 4:53 PM in response to tomstephens89by emovere,I have issues as well on my Macbook Air 11 2013.
10.10.0 works awesome. Since 10.10.1 I have sometimes WiFi connections drops and I have to wait 20 Seconds after every restart to find my WiFi Station in the Wifi Section of OS X Yosemite. (Found 5 stations instantly, found over 15 after 20 seconds, on os x 10.10.0 it has found 15 instantly)
-
Nov 24, 2014 8:01 PM in response to therealiktby cubism,By coincidence, i was doing a speedtest and WAS getting normal speeds (hooray!), and then I actually watched it peter off after 10 seconds and dwindle down to the dragging days of dial up speeds.
There doesn't seem to be anything that makes any sense with this issue. Can't believe it dropped right in front of my eyes. I have NO idea what this wifi issue is now.
I give up. MacBook Air about to hit the wall.
-
Nov 24, 2014 10:36 PM in response to cubismby tyzlor,Hi guys
My two cents worth - after doing loads of debugging on both my MAC and our WiFi network.
1) The wireless connection on my MAC does not actually "disconnect" - it loses its IP address for some strange reason. (Gets the 169.254.x.x DHCP)
- I can still do things like MAC Telnet (Mikrotik routers support this) and ARP lookups
- This is isolated to AC based wireless networks - my 2.4Ghz network does not have any issues at all. It would seem the issue may be in switching from 5Ghz to 2.4 Ghz.
- AWDL might be an issue.
2) Our WiFi controller does not show any disassociation for my MAC's mac address nor any type of roaming.
- Using Ubiquiti Unifi with AC based APs
3) our DHCP server does not show any disassociation at all for my IP address.
- Standard wireshark debug shows this on the network + on DHCP server debug log.
--
Yosemite WiFi Issues Fix
This issue with D2D/AWDL is the same root cause of the severe WiFi performance degradation affecting users on Yosemite (continues on 10.10.1). Although AirDrop was introduced in OSX Lion and used AWDL.
Turning off AWDL
You can fix your Yosemite WiFi issues, at the cost of disabling AWDL and AirDrop, by typing the following command at the OSX terminal:
sudo ifconfig awdl0 down
And vice versa to restore AirDrop and AWDL (and the WiFi issues)
sudo ifconfig awdl0 up
For clarification: that’s “a w d (lowercase L) (number zero)”
--
Maybe try the above - not sure if it will work for you. Thanks to https://medium.com/@mariociabarra/wifried-ios-8-wifi-performance-issues-3029a164 ce94
for the ideas.
I have debug logs and also loads of head banging against wall available to anyone who wants them.
What are the thoughts on disabling the 5Ghz radio ?
Regards
--M--
-
Nov 24, 2014 10:51 PM in response to tomstephens89by souko.vue,My wifi's 2.4Ghz works fine, however using 5Ghz band I constantly get disconnected. I tried many of the recommended methods and none worked for me. I even swapped out the airport card with an earlier version airport card and same problem. Finally, the following worked for me:
STEPS
1. Click on Finder then press Shift + CMD + G
2. Type in /System/Library/CoreServices/Applications
3. Open Wireless Diagnostics.app.
4. Once open, press CMD + 2 to bring up Utilities Window.
5. Click on Wi-Fi Scan
6. At the bottom-right corner, hit Scan Now.
The app will suggest best 5 Ghz Channels. In addition, the app can also collect and view your wifi's log.
For reference, I have a:
Late 2013 Macbook Pro Retina
2.0Ghz i7
250GB
8GB
AirPort Extreme Broadcom BCM43xx 1.0 (6.30.233.154.65)
The app recommended channels: 36, 40. I went into my router's 5Ghz settings and set the channel from auto to 36.
Now, it connects instantly. No more long delays trying to connect or drops.
I will report back if the problem returns.
-
Nov 25, 2014 1:10 AM in response to tomstephens89by isvana,Interesting to see WiFi diagnostics report a problem with accessing DNS (on my MBP on work 2.4GHz network) as well as WiFi channel contention... as an update to my earlier post I've seen some much longer periods of connectivity (up to 3 hrs) and shorter (fails immediately) with 10.10.1. No (discernable) problems on the home or MiFi networks (still).
Clearing the SMC may or may not have had an effect (ref http://support.apple.com/en-us/ht3964) - still failed after this.
Now trying the awdl switch...
-
Nov 25, 2014 2:23 AM in response to isvanaby isvana,Quick update - no, turning off awdl did not improve matters for me
-
Nov 25, 2014 3:35 AM in response to tomstephens89by GerryGrant,It seems to me the problem slightly changed with the update.
Before the update:
- occasionally, the Wifi-Connection dropped completely
-> Wifi-Symbol went grey
- from time to time, The Wifi-Connection stayed, but no data could be transferred
-> The dropbox-icon went grey but the Wifi-Symbol stayed Black
After the update
- The Wifi connection stayed but no data transfer possible
-> Wifi symbol stayes Black
-> Dropbox symbol stayes Black
-> occurs almost every couple of Minutes
-> disabling and reactivating wifi helps for another couple of minutes
MacBook Pro (Retina, 13-inch, Late 2012) & Telekom router
-
Nov 25, 2014 3:38 AM in response to tomstephens89by PFJ30,If anybody is having this problem "invalid password" with a dual band wireless router (in UK I am using BT Home Hub 5) it seems that renaming the 5GHz SSID differently to the 2.4 GHZ may be an answer... It's working for me at the moment. RESTART the hub afterwards.
This from BT back in 2011!!
The BT Home Hub 4 and Hub 5 are dual band with two wireless frequencies for devices to connect to: 2.4GHz and 5GHz. On both Hubs, the default setting has the same network name (or SSID) for both the 2.4GHz and 5GHz bands. Connecting a typical 5GHz-capable device to this single SSID will automatically connect the device to both the 2.4 and 5Ghz frequency at the same time.
However, not all dual band devices behave the same way and some device software does not cope well with a single SSID for both frequencies.
As a result:
- the device may not connect wirelessly to the Hub
- it may not connect to 5GHz frequency even in the same room
- the wireless connection might be intermittent
- the wireless connection might be very slow
Devices where there are known to be problems include:
- Some Apple devices including iPhone 5 and Apple TV
- some Android smartphones
- Xbox
For some devices you can solve this problem by having different network names (SSIDs) for the 2.4GHz and the 5GHz bands. To set this up, follow these steps:
- Open your web browser on a device connected to the Hub and go to bthomehub.home. This will open the Hub Manager
- Click on Advanced Settings and enter your Hub admin password when prompted. Unless you've changed it, you'll find the default Hub password on the Hub settings card
- Click on Continue to Advanced Settings
- Click on Wireless
- Click on 5GHz
- Change 'Sync with 2.4 Ghz' to No
- Change the 'Wireless SSID' to a new name (we recommend just adding '5GHz' to the end of the existing SSID name so you'll know which one is which)
- Click Apply to save the changes
After a few minutes you should see two BT Home Hub SSIDs in the list of networks on your device. All of your devices will still automatically connect to the original SSID name, which will be the 2.4GHz.
If you have existing dual band devices you want to connect to 5GHz only, you'll need to connect them to the 5GHz SSID that you've renamed.
Note- Even though wireless speeds at 5GHz can be significantly faster than 2.4GHz, the range of a 5GHz connection is not as good. As a result, you may need your device closer to your Hub (than you'd need to when using the 2.4GHz SSID) to get the best performance possible.
-
Nov 25, 2014 4:06 AM in response to cubismby KathrynG,The bit that I don't get, is that I lose internet connectivity even when I am not using wifi and using an ethernet. That really has started to make me wonder what the real problem is. Resolving host! If I see that error message once more I am going to just go stark raving mad - half way there already.
There are also way too many bad reports and articles on the failure of the 10.10.1 upgrade as well, so rather than jump from the frying pan into the fire, I am just going to wait this one out. But at this rate, I might be long gone from this planet by the time Apple are ever able to fix this. Will have to have a chat with Steve Jobs of we end up in the
-
Nov 25, 2014 4:21 AM in response to KathrynGby KathrynG,The bit that I don't get, is that I lose internet connectivity even when I am not using wifi and using an ethernet. That really has started to make me wonder what the real problem is. Resolving host! If I see that error message once more I am going to just go stark raving mad - half way there already.
There are also way too many bad reports and articles on the failure of the 10.10.1 upgrade as well, so rather than jump from the frying pan into the fire, I am just going to wait this one out. But at this rate, I might be long gone from this planet by the time Apple are ever able to fix this. This is beyond ridiculous, and while it is true that the upgrade to Yosemite did not cost anything and therefore I imagine (not a lawyer) one cannot legally claim restitution, I suspect that since the instruments that we all bought in good faith and expect to work barring mechanical failure, are no longer doing so as a result of Apple's failure to provide a functioning operating system, there has to be a loop hole somewhere that says fix this Apple or pay up! And if fixing this just means giving consumers the option of returning to Mavericks, so be it. That would work for me, I just want to be able to earn my living.
Well well... tried to save this post and received an error message from Apple saying that the post was unable to be saved, and that maybe I had been logged out - ya think! (I was not logged out.)
-
Nov 25, 2014 4:25 AM in response to KathrynGby PFJ30,There a lot of experienced user s on here who say they always sit out the first two upgrades on every OS release..
Mad as it makes you one does have to smile when people come in and say "Why can't I get back to Mavericks - it just worked!" but in its day it was one the worst received OS releases..
I am retired and mainly use my MBP on ethernet anyway so am not tearing my hair out but it must be awful for people who need their MBP mobile for business.
-
Nov 25, 2014 7:02 AM in response to PFJ30by KathrynG,But that's one of the problems PFJ30, my iMac is connected to my U Verse RG via ethernet, and it still drops connectivity. For the past two days I have had to switch the wifi on and off repeatedly and virtually every minute to try to grab a connection for even that one minute. I tried to upload some printer files to Dropbox last night and it took me two hours to do it, because the signal kept dropping. I never had a problem with Mavericks. I know some people did, but everyone here was fine.
Even submitting these posts, I have to copy the message to my clipboard just to be safe, and then reload the page after having turned the wifi icon either on or off, depending on what position it was in, because in the time of writing this the signal dropped again. That is just not right.