networking network_error ai_generated partial

UDP: bad checksum from 10.0.0.2:12345 to 10.0.0.1:53

ID: networking/udp-checksum-failure

Also available as: JSON · Markdown · 中文
75%Fix Rate
81%Confidence
1Evidence
2024-02-28First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
Linux kernel 5.15 active — — —
Linux kernel 6.1 active — — —
FreeBSD 13.2 active — — —

Root Cause

The UDP datagram received has an incorrect checksum, indicating corruption during transit, a faulty network interface, or software that generates invalid checksums.

generic

中文

接收到的UDP数据报校验和错误，表明传输过程中发生损坏、网络接口故障或生成了无效校验和的软件。

Official Documentation

https://www.kernel.org/doc/html/latest/networking/checksum-offloads.html

Workarounds

  1. 85% success Check network interface for errors: ethtool -S eth0 | grep -i error 
    Check network interface for errors: ethtool -S eth0 | grep -i error
  2. 80% success Update NIC driver or firmware to resolve hardware-level checksum issues: ifconfig eth0 down && modprobe -r driver_name && modprobe driver_name && ifconfig eth0 up 
    Update NIC driver or firmware to resolve hardware-level checksum issues: ifconfig eth0 down && modprobe -r driver_name && modprobe driver_name && ifconfig eth0 up

中文步骤

  1. Check network interface for errors: ethtool -S eth0 | grep -i error
  2. Update NIC driver or firmware to resolve hardware-level checksum issues: ifconfig eth0 down && modprobe -r driver_name && modprobe driver_name && ifconfig eth0 up

Dead Ends

Common approaches that don't work:

  1. 75% fail

    Disabling UDP checksum offloading (ethtool -K eth0 tx-checksumming off) may mask the issue but doesn't fix the root cause if the sender generates bad checksums.

  2. 80% fail

    Assuming it's a transient network issue and ignoring repeated occurrences can lead to data corruption in DNS responses or other UDP services.