Ethernet icon showing question mark and staying offline, wifi icon is ok but still no internet. Fedora 39 Gnome

Ask Fedora
,
1

Ethernet icon showing question mark and staying offline, wifi icon is ok but I am still offline in all applications. Yesterday I had no issue and it does not exist when I boot Windows on the same computer (dual-boot Fedora 39 Gnome and Windows). I tried booting with kernel 6.6.8 and 6.6.6, Gnome and Gnome xorg but it didn’t make any difference.

3

My command “ping google.com” resulted in this response:

“ping: google.com: Temporary failure in name resolution”

5 
ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=60 time=14.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=13.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=13.9 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 13.374/13.742/13.977/0.263 ms

ping -c 3 2001:4860:4860::8888
PING 2001:4860:4860::8888(2001:4860:4860::8888) 56 data bytes
64 bytes from 2001:4860:4860::8888: icmp_seq=1 ttl=60 time=15.1 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=2 ttl=60 time=14.1 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=3 ttl=60 time=13.9 ms

--- 2001:4860:4860::8888 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 13.851/14.348/15.062/0.517 ms

nslookup example.org 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	example.org
Address: 93.184.216.34
Name:	example.org
Address: 2606:2800:220:1:248:1893:25c8:1946

nslookup example.org 2001:4860:4860::8888
Server:		2001:4860:4860::8888
Address:	2001:4860:4860::8888#53

Non-authoritative answer:
Name:	example.org
Address: 93.184.216.34
Name:	example.org
Address: 2606:2800:220:1:248:1893:25c8:1946

resolvectl --no-pager status
Global
         Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub

Link 2 (enp5s0)
    Current Scopes: LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
        DNS Domain: speedport.ip

Link 3 (wlp4s0)
    Current Scopes: none
         Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported

resolvectl --no-pager query example.org
example.org: 93.184.216.34                     -- link: enp5s0
             2606:2800:220:1:248:1893:25c8:1946 -- link: enp5s0

-- Information acquired via protocol DNS in 8.6ms.
-- Data is authenticated: no; Data was acquired via local or encrypted transport: no
-- Data from: network

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: active (running) since Wed 2024-01-03 18:35:33 CET; 3min 20s ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 5520 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 18346)
     Memory: 5.0M
        CPU: 71ms
     CGroup: /system.slice/systemd-resolved.service
             └─5520 /usr/lib/systemd/systemd-resolved

Jan 03 18:35:33 fedora-ideacentre systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
Jan 03 18:35:33 fedora-ideacentre systemd-resolved[5520]: Positive Trust Anchors:
Jan 03 18:35:33 fedora-ideacentre systemd-resolved[5520]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jan 03 18:35:33 fedora-ideacentre systemd-resolved[5520]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.>
Jan 03 18:35:33 fedora-ideacentre systemd-resolved[5520]: Using system hostname 'fedora-ideacentre'.
Jan 03 18:35:33 fedora-ideacentre systemd[1]: Started systemd-resolved.service - Network Name Resolution.
Jan 03 18:35:33 fedora-ideacentre systemd-resolved[5520]: enp5s0: Bus client set search domain list to: speedport.ip, speedport.ip
Jan 03 18:35:33 fedora-ideacentre systemd-resolved[5520]: enp5s0: Bus client set default route setting: yes
Jan 03 18:35:33 fedora-ideacentre systemd-resolved[5520]: enp5s0: Bus client set DNS server list to: 192.168.2.1, fe80::1
lines 1-26/26 (END)
1 Like
7

The issue has gone without me doing anything but thank you very much for your support!

8

The issue re-appeared one day later again, so I had to try your solution anyway - unfortunatelly it lasted just one day. Now I found out that I have the issue also on my other computer connected to the same router. It is running Rhino Linux. So affected are only my both Linux OSes - Windows 11 is not affected… Rhino OS went online after a while without me doing anything. Fedora is still offline.

11

The same router works flawlessly on Windows 11 (dual boot Windows 11 & Fedora). I never needed before to configure a public DNS provider so I have no idea how to do it right now.

12

For your information, I found the solution, which helped me, here: Systemd-resolved fails on initial load