Trouble with Intel x520 10Gbit

English Network/Internet
1

Hi. Yesterday I spend the whole day to get an intel x520-DA2 dual 10Gbit network card to work without success. Neither a dhcp configuration nor a manual configuration works. With dhcp networkmanager seems to do some connection, but it fails to set a gateway. With a manual configuration networkmanager outright fails to do any connection. On a Windows machine both dhcp and manual settings work, so I guess it’s not a router misconfiguration (which is also new, as the x520’s).

Here is the output of “nmcli device show” after a dhcp connection. eth0 is an onboard 1GBit port which works just fine, eth5 is the x520 (lower part). eth0 is in a different subnet. IP4.GATEWAY is missing at eth5.

GENERAL.DEVICE:                         eth0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         D0:50:99:DE:CE:F2
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (verbunden)
GENERAL.CONNECTION:                     RJ45-1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/36
WIRED-PROPERTIES.CARRIER:               an
IP4.ADDRESS[1]:                         192.168.111.71/24
IP4.GATEWAY:                            192.168.111.254
IP4.ROUTE[1]:                           dst = 0.0.0.0/0, nh = 192.168.111.254, mt = 100
IP4.ROUTE[2]:                           dst = 192.168.111.0/24, nh = 0.0.0.0, mt = 100
IP4.DNS[1]:                             194.154.192.101
IP4.DNS[2]:                             8.8.8.8
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         eth5
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         F8:F2:1E:AE:6A:98
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (verbunden)
GENERAL.CONNECTION:                     Wired connection 3
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/16
WIRED-PROPERTIES.CARRIER:               an
IP4.ADDRESS[1]:                         192.168.112.250/24
IP4.GATEWAY:                            --
IP4.ROUTE[1]:                           dst = 192.168.112.0/24, nh = 0.0.0.0, mt = 101
IP4.DNS[1]:                             194.154.192.101
IP4.DNS[2]:                             8.8.8.8
IP6.GATEWAY:                            --

“journalctl -fu NetworkManager” when connecting with dhcp:

Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6579] device (eth5): Activation: starting connection 'Wired connection 3' (e992e497-14c2-37fb-b185-5d7e62c0941d)
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6580] audit: op="connection-activate" uuid="e992e497-14c2-37fb-b185-5d7e62c0941d" name="Wired connection 3" pid=2300 uid=1000 result="success"
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6582] device (eth5): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6587] manager: NetworkManager state is now CONNECTING
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6589] device (eth5): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6601] device (eth5): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6604] dhcp4 (eth5): activation: beginning transaction (timeout in 45 seconds)
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option dhcp_lease_time      => '600'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option domain_name_servers  => '194.154.192.101 8.8.8.8'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option expiry               => '1614712575'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option ip_address           => '192.168.112.250'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option next_server          => '192.168.112.0'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option requested_broadcast_address => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option requested_domain_name => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option requested_domain_name_servers => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6783] dhcp4 (eth5): option requested_domain_search => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_host_name  => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_interface_mtu => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_ms_classless_static_routes => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_nis_domain => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_nis_servers => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_ntp_servers => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_rfc3442_classless_static_routes => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_root_path  => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_routers    => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_static_routes => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_subnet_mask => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_time_offset => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option requested_wpad       => '1'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option routers              => '192.168.112.0'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): option subnet_mask          => '255.255.255.0'
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6784] dhcp4 (eth5): state changed unknown -> bound
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6796] device (eth5): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6818] device (eth5): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6820] device (eth5): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.6822] manager: NetworkManager state is now CONNECTED_LOCAL
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.7729] device (eth5): Activation: successful, device activated.
Mär 02 20:06:15 RSS-SERVER NetworkManager[1166]: <info>  [1614711975.7782] audit: op="statistics" arg="refresh-rate-ms" pid=2300 uid=1000 result="success"

“journalctl -fu NetworkManager” when connecting manually:

Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1613] device (eth5): Activation: starting connection 'Wired connection 3' (e992e497-14c2-37fb-b185-5d7e62c0941d)
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1614] audit: op="connection-activate" uuid="e992e497-14c2-37fb-b185-5d7e62c0941d" name="Wired connection 3" pid=2300 uid=1000 result="success"
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1616] device (eth5): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1621] manager: NetworkManager state is now CONNECTING
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1624] device (eth5): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1638] device (eth5): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <warn>  [1614712533.1656] platform: (eth5) route-sync: failure to add IPv4 route: 0.0.0.0/0 via 192.168.112.0 dev 5 metric 20100 mss 0 rt-src user: Invalid argument
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1659] device (eth5): state change: ip-config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1663] manager: NetworkManager state is now DISCONNECTED
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <warn>  [1614712533.1672] device (eth5): Activation: failed for connection 'Wired connection 3'
Mär 02 20:15:33 RSS-SERVER NetworkManager[1166]: <info>  [1614712533.1675] device (eth5): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

“invalid argument”…
Any ideas?

2

Address 192.168.112.0/24 is invalid. It is network, not host, it cannot be default gateway. Fix your DHCP server if it returns this value.

3

Okay, thanks! I will have a look at the router config tomorrow. Weird though that the same settings worked in Windows, but I think I will double check that too.

4

Okey, I don’t really understand what should be wrong with the configuration. The connection works just fine with a Windows machine (dhcp and manual config).

Basic router settings:
https://killkenny.spdns.org/nextcloud/index.php/s/t5LRF3a4nsAGH4r/preview

:sarcastic: I’m far from a network expert though, so maybe there is an obvious mistake here?

5

@Arvidjaar has it right.
And, the bottom section of your router configuration verifies because the illegal address is displayed there.

Your network is configured with a Class C private network which means that your subnet mask is 255.255.255.0, aka “/24”
When you use this subnet mask, an IP address of every machine in your network cannot end in a zero (eg your 192.168.112.0) because that’s like saying you have a street address but no house number… How is the postman going to deliver your mail if your house is only known by the street but no house number?
(Ignore that technically, the address is handled as a general broadcast, which can still work if your network is configured properly)

Your router has to have a number between 1-254 (You can’t use the first number which is zero or the last number in the range of available addresses 255) as the last number of your IP address.

More particularly,
Your router probably has an address already set for its inner network interface, that should be the Default Gateway address handed out by your DHCP server, and the address you set up manually for a static address configuration (not using DHCP).

TSU

6

It is hard to tell without any documentation, but “IP Address” field under “Local Network” looks rather suspicious. It seems your router returns its own address as gateway and this address certainly cannot be 192.168.112.0/24. Try to set something like 192.168.112.1 (pick whatever address is unused in your case).

7

Cannot be just any address.
Must be the the network address configured for that interface.
Most common addresses configured are either 1 or 254 since the router(Default Gateway for that network segment) is typically the first device in the network, but for various reasons can be any valid address in the network range.

TSU

8

Oh, thanks a lot you two! I was totally unaware 192.168.112.0 was not a valid address, 192.168.112.1 fixed it. Thanks for the explanation :slight_smile: