Routing fails on LAN with static IPv4

Hi,
I have an installation of EndeavourOS-Cassini-neon on my MS-Surface since one year - working perfect. In March I set up a new installation in parallel on the same machine with Plasma 6 an upgraded to EndeavourOS-Gemini. The (internal) WiFi ist connected to the internet with DHCP while the Surface-Dock is connected to the LAN (cable).
The network setups of both installations are identical - however with Gemini the LAN routing fails with “no route to…”, while it works perfectly with Cassini. I tried in addition with two USB-Ethernet adaptors - no routing.
The OS identifies both network adaptors and even a Ping to the connector (192.168.2.202) works - but no routing to other devices in the LAN.

Was there any change in the networking from Cassini → Gemini? I don’t believe it’s related to Plasma 5 → 6.

nmcli device show | grep IP4
IP4.ADDRESS[1]: 192.168.1.116/24
IP4.GATEWAY: 192.168.1.100
IP4.ROUTE[1]: dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 600
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 192.168.1.100, mt = 600
IP4.DNS[1]: 192.168.1.100
IP4.ADDRESS[1]: 192.168.2.202/24
IP4.GATEWAY: –
IP4.ROUTE[1]: dst = 192.168.2.0/24, nh = 192.168.2.202, mt = 100
IP4.ROUTE[2]: dst = 192.168.2.0/24, nh = 0.0.0.0, mt = 100
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: –

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.100 0.0.0.0 UG 600 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
192.168.2.0 192.168.2.202 255.255.255.0 UG 100 0 0 enp0s20f0u1u2
192.168.2.0 0.0.0.0 255.255.255.0 U 100 0 0 enp0s20f0u1u2

Hi,
I made some experiments further and installed a new setup on an other MS-Surface - again with EndeavourOS Gemini and Plasma 6 => the same effects - no routing in the LAN (segment 192.168.2.xxx), fine (internet) connection in segment 192.168.1.xxx.

I disabled IPv6 by default in the boot-command-line

For me everything looks fine, but it’s not working:

ifconfig
enp0s20f0u2u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.212 netmask 255.255.255.0 broadcast 192.168.2.255
ether bc:83:85:f5:d9:1b txqueuelen 1000 (Ethernet)
RX packets 26 bytes 4369 (4.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 78 bytes 8158 (7.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 96 bytes 7890 (7.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 96 bytes 7890 (7.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

mlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.114 netmask 255.255.255.0 broadcast 192.168.1.255
ether bc:83:85:1d:54:54 txqueuelen 1000 (Ethernet)
RX packets 9490 bytes 9205487 (8.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6045 bytes 1545362 (1.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

traceroute 192.168.2.75
traceroute to 192.168.2.75 (192.168.2.75), 30 hops max, 60 byte packets
1 surfacepro4 (192.168.2.212) 3028.356 ms !H 3028.020 ms !H 3027.909 ms !H

ip route show
default via 192.168.1.100 dev mlan0 proto dhcp src 192.168.1.114 metric 600
192.168.1.0/24 dev mlan0 proto kernel scope link src 192.168.1.114 metric 600
192.168.2.0/24 via 192.168.2.212 dev enp0s20f0u2u2 proto static metric 100
192.168.2.0/24 dev enp0s20f0u2u2 proto kernel scope link src 192.168.2.212 metric 100

Does anybody have an idea?

Can you share the setup and output from the machine that is working?

Hi,

the machine is a Microsoft Surface Pro 7+ and a Pro 4.
Which output do you want? There is no error message, just time out due to routing failure. A ping give “no route to 192.168.2.075” as example.

If you have any test command please let me know.

The setup is a plain vanilla installation of EndeavourOS Gemini (ISO download today) with complete Plasma 6 Desktop plus CUPS from the installer.

I tried to setup Network in the Live environment, but this did not work either.

The Cassini installation works fine (as others before).

Right, you are showing network info above from the not working machine. I want to see the same info from a working machine

Okay - here is the output of the Endeavour-Cassini installation (on the same machine)

nmcli device show | grep IP4
IP4.ADDRESS[1]: 192.168.1.202/24
IP4.GATEWAY: 192.168.1.100
IP4.ROUTE[1]: dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 600
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 192.168.1.100, mt = 600
IP4.DNS[1]: 192.168.1.100
IP4.ADDRESS[1]: 192.168.2.202/24
IP4.GATEWAY: –
IP4.ROUTE[1]: dst = 192.168.2.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]: dst = 192.168.2.0/24, nh = 192.168.2.202, mt = 3
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: –

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.100 0.0.0.0 UG 600 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
192.168.2.0 192.168.2.202 255.255.255.0 UG 3 0 0 enp0s20f0u1u2
192.168.2.0 0.0.0.0 255.255.255.0 U 100 0 0 enp0s20f0u1u2

ifconfig
enp0s20f0u1u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.202 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::add2:a019:3637:caa4 prefixlen 64 scopeid 0x20
ether bc:83:85:f5:d9:1b txqueuelen 1000 (Ethernet)
RX packets 36 bytes 30922 (30.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 92 bytes 31021 (30.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 7748 bytes 651796 (636.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7748 bytes 651796 (636.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.202 netmask 255.255.255.0 broadcast 192.168.1.255
ether 38:fc:98:0a:3f:a7 txqueuelen 1000 (Ethernet)
RX packets 2817641 bytes 3755351767 (3.4 GiB)
RX errors 0 dropped 4 overruns 0 frame 0
TX packets 1303514 bytes 697380761 (665.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

traceroute 192.168.2.75
traceroute to 192.168.2.75 (192.168.2.75), 30 hops max, 60 byte packets
1 192.168.2.75 (192.168.2.75) 0.701 ms 0.556 ms 0.514 ms

ip route show
default via 192.168.1.100 dev wlan0 proto static metric 600
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.202 metric 600
192.168.2.0/24 via 192.168.2.202 dev enp0s20f0u1u2 proto static metric 3
192.168.2.0/24 dev enp0s20f0u1u2 proto kernel scope link src 192.168.2.202 metric 100

I hope this helps…

I am looking for a network setup completely out of Plasma 6 - not using the network manager(s).
Tomorrow I want to try a setup without graphical display manager, just cli, in order to clarify if it might be related to Plasma 6.

Today I installed a plain vanilla EndeavourOS-Gemini with Plasma 6 and tried to install in addition XFCE4, but this failed due to connection errors to some servers. I will check tomorrow again.