Mavericks upgrade wifi problem exclamation mark

This one time advocate of Apple "computers" is no longer an advocate, and I have to thank you all for warning us of what we can expect when we download and install what seems to be yet another failed OS from the once might Apple COMPUTERS.... On my new 128gig, Retina Display IPad everything worked perfectly, until the day I made the mistake of installing iOS 7. - Same happened when I upgraded to Lion on my IMacs... Suddenly half of the 3D software which I use for work no longer worked. Same for several games, etc...

Funny thing happened today. I awoke this morning and found that Apple's idea of a Christmas present was to give their valued customers (chuckle) a free upgrade to a failed and flawed operating system. Thanks a lot for "NOTHING"... I will pass. Fool me once shame on you. Fool me twice shame on me...

Not only has Apple lost my business and my advocacy, but my loyalty and my respect as well. As a professional graphic artist and 3D animator I've never owned a PC.... Never. - That will soon be changing, because this one time advocate will never again purchase anything made by Apple. (nothing)

Hope you all have a wonderful New Year!

Same problem here, MBP Early 08, no wifi problems previously, now with Mavericks I can't connect to my wireless network - my iphone, an ipad, other laptops work just fine with the network, it's just the older MBP that has the issue.

It sees the network, then gets the exclamation point, and the 'no internet conection' warning. It also seems to be in a constant 'looking for networks' loop.

I have tried every solution in this thread, and I'm giving up, nothing worked. Very dissapointing, this laptop still does a great job, and is awesome for travelling, though it'll be a lot less useful now it has no wifi capability. Hopefully this gets fixed in an OS update?

This fixed my problem aswell, and I am pretty sure that this will fix all DHCP issues relating to Wi-Fi connectivity after upgrading to Maverick! Especially if you are able to connect via a static IP.

Thanks Clemson Grad!

Now, if only someone can translate Clemson Grad's solution for those of us who are technological illiterates....

@Runnerr - Thank you and I am glad the solution worked for you.

On our MB since then we had no issues.

@ CB500X. Upon debugging this, i found that something was blocking the DHCP response coming back from the router. So i added new rule to firewall on MB to permit DHCP responses.

HEre is what i did. By a long stretch i am an expert on cyber security, I have no idea on why apple blocked this port.

I did the following

1. sudo vi /usr/local/etc/ipfw.conf

2. add the following (only the bolded part) add 00050 allow udp from any to any src-port 67 dst-port 68 in

3. Save the file, and reboot the MB.

If you still have trouble understanding, feel free to ask, and i will try to explain. The steps #1/2 just add a new rule to firewall.

Try the following, because you might not understand how to use vi properly:

1. Go to your terminal application

a. If you dont know how to run the terminal application, Press Command + Space

b. Type in Terminal in the spotlight search and run that application

2. Copy the following and paste it in the Terminal Application:

echo "add 00050 allow udp from any to any src-port 67 dst-port 68 in" | sudo tee -a /usr/local/etc/ipfw.conf

3. Hit Enter, you will be prompted for your password, type it in and hit enter

4. Reboot your system

I got:

tee: /usr/local/etc/ipfw.conf: No such file or directory

add 00050 allow udp from any to any src-port 67 dst-port 68 in

What next? Mvrx 10.9.1.

@TheGuyintheProjectionBooth

Can you verify if you have this file or not? Just open the terminal and check for /usr/local/etc/ipfw.conf

If it exists and you are familar with vi, i recommend you to follow the instructions i have. Give that a try.

Clemson, Thanks for the reply.

I tried your version of this "fix" a while back and got the same error. Since lately I have done some updates I thought what the heck, I'd try this again. With so many having success I was hoping for the same. Mine failed last Spring, came back mid Summer and worked fine until last December when it failed again.

Ran your request and got:

-bash: /usr/local/etc/ipfw.conf: No such file or directory

just as I have all along.

To everyone that is getting the ipfw.conf error you need to turn on your Mountain Lion firewall.

This is under Preferences->Security & Privacy

That said, if your firewall is not running then it is unlikely that enabling it and applying this fix will work.

I've been keeping a close eye on this issue for a while, becuase i was having the same issue. I've applied numerous 'fixes' and it does appear my connection is stable. Not sure what fix solved it though.

However, what I still continue to struggle with is the really poor range of the wifi. I work fine when my Mac is located in my study, but if I move to the lounge (no more than 20ft) then the connection becomes so ropy as to be almost unusable. It doesn't matter if I go 2.4ghz or 5ghz, speed drops to 14mb/s and everything stops.

My windows laptop retains a good strong connection, as does my iPad and iPhone.

Anyone else seeing range issues more so than stability issues?

Firewall is on and has been.

I've made an app to fix the Wifi issues in Mavericks if you care to give 10.9 a try again: gum.co/PingFixer

Kevin

Hi Kevin,

What exactly does your app do?

I'm juding by the name it's just some kind of keep alive ping? It probably won't fix my issue which is related to poor range.

Andy

Andy, you are right. This does not help with range issues.

The app:

1. Discovers the router IP address.

2. Pings the router every .2 seconds.

Kevin

Fix now available on the Apple App store:

https://itunes.apple.com/us/app/pingfixer/id808479246?ls=1&mt=12#