32

I am using Ubuntu 16.10 and recently I have not been able to connect to internet using Ethernet. The network manager shows device not managed. The WiFi network is working fine.

enter image description here

enter image description here

I've tried the solution from this questionn Ubuntu 16.04 Ethernet issues with no use.

My /etc/network/interfaces file:

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

My /etc/NetworkManager/NetworkManager.conf file:

[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq

[ifupdown]
managed=true

Output of nmcli d:

DEVICE  TYPE      STATE      CONNECTION 
wlp2s0  wifi      connected  eduroam    
enp8s0  ethernet  unmanaged  --         
lo      loopback  unmanaged  --   
  • I see that "managed=true" did you change it from false to true? can you try to restart the service and see if it solve your problem: sudo service network-manager restart ? – Yaron Feb 13 '17 at 6:39
  • 1
    Yes, I have changed it from false to true. And I've tried that and it didn't help. – martin49 Feb 13 '17 at 6:40
  • please add the output of nmcli d to your question – Yaron Feb 13 '17 at 6:42
  • I've added it to the question – martin49 Feb 13 '17 at 6:45
63

The following bug in Ubuntu 16.10 might be related: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

First try running the following command:

sudo nmcli dev set enp8s0 managed yes

If you get the error message:

Error: Device 'enp8s0' not found.

Try running the command below:

ip link show

and look for a device name similar to enp8s0 and substitute it in the original command.


If the that didn't solve the problem, try running the following (backup orig file, and create 0 bytes file instead)

sudo mv /etc/NetworkManager/conf.d/10-globally-managed-devices.conf  /etc/NetworkManager/conf.d/10-globally-managed-devices.conf_orig
sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf  

@datka reported a different location for The file 10-globally-managed-devices.conf so the commands should be:

sudo mv /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf_orig
sudo touch /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf

The reboot, or restart the Network Manager service:

sudo systemctl restart NetworkManager

or the old way:

sudo service network-manager restart
  • 3
    The second option with creating the blank file worked! Thank you! – martin49 Feb 13 '17 at 6:58
  • 1
    @martin49 - happy to hear that it solve the problem :) – Yaron Feb 13 '17 at 7:02
  • 2
    The second option with creating the blank file worked! Thanks very much! – charybr Apr 6 '17 at 6:53
  • 8
    The second option worked for me too. However, the file 10-globally-managed-devices.conf was located in /usr/lib/NetworkManager/conf.d and not in /etc/NetworkManager/conf.d. – datka Apr 11 '17 at 7:28
  • 2
    Please note that this also applies to 18.04: askubuntu.com/questions/1036497/… – G Koe Jul 17 '18 at 19:23
28

In my case the 10-globally-managed-devices.conf just doesn't exist (from 16.04->16.10). All that is needed is to create it:

sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf

Followed by a restart:

sudo service network-manager restart
  • 6
    I also got this problem when I upgraded to 16.10 from 16.04. This answer worked for me, but I needed to restart Network Manager as well. sudo service network-manager restart – user399352 Apr 14 '17 at 22:16
  • 1
    Also a problem upgrading from 16.04 to 17.04. Cmon Ubuntu do better. Network errors are the worst. Thanks for the easy fix. Touch then [sudo service network-manager restart]. – moodboom Aug 30 '17 at 20:39
  • From answers on other questions, it may exist in /usr/lib/NetworkManager/conf.d/ --on my machine (18.04) it appears that putting the empty one in /etc/NetworkManager/conf.d/ will override that, and allow NM to manage the device. – jtniehof Aug 3 '18 at 12:11
1

Setting unmanaged-devices=none in {BASE}usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf worked for me in getting NetworkManager to manage the ethernet port, though I don't know if that messes anything else up. :^)

This was for a Ubuntu 16.10 hybrid USB build.

  • The only combination that worked for me was creating the file in /etc/NetworkManager/conf.d/10-globally-managed-devices.conf and then manually setting unmanaged-devices=none in the location you said. – tftd Mar 10 '18 at 4:05
  • Can you paste the full 10-globally-managed-devices.conf? I'm getting a Failed to read configuration: /etc/NetworkManager/conf.d/10-globally-managed-devices.conf: Key file does not start with a group error. – mpr Jan 14 at 21:48
  • The contents of the file should be (on two lines): [keyfile] unmanaged-devices=none – Jonah Braun Apr 8 at 0:53
1

While the advice to create an empty 10-globally-managed-devices.conf file worked for me, I found another way to fix this.

Calling nmcli, I noticed that my ethernet device isn't classified as one of the types (wifi, wwan) that are excluded from the unmanaged-devices clause, in contrast to the WiFi device, but as ethernet:

$ sudo nmcli 
enp0s31f6: verbunden to Kabelgebundene Verbindung 1
        "Intel Ethernet Connection I219-V"
        ethernet (e1000e), 54:E1:AD:FC:E1:22, hw, mtu 1500
        ^^^^^^^^
        [...]

wlp5s0: nicht verfügbar
        "Intel Wireless 8260 (Dual Band Wireless-AC 8260)"
        wifi (iwlwifi), 28:C6:3F:CD:A1:9F, hw, mtu 1500
        ^^^^
        [...]

Adding that type to the exceptions did work for me:

unmanaged-devices=*,except:type:wifi,except:type:wwan,except:type:ethernet
                                                     ^^^^^^^^^^^^^^^^^^^^^

Strangely enough, the original setting worked for me for more than 6 months, until I decided to clean out the packages installed on my system. However I can't tell if it was the device type or the file contents that have changed with that.

  • This seems to be a new(er) bug that (IMHO) should get reported. I noticed it on a stripped down Ubuntu 18.04 installation that had network functional before stripping it down. So I assume there is some package that masks this error in the configuration. – stefanct Sep 13 at 14:07

protected by Community Apr 14 '17 at 14:49

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.