Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Mavericks installed, now thunderbolt ethernet doesn't online after waking from sleep

Mid 2012 Retina Macbook Pro, 15 inch - as title suggests, after recently installing Mavericks from the app store + doing an upgrade install, the thunderbolt ethernet adapter no longer comes back online after the laptop wakes from sleep. System Information shows that the device is present and connected, it just won't bring the network interface up, so I have to disconnect + reconnect the adapter to get networking back up.


Wifi works fine, no problems there.


Anyone else encountered a similar issue?

MacBook Pro (Retina, Mid 2012), OS X Mavericks (10.9)

Posted on Oct 25, 2013 3:13 PM

Reply
79 replies

Jan 13, 2014 10:51 AM in response to TAMcHardy

Ok, this bug is starting to be a real pain. In combination with the bug at https://discussions.apple.com/thread/4959683 it is causing me nothing but headaches. None of the "solutions" for the network bug here have worked for me. Wake up the computer. Internet doesn't work. Find the laptop under my desk, pull the plug, plug it back in, go to send mail, mail does not work. Delete out all my mail settings and reset them back up and then send mail. Only to have to go through it all again next time I wake up the laptop. This in combination with synergy not working (which is not an apple problem of course) makes turning on the computer a chore, not a joy. This is the kind of thing that if I bought a new computer and found the network to not work, I'd be returning it the next day - regardless of the cause - something like this should be taken seriously. I have not enjoyed the new OSes simply because each one has implemented what in my mind is a major bug (mileage may vary if you don't use the feature). First with my mail, now with my network. Which wouldn't be so bad if they got fixed right away, but the mail bug has been around for almost a year, which after a couple of months with this bug gives me no hope of seeing a fix any time soon.

Jan 13, 2014 11:08 AM in response to angrypanda

Hi there Angry Panda

  1. Bad news: This happened today, so I didn't rebooted yet and don't know if is stable after a reboot. I have a lot of work to do this week, so I will not risk to reboot unti l I finished the important things and could relax about the time. Maybe I edit this answer next week 😝
  2. Next, before adding the Ethernet trough the Assistant, I deleted (Make a backup!) /Library/Preferences/SystemConfiguration/NetworkInterface.plist.
  3. Thunderbolt Ethernet Is not showed rifgh on Network, It appears as "Thunderbolt Bridge"


Good luck!

Jan 13, 2014 6:12 PM in response to andyfoo

Just as an update. The problem is still a problem. It comes and goes like the wind. Some nights i've just left my new MACBook Pro (Grrrrrr) it in it's broken state only to find that it's working in the morning. Other times it seems to awake after my wifi connection connects. But nothing is consistent. I've change my setting on IPv6 .. to no avail. Even switching to USB -ethernet worked immediately..


i'm not a happy MAC camper this year...


So my all important update is.... It's still broken and none of our workarounds seem to work around this problem.

Jan 19, 2014 3:26 AM in response to Carlos Mestre

Hi Carlos,


Just to be certain - your Wifi is turned off, and you are using a static IP address, not DHCP?


I'm really disappointed with this piece of hardware (mid-2013 Macbook Air) - not only is it incompatible with Marvericks (for me a stable network connection is a pre-requisite), but it also has a rather nasty habit of turning off the display when on battery and it not coming back on....see here: https://discussions.apple.com/thread/5475679?start=0&tstart=0


If this is a sign of things to come with Apple, I'm off.


Cheers, Jon

Jan 27, 2014 3:37 AM in response to Carlos Mestre

It most definitely is very painful. It seems to be worse with static IP rather than DHCP. And I experience the same issue with the external Apple TB/Ethernet adapter as well as the Ethernet port inside the TB display. It's not a specific adapter, it most definitely is a bug in the TB adapter driver that does not complete the same configuration steps upon wake as upon power-up or reconfigure. Hence the unplug/plug works. The only fix will be if the Apple devs get around to this bug (which I reported after the upgrade). I was hoping 10.9.1 would do it, unfortunately no luck.


