[SOLVED] Network connected, but no internet

berndbausch · 01-01-2021, 01:07 AM

Quote:

Originally Posted by tofino_surfer

Actually the USB-C ethernet adapter may just not be plugged in.

Then lsusb would not list it.

tofino_surfer · 01-01-2021, 11:42 AM

Quote:

Then lsusb would not list it.

From the OP in post #11

Quote:

My wired interface is a USB-C ethernet adapter that I bought for one of my MacBook Pros a couple years ago. It seems to work just fine, but is obviously not a permanent part of the machine

When the adapter is attached, the output of lsusb lists this:

Bus 002 Device 003: ID 0adb:1853 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter

The OP stated that this adapter is plugged in only when needed and was not plugged in when they ran ls -l /sys/class/net.

To solve this misunderstanding the OP needs to plug the adapter in and then run ls -l /sys/class/net with it attached.

v00d00101 · 01-01-2021, 11:10 PM

I had a USB adapter that used that chipset and had to do two things to make it work. Get a driver from the realtek site then compile it and also I think I had to install some firmware using apt. This was on latest Devuan/Debian so YMMV.

https://www.pcsuggest.com/install-rtl8153-driver-linux/

Thats the site I used to deal with the driver.
The firmware package, I think was called firmware-realtek.

That got me the network adapter.

I then setup the adapter in /etc/network/interfaces

Code:

iface <devname> inet static
        address 192.168.0.100/24
        gateway 192.168.0.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 8.8.8.8 9.9.9.9

Setup /etc/resolv.conf with some public dns servers for testing with.

Code:

nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 9.9.9.9
nameserver 1.0.0.1
nameserver 8.8.4.4

Ran ifup <devname>
Then ping google.com

If it hasnt failed, you have working network capabilities.

<devname> is the name of your device, it might be enpxsx or similar, or eth0. You can also change the interfaces file to use dhcp if thats what you prefer. If your network uses a different ip/mask/gateway then change interfaces to reflect that.

rocketfuel · 01-02-2021, 02:21 PM

Quote:

To solve this misunderstanding the OP needs to plug the adapter in and then run ls -l /sys/class/net with it attached.

The output of the above command when the adapter is attached:

Code:

lrwxrwxrwx 1 root root 0 Jan  2 12:13 enxc05627f2a080 -> ../../devices/pci0000:00/0000:00:0d.0/usb2/2-1/2-1:1.0/net/enxc05627f2a080
lrwxrwxrwx 1 root root 0 Jan  2 12:11 ipv6leakintrf0 -> ../../devices/virtual/net/ipv6leakintrf0
lrwxrwxrwx 1 root root 0 Jan  2 12:11 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx 1 root root 0 Jan  2 12:11 pvpnksintrf0 -> ../../devices/virtual/net/pvpnksintrf0
lrwxrwxrwx 1 root root 0 Jan  2 12:11 wlp0s20f3 -> ../../devices/pci0000:00/0000:00:14.3/net/wlp0s20f3

It's the same if NetworkManager is running or if I run dhclient to get my wireless working.

Again, it seems to me that NetworkManager is prioritizing the two dummy connections that ProtonPVN set up, so that all other connections fail. If I can figure out a way to remove the dummy connections (as listed with "nmcli con"), I think I will be able to solve the problem.

Also, thank you again to everyone for the help. This is a great learning experience.

rocketfuel · 01-02-2021, 02:24 PM

Quote:

Originally Posted by v00d00101

I had a USB adapter that used that chipset and had to do two things to make it work.

The adapter has worked fine out-of-the-box in the past, so I don't think I need to do anything special to get it working again. ProtonVPN installed two dummy connections that seem to be prioritized over my adapter and wifi card, so I think that's where the problem is. Once I run dhclient, my wifi card goes to the top of the interface list (when listed with "nmcli con") and functions as expected.

tofino_surfer · 01-02-2021, 02:57 PM

The output of the above command when the adapter is attached:

Code:

lrwxrwxrwx 1 root root 0 Jan  2 12:13 enxc05627f2a080 -> ../../devices/pci0000:00/0000:00:0d.0/usb2/2-1/2-1:1.0/net/enxc05627f2a080

This is exactly what you should get with a USB Ethernet adapter. These are symlinks created by udev when the device is detected so it doesn't matter if your are using NM or not. Everything after the x is likely the MAC address.

https://access.redhat.com/documentat...e_device_names

berndbausch · 01-02-2021, 05:22 PM

Quote:

Originally Posted by rocketfuel

Again, it seems to me that NetworkManager is prioritizing the two dummy connections that ProtonPVN set up, so that all other connections fail. If I can figure out a way to remove the dummy connections (as listed with "nmcli con"), I think I will be able to solve the problem.

The command to delete a connection is nmcli con delete. Or remove the connection config files under /etc/NetworkManager/system-connections and nmcli con reload.

rocketfuel · 01-02-2021, 06:38 PM

Quote:

Originally Posted by berndbausch

The command to delete a connection is nmcli con delete. Or remove the connection config files under /etc/NetworkManager/system-connections and nmcli con reload.

Awesome, this worked! I did:

Code:

nmcli con delete <connection name>

and then

Code:

sudo service NetworkManager restart

and all is well! Thank you all so much for the help!!!