Fedora 33: Network does not work anymore

Discussions in English on using Fedora
#1

Hello and gretings,

i recently upgraded from fedora 32 to fedora 33 which worked smoothly. But since this upgrade the network does not work anymore. There is a physical connection (to an onboard Intel® 8258V Gigabit Network Adapter on an ASUS Crosshair V Formula Z (not the youngest hardware, i admit)) and fedora 33 did find it and configurated it well. But mo program is able to use this… like there is no network.

What can i do to find the problem and what must i do to fix it?

By the way: i am the dreaded below average linux user, who expects fedora to run smoothly ‘out-of-the-box’, which worked since fedora 20.

Thanks in advance,
Uriens The Gray

1 Like
#2

Try to establish the connection and check the output:

nmcli general status; nmcli connection show; \
networkctl -n 0 status; resolvectl dns; \
ip address show; ip route show; \
ping -w 3 8.8.8.8; \
ping -w 3 fedoraproject.org
#3

Hi. I have the same issue.

# ping -w 3 8.8.8.8;

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2025ms

And for the second one:

# ping -w 3 fedoraproject.org
ping: fedoraproject.org: Name or service not known

What should we do? This is a fresh install of Fedora 33. The result of the first command is that everything is “enabled”:

# nmcli general status; nmcli connection show;
STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
connected  full          enabled  enabled  enabled  enabled 
NAME         UUID                                  TYPE      DEVICE 
System eth0  5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03  ethernet  eth0   
System eth1  9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04  ethernet  eth1

And the second command suggests:

# networkctl -n 0 status; resolvectl dns;
●   State: routable                                      
  Address: 10.13.0.6 on eth0                             
           192.241.X.X on eth0                       
           10.128.56.117 on eth1                         
           fe80::8cd3:a5ff:fe12:3520 on eth0             
           fe80::e0ad:65ff:fec3:85e on eth1              
  Gateway: 192.241.X.1 (ICANN, IANA Department) on eth0
Global:
Link 2 (eth0):
Link 3 (eth1):
#4

Some more info if it helps:

# systemctl restart systemd-networkd

# networkctl -n 0 status; 

●   State: routable                                      
  Address: 10.13.0.6 on eth0                             
           192.241.174.143 on eth0                       
           10.128.56.117 on eth1                         
           fe80::8cd3:a5ff:fe12:3520 on eth0             
           fe80::e0ad:65ff:fec3:85e on eth1              
  Gateway: 192.241.174.1 (ICANN, IANA Department) on eth0

# ping www.google.com
ping: www.google.com: Name or service not known
#5

Did it work on Fedora 32 before upgrading?
Do you have the same hardware as the OP?

1 Like
#6

I found the issue was that /etc/resolv.conf does not stay persistent in Fedora. Changing it to symlink does work for now:

1 Like
#7

Looks like your problem is not limited to resolver config.

#9

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