I am seeing the errors below all the time in my syslog on both my Unriad servers.  It's driving me nuts, but there doesn't seem to be much to go in in order to investigate further.  Sometimes the logs are flooded with these messages and other times it can be more sporadic.  Any idea what could cause this so I can investigate further?  That Mac address is the Unraid server's Mac address.

 

Apr 22 12:54:12 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 12:54:12 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 12:54:12 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 12:54:13 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 12:54:13 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 12:54:13 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 12:54:23 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 12:54:23 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 12:56:40 SmashySmash shfs: /usr/sbin/zfs create 'ingestion_cache/unraiddata2' Apr 22 13:24:37 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 13:24:37 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 13:24:47 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 13:24:47 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 13:55:01 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 13:55:01 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 13:55:11 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 13:55:11 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 14:09:04 SmashySmash emhttpd: read SMART /dev/sdc Apr 22 14:25:25 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 14:25:25 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 14:25:35 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0) Apr 22 14:25:35 SmashySmash kernel: br0: received packet on bond0 with own address as source address (addr:0c:c4:7a:bc:56:c8, vlan:0)

Edited April 22, 20242 yr by Bmalone

this usually means that you have combined more than one lan card into a "bond" (aka port aggragation, aka trunk), set this to something else than "active backup" and connect these cards to either the same switch without configuring the switch to support this trunk style, or connect them to different switches that are also connected to each others somehow (switch loop).

 

In rare conditions it also can mean that your lan card is broken or switch are broken and reflect packets that should not.

 

But the first version is much more likely.