Mavericks upgrade wifi problem exclamation mark

Didn't work for me.

Ok guys hope that helps a bit but here is what has done the trick for me so far. First turn off and on my router. Then i ran a utility called applejack. Need to be done viasingle user mode. Ran it in automatic mode and it did pick up some corrupted files that were automaticaly removed. Everything has been stable after reboot for the last 4ish hours while the wi fi would drop every other minute before. Hope that helps

You seem to have a valid IP... Try an open DNS such as 8.8.8.8 see if that works. http://support.apple.com/kb/ph6373 (article is dated but steps still the same).

I have been using Applejack on my 10.6 and earlier machines for years and it fixes a world of hurt. But I didn't know you could install or use it in anything newer than 10.6, and the dev says not to use it at all. So since I love danger and am so desperate to find a solution to the WiFi problems since it doesn't look like anything will be coming from Apple, since it hasn't in years, I though I would force Applejack to install and try it. So right now I am in my Snow Leopard partition trying to fix the severely trashed Mavericks and ML partitions. When I tried to start up after running AJ, neither partition would boot. Nor would the Recovery volumes boot either. Things are just about done "repairing". In a few minutes I will be able to try to boot to Mvrx. And thing were working so well, except for WiFi. I should have left it alone. But as I said I was desperate.

Rebooted into Mavericks and the gear is turning . . . screen flicker and freeze. Had to force shut down and I noticed that my MBP is very hot. So I will let it cool a bit before trying again. So I guess the lesson is when the dev says not to use their app on something, don't. Oh, I have the partitions backed up to a pleasant point with both ML and Mvrx. So recovery is possible. Next I'm going to try what Gilbnx posted. Did I say I was desperate? And Mvrx was working so well, except for WiFi.

OK. One more time. Gear spinning . . . spinning . . . WE HAVE BOOT to Mvrx. It doesn't feel as solid as it was. And it's slow, very slow and no WiFi. Oh well, I'll never learn.

Posting from my 10 year old G4 FW800 Workhorse - 10.5.8

Roger, can you ping your router in this case when you see the issue ?

Try this:

sudo tcpdump -i en0 -s0 -v -w ~/Desktop/dhcp.pcap port bootps

and then reproduce the issue. Upload the dhcp.pcap and I can take a look and see if there is something obvious going on.

Running 15" 2012 MBPR, 10.9 upgrade is resulting in intermittent reconnect failures when waking from sleep. Vanillla build, ATT UVERSE 2WIRE 3600HGV WIFI-G Gateway with WPA2.

Can someone from Apple internal please log a ticket for driver failure in 10.9 on this model? Research indicates widespread failure. Suspect App Nap and en0 conflict.

Thanks you!

This is a end-user-to-end-user support forum, checkout http://getsupport.apple.com

Hi wifiguru

The router responds to pings when the ethernet cable is plugged in. With it unplugged, relying on wifi, the response is as follows.

Ping has started…

ping: sendto: No route to host

ping: sendto: No route to host

ping: sendto: No route to host

ping: sendto: No route to host

ping: sendto: No route to host

ping: sendto: No route to host

ping: sendto: No route to host

ping: sendto: No route to host

ping: sendto: No route to host

ping: sendto: No route to host

PING 192.168.1.254 (192.168.1.254): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

--- 192.168.1.254 ping statistics ---

10 packets transmitted, 0 packets received, 100.0% packet loss

Going to try your Terminal command now.

This is the response with ethernet plugged in.

familygeensimac:~ familygreen$ sudo tcpdump -i en0 -s0 -v -w ~/Desktop/dhcp.pcap port bootps

Password:

tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 65535 bytes

Got 0

This is the response with ethernet unplugged, relying on wifi.

Family-Greens-iMac:~ familygreen$ sudo tcpdump -i en0 -s0 -v -w ~/Desktop/dhcp.pcap port bootps

tcpdump: WARNING: en0: no IPv4 address assigned

tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 65535 bytes

Got 0

I'm not sure whether this is what you wanted, or whether it is of any help. I've also now updated my MacBook Pro to Mavericks and that is working perfectly well on wifi!

Miska - tried the open DNS as you suggested but no improvement with that.

Try the tcpdump -i command again but change it from en0 to en1 because en0 is your ethernet adaptor. You can also change the files name ~/Desktop/dhcp2.pcap.

Miska,

Problem is a layer 2 (data link) issue, not a layer 3 (Network) issue. Appreciate the goodwill though.

I spoted that and great use of the OSI model 😮... Now he mentioned router respondes when ethernet is plugged in but doesn't when it's unplugged... He's unable to go online with ethernet and wifi... What are the changes that both Ethernet and WiFi are having Layer 2 issues? That leads me to my next question... Are you able to go online with any other device in your network?

iOS devices are unaffected, only my Mac, and only after 10.9 upgrade is affected. I have a 15" MBPR so WIFI is en0 for me as I have no ethernet.

Ethernet, should, be unaffected. In my opinion, this is a compatibility issue between only certain routers, and the new drivers in 10.9 and certain Apple Laptop Models.

I need to run through my logs and find the failure. It's obviously a failure to reconnect due to logic bomb with timeouts (driver problem) or renegotiation failure with the WiFi endpoint. The questions becomes even when I find which, can I re-write driver code 🙂 I'm a sys admin, not a coder. I know this is a driver problem induced by 10.9, but helpless to fix it without some substiantial time investment 😟

You sound like you know what you doing, ff possible install perform a clean install of Mavericks on a different partition/drive and see if it works "out-of-the-box" that will cut hours of troubleshooting for you.

That worked for me too. MBP 8,3