Upon bootup the network connection appears to be connected, for several reboots, I was shortly able to ping However, I'm not longer able to do this. Then after logging in (<30 seconds) the network manager says the cable is disconnected. Unplugging and re-plugging the cable does not change this status.

The wireless connection is working.

I have previously used the wired connection in older versions of ubuntu (16.10 & 16.04) on this laptop, although I haven't tested them recently.

The network cable works with other computers.

The NIC device is a BCM5762.

Here is the output of ifconfig

    enp1s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 40:b0:34:09:9a:c0  txqueuelen 1000  (Ethernet)
        RX packets 91  bytes 54152 (54.1 KB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 146  bytes 32104 (32.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 36  
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet  netmask
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 294  bytes 23870 (23.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 294  bytes 23870 (23.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet  netmask  broadcast
        inet6 fe80::3260:ab36:9b89:9e58  prefixlen 64  scopeid 0x20<link>
        ether 7c:b0:c2:4e:13:d0  txqueuelen 1000  (Ethernet)
        RX packets 1247  bytes 1208923 (1.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 881  bytes 160559 (160.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Here is the output of lshw -C network

       description: Ethernet interface
       product: NetXtreme BCM5762 Gigabit Ethernet PCIe
       vendor: Broadcom Limited
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: enp1s0
       version: 10
       serial: 40:b0:34:09:9a:c0
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.137 firmware=sb latency=0 link=no multicast=yes port=twisted pair
       resources: irq:36 memory:e0820000-e082ffff memory:e0810000-e081ffff memory:e0800000-e080ffff
       description: Wireless interface
       product: Wireless 7265
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 59
       serial: 7c:b0:c2:4e:13:d0
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=4.15.0-23-generic firmware=29.1044073957.0 ip= latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:47 memory:e0d00000-e0d01fff

I had my network card get disabled after this morning's Ubuntu update. Rebooting the machine in Win10 the network card still works, so it's an Ubuntu configuration.

The way I solved it was the following:

sudo lshw -C network

This listed the "logical name" values:

logical name: enp8s0
logical name: docker0
logical name: enp0s29f7u7c4i2

I have a Dell T7400, so I know the device is a Broadcom NetXtreme BCM5754. Dell support provides no Ubuntu drivers, but you don't really need one. Somehow my ethernet device name was renamed.

sudo vi /etc/network/interfaces

Add the logical name to the end of the file:

auto enp8s0
iface enp8s0 inet dhcp

Finally, turn the interface on:

sudo ifup enp8s0
  • 1
    This did not work for me.
    – Andor Kiss
    Jan 26 '19 at 13:42
  • 1
    this worked for me, thx so much, I wonder if people at ubuntu are deliberately sabotaging themselves with this network renaming, it's enough to make me stop using it at work Jun 4 '19 at 8:30
  • 1
    The interfaces file and ifup are not in basic ubuntu 19. Feb 21 '20 at 20:22
  • 1
    Adding the interface file like that stopped it from being shown in settings. Feb 21 '20 at 21:01
  • 1
    Nevermind I figured it out. Now I just wanted to say something else. I did this and seemingly the situation got worse. Intead of the wired connection being there but 'just' not working it now was no longer there, or on closer inspection 'not managed'. However, by applying the steps in this answer: askubuntu.com/a/1043244/674732 I got everything back to normal again. So apparently the two answers together fixed the issue. Thank you both and I leave this here for future visitors.
    – Vincent
    Jan 25 '21 at 23:40

I tried the solutions above and they did not work.

What worked for me was disabling wifi using the network icon on the upper right corner of Ubuntu's GUI then restarting the network manager using :

service network-manager restart

I think that having a working wired connection cable that is plugged-in and a connected wlan card to a wifi network at the same time creates a conflict.

  • This helped, but now my wired connection shows as "Wired Unmanaged." Will try to find a full solution and report back.
    – bhass1
    Apr 15 '20 at 18:31
  • 1
    This helped, but it put my wired connection icon to show as "Wired Unmanaged." To solve this, I needed to follow the accepted answer here (askubuntu.com/questions/882806/ethernet-device-not-managed). Namely, find, backup, and replace the 10-globally-managed-devices.conf with a 0-byte file using touch. On Ubuntu 18.04 the file was located at: /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf
    – bhass1
    Apr 15 '20 at 18:39

Run old GUI


Then activate Enable Networking.

If it doesn't solve it, try running


to edit any weird configuration in the connections.

You can also see what the NetworkManager is doing with these commands.

# Run one by one to see if anything is useful
nmcli device


nmcli device show

if your network device says unmanaged, it means the NetworkManager will not try to use that device to connect.

Workaround to bypass the NetworkManager

Configure network with netplan

# Create a config file
sudo nano /etc/netplan/ethernet.yaml

and enter this

  version: 2
  renderer: networkd
      dhcp4: true

replace eno1 with whatever your device is (mine was ens33). To see your list of devices, run ip addr.

Finally apply the new configurations

sudo netplan apply
  • Worked for me...
    – Elder Geek
    Dec 29 '20 at 2:26

Similar problems here, this could be related to this bug or this bug in NetworkManager.

I work around this problem by using ifupdown together with ifplugd for detecting properly if a connector is plugged in the nic or not (I'm working on a laptop) and I have no connectivity issues anymore.


I had the same problem - my newly-installed Ubunut 18.04 wasn't detecting my ethernet connection for a second, though the led at the port was constantly blinking as if it were normal. I typed lshw -C at the terminal and among the output displayed there was no eth0 ( it refers to ethernet connection, no eth0 means no ethernet connection). I searched online and found out that the particular ethernet driver might be absent in Ubuntu.

I downgraded my kernel and ... spent more than two days feverishly trying to solve the problem.

The solution : I reinstalled Ubuntu 18.04 and that solved my problem. I don't know what went wrong in the first installation.


Had the same problem try:

sudo apt install ifplugd



Fixed it for me.


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