Something went wrong with network

Dear colleagues,

I’m facing network issues since I’ve updated to Fedora 35. I dont know why but local network fail, I cannot SSH, even ping to local machines (only to the gateway works) while Internet connection works fine.

I’ve been playing a bit with routes, configuring from network-scripts and network service (I now it is deprecated), going back to network.manager, using the UI and using nmcli as well, but no luck…

I’ve tried as well with the firewalld disabled but same issue, honestly I don’t know what else to look.
Can you bring some light on my issue?

Current routes:

[user@host ~]$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    100    0        0 eno1
192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 eno1

Thanks

1 Like

Welcome to the askfedora community.

Please provide us with the output of ip address and ip route

When you post that, if you use the </> button above and make certain the ``` are both above the first line and below the last line, it will retain the formatting as seen on your screen so it is easily readable.
As you can see from your post, if either are on the same line as the text it will instead show as a single full line of text with the red color. This is what that would have looked like.

[user@host ~]$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    100    0        0 eno1
192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 eno1
1 Like

Hello JV. Thanks for the hints.

[user@host ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether ac:22:0b:4e:13:ad brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 192.168.1.39/24 brd 192.168.1.255 scope global dynamic noprefixroute eno1
       valid_lft 81563sec preferred_lft 81563sec
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:4c:77:f8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
[user@host ~]$ ip r
default via 192.168.1.1 dev eno1 proto dhcp metric 100 
192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.39 metric 100 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 metric 425 linkdown 

Whith this config I can send ICMP to the GW but not to other alive IPs in the network:

[user@host ~]$ ping -c 1 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.648 ms

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.648/0.648/0.648/0.000 ms
[user@host ~]$ ping -c 1 192.168.1.38
PING 192.168.1.38 (192.168.1.38) 56(84) bytes of data.
From 192.168.1.39 icmp_seq=1 Destination Host Unreachable

--- 192.168.1.38 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
 

Hello JV and thanks for the hints

[user@host ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether ac:22:0b:4e:13:ad brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 192.168.1.39/24 brd 192.168.1.255 scope global dynamic noprefixroute eno1
       valid_lft 81563sec preferred_lft 81563sec
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:4c:77:f8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
[user@host ~]$ ip r
default via 192.168.1.1 dev eno1 proto dhcp metric 100 
192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.39 metric 100 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 metric 425 linkdown 

And this is what happen when pinging devices in the same netwok:
I can reach the GW but not other alive hosts.

[user@host ~]$ ping -c 1 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.581 ms

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.581/0.581/0.581/0.000 ms
[user@host ~]$ ping -c 1 192.168.1.38
PING 192.168.1.38 (192.168.1.38) 56(84) bytes of data.
From 192.168.1.39 icmp_seq=1 Destination Host Unreachable

--- 192.168.1.38 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

1 Like

Hello Vladislav,
Thats not my case, I didn’t use McAfee or any ICMP blocker (indeed the only device having issues for pinging is the Fedora one and I have 3 other linux boxes)
Thank you anyway.

It sounds like there is something going on at the router that fails to connect the fedora box to the others.

I see that the IP is dhcp, so theoretically the netmask should be the same, assuming that all have dhcp addresses assigned by the router.

Have you tried a power off & on of the router so it is reset with all new connections/routing tables, etc.? Sometimes this type of error appears when a router gets something wrong in its config and a restart will fix it.

It is also possible that the router may consider one of the hosts (maybe the fedora one) to be in the DMZ and prevents it contacting the others locally.

1 Like

What happens if you ping the 192.168.1.39 from the 192.168.1.38?

1 Like

Router rebooted and connectivity working fine again.
You saved my day :heart_eyes:

Same, 100% packet loss, now I found the failure was in my cheap ISP router.
Thanks!