[SOLVED] Cannot connect to internet anymore after upgrade

lviggiani · 2021-01-11 08:15:02

Today, after updating my system and restarting my archlinux won't connect to the internet anymore. It connects to WIFI (also tried hotspotting from my phone) but in GNOME the system try icon shows a question mark. The internet connection is OK as I'm using it from another computer to write this post.
Also pinging from terminal any address says that there's a temporary error in name resolution. I've tryed hanging the dns setting in my wifi connection and aslo uase another wifi but I still get the same problem.
Can someone help me please?

EDIT:

$ systemctl status NetworkManager 

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Mon 2021-01-11 08:59:14 CET; 24min ago
       Docs: man:NetworkManager(8)
   Main PID: 356 (NetworkManager)
      Tasks: 3 (limit: 18676)
     Memory: 15.9M
     CGroup: /system.slice/NetworkManager.service
             └─356 /usr/bin/NetworkManager --no-daemon

gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <info>  [1610351965.4253] manager: NetworkManager state is now CONNECTED_LOCAL
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <info>  [1610351965.4287] manager: NetworkManager state is now CONNECTED_SITE
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <info>  [1610351965.4290] policy: set 'FASTWEB-H5IXAP' (wlp0s20f3) as default for IPv4 routing and DNS
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <info>  [1610351965.4294] dns-mgr: Writing DNS information to /usr/bin/resolvconf
gen 11 08:59:25 arch-linux-luca NetworkManager[801]: Failed to resolve interface "NetworkManager": Nessun device corrisponde
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <warn>  [1610351965.4424] dns-mgr: resolvconf failed with status 256
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <warn>  [1610351965.4426] dns-mgr: could not commit DNS changes: resolvconf failed with status 256
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <info>  [1610351965.4426] device (wlp0s20f3): Activation: successful, device activated.
gen 11 09:00:22 arch-linux-luca NetworkManager[356]: <info>  [1610352022.6235] agent-manager: agent[e3f7424dea42c004,:1.54/org.gnome.Shell.NetworkAgent/1000]: agent registered
gen 11 09:09:54 arch-linux-luca NetworkManager[356]: <info>  [1610352594.0863] audit: op="connection-update" uuid="dc71d31b-68db-4265-a0bf-a4267db1205e" name="FASTWEB-H5IXAP" args="connecti>

and

$ cat /etc/resolv.conf

# Generated by NetworkManager

Last edited by lviggiani (2021-01-12 07:38:12)

lviggiani · 2021-01-11 08:41:13

I've temporary solved by manually adding Google dns server to /etc/resolv.conf and restarting NetworkManager service

$ cat /etc/resolv.conf

nameserver 8.8.8.8

however I don't think it's the best solution

Last edited by lviggiani (2021-01-11 08:41:41)

twelveeighty · 2021-01-11 14:41:47

Looking at the change logs for NetworkManager, its comment is: "FS#68891 Restore resolvconf" and that bug asked to "Please reenable resolvconf support so that the new "auto" mode of "rc-manager" properly falls back to resolvconf when systemd-resolved is not detected."

This made openresolv an optional dependency of NetworkManager. I'm not suggesting to blindly install that, but take a look at the bug description and see if those scenarios apply to your case?

nl6720 · 2021-01-11 16:19:18

lviggiani wrote:

gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <warn>  [1610351965.4424] dns-mgr: resolvconf failed with status 256
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <warn>  [1610351965.4426] dns-mgr: could not commit DNS changes: resolvconf failed with status 256

Did you perhaps install systemd-resolvconf while not using systemd-resolved? If so, then that's an invalid configuration, systemd-resolvconf should only be installed on a system where systemd-resolved.service is enabled/started.

lviggiani · 2021-01-12 07:37:05

nl6720 wrote:

lviggiani wrote:
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <warn>  [1610351965.4424] dns-mgr: resolvconf failed with status 256
gen 11 08:59:25 arch-linux-luca NetworkManager[356]: <warn>  [1610351965.4426] dns-mgr: could not commit DNS changes: resolvconf failed with status 256
Did you perhaps install systemd-resolvconf while not using systemd-resolved? If so, then that's an invalid configuration, systemd-resolvconf should only be installed on a system where systemd-resolved.service is enabled/started.

Yes that's just my case! Honestly I don't remember having deliberately installed systemd-resolvconf nor disabled systemd-resolved.service. Maybe it came as a dependency of something else or maybe I just followed some guide in the past and I can't remember.

SOLUTION:
BTW, enabling/starting systemd-resolved.service solved the issue for me thanks!

Last edited by lviggiani (2021-01-12 07:43:02)

nl6720 · 2021-01-12 09:05:28

NetworkManager doesn't support using systemd-resolvconf as a resolvconf implementation, so starting systemd-resolved.service shouldn't be enough to fix you setup. Since you say it works now, I presume you created the /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf symlink as instructed in https://wiki.archlinux.org/index.php/Sy … solved#DNS.

wickedlester · 2021-01-13 15:37:38

I ran into this problem this morning. Did some digging and found that I had systemd-resolvconf installed as a dependency to netctl. since I use networkmanager I didn't need netctl installed anyway so I uninstalled netctl and systemd-resolvconf and that fixed my issue.

Sunday87 · 2021-01-16 13:14:45

Had the same problem too and uninstalling systemd-resolvconf and netctl and installing openresolv instead fixed it. I had a look in my pacman.log to see about these packages. So in 2017 when I originally set up my thinkpad, I installed openresolv along with NetworkManager. In 2019, I don't know the reason, openresolv was deinstalled and systemd-resolvconf installed instead - but everything continued to work just fine. Ever since systemd-resolvconf got updated quite a few times until suddenly it stopped working yesterday. I never knowingly set up systemd-resolved so my /etc/resolv.conf is just a regular file and no symlink. So I am a bit stymied how I got away with systemd-resolvconf for over a year.

Arch Linux

#1 2021-01-11 08:15:02

[SOLVED] Cannot connect to internet anymore after upgrade

#2 2021-01-11 08:41:13

Re: [SOLVED] Cannot connect to internet anymore after upgrade

#3 2021-01-11 14:41:47

Re: [SOLVED] Cannot connect to internet anymore after upgrade

#4 2021-01-11 16:19:18

Re: [SOLVED] Cannot connect to internet anymore after upgrade

#5 2021-01-12 07:37:05

Re: [SOLVED] Cannot connect to internet anymore after upgrade

#6 2021-01-12 09:05:28

Re: [SOLVED] Cannot connect to internet anymore after upgrade

#7 2021-01-13 15:37:38

Re: [SOLVED] Cannot connect to internet anymore after upgrade

#8 2021-01-16 13:14:45

Re: [SOLVED] Cannot connect to internet anymore after upgrade

Board footer