Re: checksum failure from 161.79.0.0
Roy Marples
Mon Dec 02 17:44:43 2019
Hi Alarig
On 02/12/2019 12:54, Alarig Le Lay wrote:
From time to time dhcpcd displays checksum failure. When it occurs I
loose the lease and the old IPv4 address isn’t removed from the interface.
The IPv6 lease has never expired for now.
The IP 161.79.0.0 belongs to a Brazilian ISP and is well routed to it,
so I don’t think that it’s used alongside my ISP (which is Norwegian).
And it’s always displayed. Sometimes, I also have a checksum failure
from 0.0.0.0
core01-arendal ~ # /sbin/dhcpcd --renew enp2s0
DUID 00:01:00:01:20:4a:2e:93:00:0d:b9:48:c1:c0
enp2s0: IAID b9:48:c1:c1
enp2s0: IA type 25 IAID e8:7b:be:be
enp2s0: rebinding prior DHCPv6 lease
enp2s0: REPLY6 received from fe80::5e5e:abff:fe43:1ece
enp2s0: renew in 43200, rebind in 69120, expire in 86400 seconds
lo: adding reject route to 2001:4640:a14f::/48
enp2s0: delegated prefix 2001:4640:a14f::/48
enp2s0: soliciting an IPv6 router
enp2s0: soliciting a DHCP lease
enp2s0: checksum failure from 161.79.0.0
enp2s0: checksum failure from 161.79.0.0
enp2s0: offered 88.89.68.6 from 88.91.209.1
enp2s0: probing address 88.89.68.6/22
enp2s0: leased 88.89.68.6 for 1200 seconds
enp2s0: adding route to 88.89.68.0/22
enp2s0: adding default route via 88.89.68.1
forked to background, child pid 29103
And here is my config:
core01-arendal ~ # grep -v '^#' /etc/dhcpcd.conf
hostname
duid
persistent
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option interface_mtu
require dhcp_server_identifier
slaac private
interface enp2s0
metric 30
ia_pd e8:7b:be:be
I have an igb NIC:
02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network
Connection (rev 03)
Subsystem: Intel Corporation I211 Gigabit Network Connection
Kernel driver in use: igb
Kernel modules: igb
core01-arendal ~ # ethtool -i enp2s0
driver: igb
version: 5.4.0-k
firmware-version: 0. 6-1
expansion-rom-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
I didn’t changed the offload params:
core01-arendal ~ # ethtool -k enp2s0 | grep offload
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
l2-fwd-offload: off [fixed]
hw-tc-offload: on
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
Could it be a dhcpcd bug? Or perhaps something related to a hardware
offload?
It could very well be a dhcpcd bug!
You didn't say what dhcpcd version you are using, but it was broken in
the 8.1.0 release and then fixed in 8.1.1 (but please use 8.1.2)
Roy
Archive administrator: postmaster@marples.name