September 2, 20205 yr I'm quite a newbie, so I'm not sure this is a bug (actually several bugs), but I believe it is. My setup is a motherboard with an internal NIC connected to the internet and a Solarflare Card with 2 NICs, one connected to just a single host on the other side. Consider the network configuration on the screenshot eth0 is pretty straightforward with DHCP setting, however, eth1 has assigned a static route, no gateway (0.0.0.0) and a metric of 255. The issue now is how this seems to be interpreted in the routing (see 2nd screenshot). The 1st probable bug in "eth1 via 255" is that the metric "255" is somehow misinterpreted as an interface or an IP address. The 2nd bug is that I cannot delete this route with the trash icon next to it. It asks for confirmation which I give, but nothing happens. An "ip route" command yields ip route default via 192.168.1.1 dev br0 proto dhcp src 192.168.1.2 metric 1 default dev eth1 metric 255 192.168.1.0/24 dev br0 proto dhcp scope link src 192.168.1.2 metric 1 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.3 The command ip route del default dev eth1 is able to delete the route indeed. There is another presumed 3rd bug, that is after I had added the network card and rebooted Unraid, it was unreachable from the outside world. I had to log in locally and noticed that the network setting was completely screwed up (DHCP wasn't enabled anymore, so I had to statically assign the IP and, due to my incapability to resolve it on the command line, would then use the GUI network settings to adjust it again). Can somebody confirm these are bugs? Edited September 2, 20205 yr by kana Corrections
Archived
This topic is now archived and is closed to further replies.