Ethernet connected but cannot connect to internet

SheepYY039 · 28 May 2022 11:14

After a reboot yesterday, my internet stopped working. I have tried a lot of solutions online, but after the whole day, it is still not working. I have tried switching users, but it does not work for both users. Additionally, network runs well on my boot USB, so it shouldn’t be a problem with my net card.

nmcli connection show

NAME                          UUID             TYPE        DEVICE 
br-4bc4667df2e7      [a bit long to type]     bridge    *same as NAME*
br-4daaa69d574d                               bridge    *same as NAME*
docker0                                       bridge    *same as NAME*
enp2s0                                        ethernet  *same as NAME*
Wired connection 1                            ethernet        --

journalctl -fu systemd-resolved.service

[the time] [hostname] systemd-resolved[10287]: Using degraded feature set UDP instead of UPD+EDNS0 for DNS server 208.67.222.222
... Some more similar messages
[the time] [hostname] systemd-resolved[10287]: Failed to send hostname reply: Transport endpoint is not connected
... repeats

/etc/NetworkManager/NetworkManager.conf

[main]
plugins=keyfile
[device]
wifi.scan-rand-mac-address=no

/etc/NetworkManager/conf.d/20-rc-manager.conf

[main]
rc-manager=resolvconf

/etc/NetworkManager/conf.d/99-dont-touch-my-dns.conf

[main]
dns=none

System info:

Realtek RTL8125 2.5GbE
Driver: “r8169”
Driver Modules: “r8169”

Sorry if I gave too little input, since I cannot connect to the internet, I have to type the output from my laptop. Feel free to ask for other output, I will be willing to type them if they could be helpful to solve my problem!

Thanks in advance.

Edit 1:
I have found that there should be network, but it is like less than 1KB/s, so it barely works. When I try pamac install linux515-headers, it outputs Temporary failure in name resolution of all of my mirrors. I then try sudo pacman-mirrors --fasttrack, then the output is WARNING https://repo.manjaro.org/ 'Connection: HTTPSConnectionPool(host='repo.manjaro.org, port=443): Max entries exceeded with url: / (Caused by NewConnectionError('urllib3.connection.HTTPSConnection object at <0x7f0dd0d15e70>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))'

Is this a problem with DNS Configuration? If so, how do I fix it?

winnie · 28 May 2022 23:42

Right off the bat, can you ping 8.8.8.8 ?

ping 8.8.8.8

SheepYY039 · 29 May 2022 03:05

Thanks for responding! No, I cannot ping 8.8.8.8 nor can I ping my router ping 192.168.3.1, nothing responses and all packets are lost.

winnie · 29 May 2022 03:17

Not a DNS issue then.

But it looks like you’re using custom network configs (which might explain why your networking is without any issue with a live USB environment.)

I’m assuming you created those custom files a while back, and it only stopped working now? Was this the first reboot since the Pamac updates?

You might also get better results if you use the r8168 driver instead.

But since you say everything works with a live USB session, it makes me suspect there’s a system-side configuration problem.

SheepYY039 · 29 May 2022 03:53

Well, if I understood your question correctly, you mean the reboot that started causing network issues? That’s on the day before yesterday.

Okay! How can I install the r8168 driver without internet? Can I install it on another PC, and use a USB to copy it across? If so, how should I do it?

winnie · 29 May 2022 03:56

I don’t think that’s the culprit (just an idea for future reference, for those who use a certain family of Realtek chipsets.)

But this seems worth noting.

Maybe check these logs instead:

journalctl -fu NetworkManager.service

SheepYY039 · 29 May 2022 04:08

journalctl -fu NetworkManager.service

