Mavericks Internet Sharing requiring restarts

Awesome I'm pleased that I have managed to help some people. Great news.

My connection has been rock solid since. I have never had to turn off and on again like I had to with 10.6 thru 10.8.

So Mavericks, except for being broken out the box, has solved the wifi sharing instability I had previously.

It seems to have worked for me, too. I just went in to the preferences and re-entered my wifi network password. Good to go.

Nothing fixes this issue but a restart... This is so frustrating. Shame on you Apple

Have you tried LBJ-UK's remedy? It seems to have worked for at least some people who were experiencing enough of a problem to ask for help on this forum.

I have the current 27 inch iMac and I have always been able to share my Ethernet connection over Wi-Fi to my smartphones, but since updating to Maverick, it no longer works. I have tried pretty much all the suggestions that I could find in many different forums online and still nothing works. My mobile phone is able to pick up the Wi-Fi signal but is unable to obtain IP address, it keep searching and searching until it fails.

I spoke to a senior Apple technician after two calls and he suggested to me that the Wi-Fi sharing is not meant to work with non-Apple devices like my Samsung smartphone, BlackBerry smartphone or my Windows laptop. He also indicated that there's nothing that they changed the good cause the Wi-Fi sharing not to work so he suggested that I contact the other companies mentioned above for a solution. He also stated that he doesn't see why I don't use my wireless router since I have one.

I'm not sure if he was not able to help or was unwilling to help but those suggestions were out of line in my opinion. So I have yet to resolve the problem. If anyone has any other suggestions we'll be more than happy to try them.

Within the last hour, I have had a Dell Windows XP laptop connected to the wifi signal from my iMac so at least some non-Apple devices will work with wi-fi internet sharing. As LBJ-UK's posts suggests, there seems to be an issue with settings not being properly carried forward when upgrading to Mavericks so it might be worth removing or deleting all relevant settings and re-enabling them. The ones that come to mind are wifi router SSID and wifi passwords, the SSID and password for the internet sharing wifi signal and the connection settings for your phones and other devices.

I tried pretty much everything mentioned in this thread including LBJ_UK's remedy. Nothing helps but a restart

I can't get internet sharing to work at all, at least not with other known SSIDs available. The machine simply connects to and stays connected to another AP instead of establishing its presence as an AP when I try to activate sharing on my MBP17-2013 w/10.9.

just restart and it works fine again.

Hello everybody,

LBJ-UK's solution didn't work for me, too. But I took a look into the console output and found the following errors after turning on connection sharing:

[...]

bind(bootps 67): Address already in use

error creating internal interface for devname bridge0@0: Address already in use

[...]

Issuing the following command revealed the process already binding udp port 67:

sudo lsof -i upd:67

Obviously bootpd already (still) uses this port. I assume this binding origins from a previous connection sharing which has not been properly shut down.

I tried to stop the bootpd daemon by issuing:

sudo /bin/launchctl unload -w /System/Library/LaunchDaemons/bootps.plist

But that returned:

launchctl: Error unloading: com.apple.bootpd

The lsof command issued previously revealed the process-id of bootpd, so I tried to kill that process:

sudo kill <process-id shown in the output of the lsof command>

Unfortunately that did _not_ kill the process. A brief check with lsof reveiled that bootpd is still running with the same process-id. I guess a simple "kill" command failes for the same reason as launchctl.

Because bootpd can not be shut down in a normal way I killed it "the hard way":

sudo kill -9 <process-id shown in the output of the lsof command>

A quick lsof afterwards showed that no process is now using port 67!

Now I was able to stop my connection sharing (I forgot to stop it before killing bootpd) and start it - and it works perfect again, without any reboot! :-)

I assume that there is a problem when the Mac enters standby mode with active connection sharing. It seems to fail to resume it properly afterwards. :-/

To quickly resolve this issue if it occurs again, I wrote a script containing the following line which automates searching the process id of bootpd and killing it:

sudo lsof -i udp:67 | grep bootpd |awk '{ print $2 }'| while read pid; do echo killing $pid; sudo kill -9 $pid&&echo "successfull..."; done

I hope this helps some of you!

regards,

Stephan

What a great job may I say! Works like a charm. Thanks a lot Stephan!

I had the same issue after a clean install of mavericks. Just ran disk utility and repaired my disk permissions. Everything seems normal again now.

bolste wrote:

sudo lsof -i udp:67 | grep bootpd |awk '{ print $2 }'| while read pid; do echo killing $pid; sudo kill -9 $pid&&echo "successfull..."; done

This worked perfectly for me, thanks!

This worked for me yesterday. Today the problem is back. DO I have to do this full dance every time I want to share teh internet on Mavericks?! Is there a fix that makes this problem go away once and for all?

In my case it's not necessary to run this commands every time I start internet sharing. It mostly ocurres after entering and resuming from standy whiile internetsharing is active. I doubt that there is a real fix for that, yet. Why don't you put all commands in a script and run it every time you have the problem. For your convinience you can put that script on your desktop so you don't have to start a terminal first.