6.11.3 br0: received packet on eth0 with own address as source address

[mattekure]

I recently updated to 6.11.3 and have begun noticing the logs filling up with these messages.  There doesnt seem to be any error associated with it, but I dont  know whats going on.  Diags attached.  Any help is appreciated.

 

Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:45 Tower kernel: br0: received packet on eth0 with own address as source address (addr:70:85:c2:d8:8f:b9, vlan:0)
Nov 14 12:09:53 Tower kernel: net_ratelimit: 32742 callbacks suppressed

 

tower-diagnostics-20221114-1224.zip

[Arbadacarba]

 

 

Really curious if this helps... and if so which direction.

[MAM59]

These kind of error usually shows up if there is a routing loop within your lan.

It often happens, if you connect two ports of a switch to the same destination and forget to tell the switch that this should be treated as a trunk / bond.

It also could mean that there is a circular connection between many switches so a packet is forwarded around and around in a loop.

(Note that intelligent switches will notice these situations and cut off one line or put them to sleep to be used as a fallback if the other line fails. But normal, dumb an cheap switches get crazy and do strange things)

I also saw bad lan cards (not on the unraid box, but somewhere in the LAN) that echoed back everything they received therefor driving other devices crazy.

 

In general it means : CHECK YOUR WIREING (and Network settings) and LAN Devices

 

From your diagnostics I see that you only have one LAN card with a very simple setting. I dont know but maybe former UNRAID versions silently ignored and dropped such echo-back packets. Or, it was just coincidencally that one other device broke and now produces such problems.

 

Good luck on your search, these kind of bugs are hard to track down (Maybe you need to use a Networksniffer like Wireshark and trigger it to this MAC Address, but even then, you will get a lot of "good" packets and now and then one of these illegal echos).

 

[mattekure]

Thanks for the ideas.  I'll keep poking at it.  As you mentioned, I have a very simple setup with only one LAN card/cable.  I am not aware of any special settings in my switch, other than having a static IP for my Unraid server.  

[MAM59]

As I said, there is a good chance that a totally different device on the lan produces these reflections.

You may start to pull out the others one by one and see if the errors vanish.

This may take some time but will surely work.