No Internet on Silverblue 41

I’ve just rebased to Silverblue 41 prerelease. I can connect to my Internet devices (home router and phone), but I can’t reach the Internet. The Internet connection works fine with these devices when I boot my pinned Silverblue 40.

Is this a known issue for anyone? I could not find anything here

Any advice on how to debug it?

Here’s my WiFi adapter:

$ lspci | grep Network
01:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
1 Like

Can you try ping 1.1.1.1 ?

Added network

No, it doesn’t seem a DNS issue.

I’m now connected to the WiFi router at work and I have the same problem. The DNS here is 192.168.178.1 and I can ping it.

I’ve already tried disabling IPv6 but it didn’t help.

Ping on the local lan is not the same as pinging to the internet.
Try a ping to 1.1.1.1 or 8.8.8.8 and if that works then it possibly is dns. If that does not work then it would seem you may be getting blocked at the gateway router.

You are right: I can ping 1.1.1.1 but I cannot ping google.com.

systemd-resolve --status is printing:

Failed to get global data: Could not activate remote peer ‘org.freedesktop.resolve1’: startup job failed

The problem seems to be systemd-resolved.service. It’s enabled but it failed at startup.

As a temporary workaround I disabled systemd-resolved and added the DNS server IPs manually. I can now browse the Internet in Silverblue 41.
Should I report this bug? Or it’s just me (some wrong configuration)?

Here’s how I did it.
First, disable the service:

sudo systemctl disable systemd-resolved.service

I’ve created the file /etc/NetworkManager/conf.d/no-systemd-resolved.conf with this content:

[main]
systemd-resolved=false

I’ve created the file /etc/resolv.conf with these lines:

nameserver 1.1.1.1
nameserver 8.8.8.8

And restarted the service:

sudo systemctl restart NetworkManager.service

Incidentally, I can see that resolv.conf has remained also a symlink (?):

# ls -l /etc/resolv.conf
lrwxrwxrwx. 1 root root 39 24 set 00.21 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
root@fedora:~# cat /etc/resolv.conf
nameserver 1.1.1.1
nameserver 8.8.8.8

EDIT: it looks like I should first remove the existing symlink /etc/resolv.conf and then create the file with the same name. Otherwise the file disappears when the system is restarted.

Do you see an error message if you run systemctl status systemd-resolved.service?

(When the service is enabled, of course. The output won’t be interesting now that you’ve disabled it.)

Bug report

I’ve just made a test on today Silverblue 41 image.

First of all, I had to go back to the default configuration:

  • I commented all the lines in /etc/NetworkManager/conf.d/no-systemd-resolved.conf
  • I made a backup of the manual config file: cp /etc/resolv.conf /etc/resolv.conf.bak
  • I deleted resolv.conf and recreated the original symlink: rm /etc/resolv.conf && ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
  • Finally I re-enabled the service: systemctl enable systemd-resolved.service
  • and I restarted my computer

The Internet is not working and I see this:

# systemctl status systemd-resolved.service
× systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Sat 2024-11-02 21:55:32 CET; 2min 44s ago
 Invocation: 3861d9d51cd545b08b02399952b55ef8
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
             https://systemd.io/WRITING_RESOLVER_CLIENTS
    Process: 901 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=1/FAILURE)
   Main PID: 901 (code=exited, status=1/FAILURE)
      Error: 12 (Impossibile allocare memoria)

nov 02 21:55:32 fedora systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5.
nov 02 21:55:32 fedora systemd[1]: systemd-resolved.service: Start request repeated too quickly.
nov 02 21:55:32 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
nov 02 21:55:32 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
nov 02 21:55:35 fedora systemd[1]: systemd-resolved.service: Start request repeated too quickly.
nov 02 21:55:35 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
nov 02 21:55:35 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.

I see that this file is missing:

# ls /run/systemd/resolve/
root@fedora:~# 

Maybe I did some mistake?

Getting the Internet working again requires two commands:

  • rm /etc/resolv.conf && cp /etc/resolv.conf.bak /etc/resolv.conf
  • systemctl restart NetworkManager.service

So it seems a memory allocation problem, as in the bug report you linked above.