Networking – Fixing ‘Ethernet Device Not Managed’ Issue

16.10ethernetnetwork-managernetworking

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  --

Best Answer

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
Related Question