Intel NIC UDP Checksum Offloading Causes IPMI Packet Loss on Windows 11
Disable IPv4 UDP Rx checksum offloading on Intel NICs to restore IPMI communication on Windows 11 and Windows 10.
Disable IPv4 UDP Rx checksum offloading on affected Intel NICs to restore IPMI communication.
Summary
On May 4, 2026, Michal Necasek documented a networking anomaly where Windows 11 machines failed to receive IPMI UDP packets from a Tyan SMDC module, despite the packets arriving on the network. The issue manifested as a DropReason INET: checksum is invalid reported by PktMon, while Wireshark and Linux ipmitool confirmed the checksums were correct. The culprit was identified as the Intel I211 NIC driver (e1r68x64.sys) on Windows 11 and the Intel 82579LM driver (e1i65x64.sys) on Windows 10, both performing faulty IPv4 UDP receive checksum offloading. Disabling the IPv4 UDP Rx checksum offload flag in the respective driver configuration restored IPMI communication for both the host and its VMs. The problem did not appear on a Windows 10 laptop with a Killer Wireless 1525 adapter, nor did it affect DHCP or DNS, indicating the issue is isolated to specific Intel NICs. Linux, even with the same hardware, accepted the packets without modification, confirming the driver’s checksum logic is at fault. The author speculates that the NIC’s handling of the IP Packet ID field and lack of DF flag in outgoing packets may trigger the incorrect checksum validation. The practical fix is to turn off IPv4 UDP Rx checksum offloading on affected Intel NICs, a workaround that avoids the need for driver updates.
Key changes
- Windows 11 Intel I211 NIC drops UDP packets to port 623 due to checksum offloading
- PktMon reports DropReason INET: checksum is invalid
- Wireshark and Linux ipmitool confirm checksums are correct
- Disabling IPv4 UDP Rx checksum offload in e1r68x64.sys restores IPMI traffic
- Same issue on Windows 10 Intel 82579LM resolved by disabling in e1i65x64.sys
- Linux accepts packets with same hardware, indicating driver fault
- Issue isolated to specific Intel NICs, not affecting DHCP or DNS
- Workaround avoids need for driver update