device (enp2s0): Activation: successful, device activated.
device (enp2s0): carrier: link connected
device (enp2s0): carrier: link connected
device (enp2s0): carrier: link connected
manager: (vethfd775f6): new Veth device (/org/freedesktop/NetworkManager/Devices/301)
manager: (veth26bbf31): new Veth device (/org/freedesktop/NetworkManager/Devices/302)
device (veth26bbf31): carrier: link connected
device (br-4daaa69d574d): carrier: link connected
manager: (vethfd775f6): new Veth device (/org/freedesktop/NetworkManager/Devices/303)
device (veth26bbf31): released from master device br-4daaa69d574d
manager: (vethb3d091e): new Veth device (/org/freedesktop/NetworkManager/Devices/304)
manager: (veth3e8b999): new Veth device (/org/freedesktop/NetworkManager/Devices/305)
device (veth3e8b999): carrier: link connected
device (br-4daaa69d574d): carrier: link connected
manager: (vethb3d091e): new Veth device (/org/freedesktop/NetworkManager/Devices/306)
device (veth3e8b999): released from master device br-4daaa69d574d
...

it continues until org/freedesktop/NetworkManager/Devices/324 currently

Keruskerfuerst · 29 May 2022 05:23

What gives the output of ip a ?

SheepYY039 · 29 May 2022 09:14

Just now I was trying to transfer the output of the command ip a to my laptop, and I realized that my Bluetooth also seemed to be not working. I am not sure if it is related to this issue, but I have also included some information below:

systemctl status bluetooth.service

systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

~~and running bluetoothctl just outputs~~

Waiting to connect to bluetoothd ...

~~Also, opening the bluetooth manager GUI results in a popup window~~

Bluez daemon is not running, blueman-manager cannot continue. This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started.

~~For your information, I am using a Bluetooth Adapter USB.~~

I was dumb, and to re-plugged the Bluetooth USB, and Bluetooth was back

Anyways, the output of ip a is

1: 1o: <LO0PBACK, UP, LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 br 00:00:00:00:00:00  
    inet 127.0.0.1/8 scope host lo
       valid lft forever preferred lft forever
    inet6 ::1/128 scope host
      valid lft forever preferred lft forever
2: enp2s®: <BROADCAST, MULTICAST, UP, LOWER UP> mtu 1500 qdisc fq codel state UP group default qlen 1000
    link/ether 2c:f0: 5d:cb:89:92 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.39/24 br 192.168.3.255 scope global enp2s0
      valid ft forever preferred lft forever
4: docker®: <BROADCAST, MULTICAST, UP, LOWER UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:a9: fb:46:ac brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 br 172.17.255.255 scope global docker®
      valid ft forever preferred lft forever
    inet6 fe80:: 42: a9ff: fefb:46ac/64 scope link
      valid ft forever preferred ft forever
5: br-4bc4667df2e7: <BROADCAST,MULTICAST, UP, LOWER UP› mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:a9:7d:6d:52 brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 br 172.19.255.255 scope global br-4bc4667df2e7
      valid lft forever preferred lft forever
    inet6 fe80:: 42:a9ff: fe7d: 6d52/64 scope link
      valid lft forever preferred lft forever
6: br-4daaa69d574d: <NO-CARRIER, BROADCAST, MULTICAST, UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:ce:2f:01:1e brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 br 172.18.255.255 scope global br-4daaa69d574d
      valid lft forever preferred lft forever
    inet6 fe80:: 42: ceff: fe2f:11e/64 scope link
      valid ft forever preferred lft forever
8: veth628f7d50if7: ‹BROADCAST,MULTICAST, UP, LOWER UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether 8e:52:8d:65:92:43 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80:: 8c52:8dff:fe65:9243/64 scope Link
      valid lft forever preferred lft forever
12: veth67644eedif11: <BROADCAST, MULTICAST, UP, LOWER_UP› mtu 1500 qdisc noqueue master br-4bc4667df2e7 state UP group default
    link/ether 36:10:35:28:ca:9e brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet6 fe80:: 3410:35ff: fe28: ca9e/64 scope Link
      valid lft forever preferred lft forever
14: vethscoc2080if13: <BROADCAST, MULTICAST,UP, LOWER_UP> mtu 1500 qdisc noqueue master docker® state UP group default
    link/ether 6a:27: f5:52:12:27 brd ff:ff:ff:ff:ff:fflink-netnsid0
    inet6 fe80::6827:f5ff: fe52:1227/64 scope link
      valid ft forever preferred lft forever