While unplugging and replugging works, it's cumbersome. A *slightly* more pleasant work-around is to open the Network preferences, mark the adapter service as inactive, apply, then reactivate it. It comes back right away. Not sure if this could be scripted?

Jan 27, 2014 4:31 AM in response to allklier

Hi,


I had a quick look at details for 10.9.2 on osxdaily and it seems like there are a lot of graphics driver updates and also something for thunderbolt. Not sure if the penny has finally dropped for Apple, this should be top priority for them. Imagine if you'd just spent the best part of $4k on a laptop and cinema display and thunderbolt doesn't work properly!


Cheers,


Jon

Feb 8, 2014 8:37 AM in response to andyfoo

After all suggestions have failed for me so far, I'm attempting a new workaround, an improvement of mzago's hint (using a command line script to restart the network) that won't require any user interaction at all. This will require some techie skills and familiarity with the command line through Terminal.app. This is at or beyond my level of competence so I'll appreciate feedback here.


  • Install sleepwatcher, a utility that monitors sleep state and can execute commands when your computer goes to sleep and wakes up. It creates two hidde configuration files in your home directory that we will use momentarily.
  • Open Terminal.app and create a shell script as per mzago's hint. My file is /usr/local/bin/RestartThunderboltEthernet.sh

#!/bin/sh

sudo /usr/sbin/networksetup -setnetworkserviceenabled "Thunderbolt Ethernet" off &> /dev/null

sudo /usr/sbin/networksetup -setnetworkserviceenabled "Thunderbolt Ethernet" on &> /dev/null

Change owner and permissions as follows. The first changes the owner to root, the second runs the script *as* root but makes it executable by all:

sudo chown root:wheel /usr/local/bin/RestartThunderboltEthernet.sh

sudo chmod 4755 /usr/local/bin/RestartThunderboltEthernet.sh

  • As per Greg Hart's suggestion, add "<username> ALL = NOPASSWD: /usr/local/bin/RestartThunderboltEthernet.sh" to sodoers via visudo. This enables the script to be executed via "sudo ..." without having to enter a password.
  • Add the following to the .wakeup file in your home directory:

sudo /usr/local/bin/RestartThunderboltEthernet.sh


If this works properly, every time your machine wakes up the RestartThunderboltEthernet.sh script will software-toggle the ethernet interface automatically, essentially accomplishing the same thing as unplugging and replugging the adapter. Currently I'm having trouble getting .wakeup to execute properly. But I think a solution is within reach.

Feb 8, 2014 11:02 AM in response to Jeff Bailey

OK, I think I've got this figured out. I did two things: 1) eliminate the ampersands ("&") from the RestartThunderboltEthernet.sh scripts; we want the commands to run serially rather than backgrounded simultaneously; and 2) insert a 2 second sleep between them. The file now looks like this:


#!/bin/sh

sudo /usr/sbin/networksetup -setnetworkserviceenabled "Thunderbolt Ethernet" off > /dev/null

sleep 2

sudo /usr/sbin/networksetup -setnetworkserviceenabled "Thunderbolt Ethernet" on > /dev/null


Also it seems the .wakeup file installed by sleepwatcher only executes *one* line, so make sure that one line is "sudo /usr/local/bin/RestartThunderboltEthernet.sh".


This method seems to give my Thunderbolt ethernet enough of a poke in the ribs to wake it up.

Feb 16, 2014 3:07 PM in response to andyfoo

I can confirm the same, using the latest model MBP/Mavericks with Thunderbolt gigabit adapter set up with static IP loses network connection after sleep. Unplugging/replugging network cable brings it back online until the next sleep cycle. This is very troubling, I have always used static IPs in my network and I have never had network problems of any kind up until now, networking with OS X has always been a breeze. I have switched connection type back to DHCP (which has no connect/disconnect issues with the thunderbolt adapter) until problem is cleared up, hopefully in next Apple update. This was a necessary but dissapointing purchase of a $30 network adapter!


I also have a 2010 MBP (ethernet port on side) with a fixed IP that I recently updated to Mavericks; there are no disconnect issues whatsoever waking it from sleep.

Mavericks installed, now thunderbolt ethernet doesn't online after waking from sleep

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.