I've been getting this warning in syslog every minute. Eth0 is always being renamed to some unique string. 

Nov  3 14:57:48 Tower kernel: igb 0000:04:00.0 eth0: mixed HW and IP checksum settings.
Nov  3 14:57:49 Tower kernel: igb 0000:04:00.0 eth0: mixed HW and IP checksum settings.
Nov  3 14:57:49 Tower kernel: eth0: renamed from veth3d8769f
Nov  3 14:57:49 Tower kernel: device br0 entered promiscuous mode
Nov  3 14:58:50 Tower kernel: device br0 left promiscuous mode
Nov  3 14:58:50 Tower kernel: veth3d8769f: renamed from eth0

This is the iommu grps for the nics.

IOMMU group 28:	[8086:1533] 04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
IOMMU group 29:	[8086:1533] 05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

My motherboard has dual intel nics and ipmi. The ipmi will share use of a nic, but primarily defaults to the first nic. The ipmi has its own configured ip, so there are dual ips on the first nic, one for the ipmi and one for unraid. In order to pass the second nic to a VM, I added the line to flash boot up that hides that nic from being used by unraid.

 

Any help is greatly appreciated. Thanks.

I am having the same issue after installing https://www.amazon.com/gp/product/B077YM9Q23/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 

I set them up and bonding Mode 1

 

Nov 4 13:16:59 Tower kernel: igb 0000:01:00.0 eth0: mixed HW and IP checksum settings.
Nov 4 13:16:59 Tower kernel: igb 0000:01:00.1 eth1: mixed HW and IP checksum settings.
Nov 4 13:16:59 Tower kernel: eth0: renamed from veth1018a58
Nov 4 13:17:06 Tower rc.docker: Confluence: started succesfully!
Nov 4 13:22:42 Tower kernel: veth1018a58: renamed from eth0
Nov 4 13:22:42 Tower kernel: igb 0000:01:00.0 eth0: mixed HW and IP checksum settings.
Nov 4 13:22:42 Tower kernel: igb 0000:01:00.1 eth1: mixed HW and IP checksum settings.
Nov 4 13:48:52 Tower kernel: igb 0000:01:00.0 eth0: mixed HW and IP checksum settings.
Nov 4 13:48:52 Tower kernel: igb 0000:01:00.1 eth1: mixed HW and IP checksum settings.
Nov 4 13:48:52 Tower kernel: eth0: renamed from veth459012b
Nov 4 14:34:30 Tower dhcpcd[1912]: br0.40: failed to renew DHCP, rebinding

 

Edited November 4, 20205 yr by son12710

The checksum errors stated happening with the igb Intel driver a few releases ago, they are harmless, the eth0 renamed logs are normal, they are related to the docker engine.

While I understand that they are harmless and related to the Docker engine, we're also having an nf_conntrack related crash, with the Docker engine. Some of us, at least, in another thread which the devs recently mentioned that they can't reproduce.

 

Maybe this should be looked into instead of dismissed?

What is the actual location of the misconfiguration? How would one go about setting it to conform, despite it being harmless? Is this within the reach of an experienced Linux user, or is this developer land? Kernel parameters? Module parameters? Sysctl pokes? I cannot find reference to this error that isn't an unRaid forum, and none of the ones I've found have a fix.