16: veth7cfOeba@if15: <BROADCAST, MULTICAST, UP, LOWER _UP> mtu 1500 qdisc noqueue master br-4bc4667df2e7 state UP group default
    link/ether 8a:5e:86:76:44:9b brd ff:ff:ff:ff:ff:ffLink-netnsid4
    inet6 fe80:: 885e: 86ff: fe76:449b/64 scope link
      valid lft forever preferred lft forever
468: wipos20f0u7: «NO-CARRIER, BROADCAST, MULTICAST, UP> mtu 1500 qdisc ma state DOWN group default glen 1000
    link/ether 00:0b:81:9d:90:66 brd ff:ff:ff:ff:ff:ff

winnie · 29 May 2022 13:15

I almost want to think there’s some sort of issue with the use of containers and/or virtual machines. That’s a lot of “adapters”.

Plus, the three custom config files related to NetworkManager and DNS.

The logs show enp2s0 is connected.

What if you temporarily disable the custom configs you made?

zbe · 29 May 2022 13:22

Is there any particular reason you are using systemd-resolved?

SheepYY039 · 29 May 2022 14:34

Actually, I forgot what custom configs I made. I wanted to try and “reset” my network configs yesterday, but I can’t remember what was default and what is new…

Yes, I run a Windows 11 VM on my machine through VMWare, also, I was trying to investigate into setting up KVM so I can try and run Microsoft Office in my machine. After this problem, I have uninstalled those services, but I am unsure if there are still files and configs written by them that is causing the problem, as I also suspect that those are the origin of this problem now…

SheepYY039 · 29 May 2022 14:36

Nope, I am unsure what its doing, tbh. Is it better to not use it, or use anything else or sth? I am willing to try other solutions… Also, the file 99-dont-touch-my-dns.conf was created because I was following the Network Configuration steps on the Manjaro Wiki while trying to decode this problem.

winnie · 29 May 2022 14:37

For comparison, if it means anything:

My /etc/NetworkManager/NetworkManager.conf is blank:

# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.

There is nothing under my /etc/NetworkManager/conf.d/ directory

SheepYY039 · 29 May 2022 14:45

I have now removed all files under my /etc/NetworkManager/conf.d directory, and removed those lines in the NetworkManager.conf file. However, the network is still not back after rebooting.

I have realized that those veth devices are related to docker, and seem to be containers from docker. However, I think docker does not run when I am not connected to the internet, right? Just to ensure, I have disabled all my running docker containers.

zbe · 29 May 2022 16:48

Nah it shouldn’t matter, just asking because NetworkManager provides dns as well. Btw, disable and stop systemd-resolved.service if you removed all those .conf files for NetworkManager.

Can you ping anything on the internet? Can you ping your own router or connect to it via web, what is its IP?

hape · 29 May 2022 17:00

can you show your routing table (“ip route show”)?

HP

SheepYY039 · 30 May 2022 02:14

ip route show

default via 192.168.3.1 dev emp2s@ proto static
172.17.0.0/16 dev docker® proto kernel scope link sr 172.17.0.1 linkdown
172.17.0.0/16 dev docker® proto kernel scope link src 172.17.0.1 metric 427 Linkdown
172.19.0.0/16 dev br-4bc4667df2e7 proto kernel scope link sc 172.19.0.1 Linkdown
172.19.0.0/16 dev br-4bc4667df2e7 proto kernel scope link sc 172.19.0.1 metric 425 Linkdown
192.168.3.0/24 dèv emp2s@ proto kernel scope link src 192.168.3.39

I can’t ping anything from the internet nor can I ping my router 192.168.3.1.

SheepYY039 · 30 May 2022 04:02

After following the steps provided by sudo-obey, I can now ping stuff. I can confirm that the problem is related to my firewalld config, as the problem starts after I enable firewalld. The problem is not there when I change to use ufw.

Thanks to all of you @winnie @Keruskerfuerst @zbe @hape!

Steps given by sudo-obey to clean the firewall and DNS rules:

sudo iptables -F INPUT
sudo iptables -F OUTPUT
sudo iptables -P INPUT ACCEPT
sudo iptables -P OUTPUT ACCEPT
sudo systemctl restart NetworkManager

Once finished, reboot your system.

system · 1 June 2022 18:02

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.