If you go down the route of completely disabling and re-enabling the adapter, be aware that this can occasionally result in the adapter being stuck on disabled until the machine sleeps and wakes again (there are bound to be ways to avoid this but I moved to the manual address method instead). The underlying cause seems to be some of the services or settings related to the ethernet adapter are not re-enabled after wake, it's possible if you could work out exactly what needed to be reenabled and do just that instead of my rather brute force solution.
The exact procedure might vary depending on your connection and environment. Networksetup -setmanualwithdhcprouter ethernet $INITIAL INITIAL= networksetup -getinfo ethernet | grep IP address | cut -d ' ' -f 3 Sleepwatcher uses a file in /etc that is read basically as a script, the current one we are using is along these lines. It does cause a couple of seconds delay before you can login after waking, but it always fixes the issue. We got around the problem by using sleepwatcher (third party launch daemon) to fix it after every wake.Ĭurrent implementation is to have it swap the adapter to manual+DHCP and then back to full DHCP.
This seems to be a pretty common bug in 10.9 all our machines do it.
