Since updating to 10.9.2 last week, I've been experiencing issues when connecting via WiFi to my home network. I've constantly got to renew the DHCP lease manually in order to sort it out. My MBP picks up my network, but doesn't connect automatically when I wake it from sleep, even after a reboot. Anyone else had this problem with 10.9.2 ?
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: How frequently are you watching FIFA World Cup 2026 matches?
Mavericks 10.9.2 Update - WiFi Issues
- Thread starter shanezn
- Start date
DrJohnZoidberg
Honorary Master
My wifi seems to have improved. MBA 2013 model, used to have massive lag spikes because of the wifi, now seems to be good.
Did some digging on the Apple support forum, and it seems there are quite a few people with the same issue as me. Doesn't look like there's a fix yet, just work arounds, most of which I've already been using. Hopefully they address the issue in the next update.
koffiejunkie
Executive Member
I did have similar issues. Reset the pram and the other one (can't remember what it's called), and all was good.
![[)roi(]](/forum/data/avatars/m/8/8711.jpg?1563828683){kind=avatar}
I have no such issues on 10.9.2.
Also 10.9.3 is not targeted to address any WIFI issues; here's an extract from the 10.9.3 beta
If you're sure it's not related to your network kit and/or recent settings changes; then I think you're probably best off replacing your current WIFI kext with the 10.9.1 one; but only attempt this with a backup of both your Mac and your current kext. You can btw retrieve a copy of the older kext from a backup done on 10.9.1
/EDIT Resetting NVRAM/PRAM is not proven to work as this Apple note confirms : http://support.apple.com/kb/ht1379
Last edited:
SauRoNZA
Honorary Master
SMC I presume.
Been having similar issues with Wifi dropping on my 2011 MBP and then I switch it on and off to make it work again.
Resetting the NVRAM is the only way I could get my Mini (core duo) to connect to my network after a restart. It's running 10.6 though.
@OP - have you tried manually setting your IP instead of relying on DCHP?
I have. After a day or 2, it comes up with an IP conflict, and then I have to switch off WiFi and switch on again to resolve. I just switched back to DHCP, figuring it's less of a ball ache.
Have you been assigning an IP outside the DHCP range?
No, but I have used an IP that was pretty high up in the range. Even with the 3 iDevices and desktops, PS3 etc, there's no way for an IP conflict to have occurred. When turning WiFi off and then on again, I kept the same IP, and I don't get a conflict error, so not sure what's gone wonky and where.
Sounds like that could be your problem (or at least one of them).
OS X's behavior during IP conflicts is to try to source an alternate; and to disable when that fails.
Important: Your DHCP scope should specifically exclude all fixed IPs; Also check on the DHCP reservation timeout interval.
For central and documented control I'd recommend you look into assigning Fixed IPs based on either DHCP Client ID or Mac Address.
Then make sure that your dynamic DHCP address allocation pool is configured to exclude any addresses either hard captured, assigned via DHCP Client ID or Mac Address.
Last edited:
As luck would have it even resetting the nvram no longer works.
I'm going to have to get myself a USB wifi adapter.are you also having this issue? & also on 10.9.2?As luck would have it even resetting the nvram no longer works.
NVRAM according to the Apple note I included previously, shows WIFI issues cannot be addressed by a reset of this.
Last edited:
that sucks; what about Ethernet?
Also have you tried replacing your airport kext with a new copy; possibility for driver corruption?
Last edited:
koffiejunkie
Executive Member
As luck would have it even resetting the nvram no longer works.
I may also have deleted everything under ~/Library/Caches but I don't remember.