System log has been blown up with this this error. I have started in the safe mode also and its still there. I have never seen this before, any issues I should be worried about? 

 

Diagnostic attached.

 

 

May 29 02:49:03 Tower_2 kernel: br0: received packet on eth0 with own address as source address
May 29 02:49:04 Tower_2 kernel: br0: received packet on eth0 with own address as source address
May 29 02:51:06 Tower_2 kernel: br0: received packet on eth0 with own address as source address
May 29 02:51:09 Tower_2 kernel: br0: received packet on eth0 with own address as source address
May 29 02:51:12 Tower_2 kernel: br0: received packet on eth0 with own address as source address
May 29 02:53:12 Tower_2 kernel: br0: received packet on eth0 with own address as source address
May 29 02:53:12 Tower_2 kernel: br0: received packet on eth0 with own address as source address
May 29 02:53:19 Tower_2 kernel: br0: received packet on eth0 with own address as source address

tower_2-diagnostics-20170529-0827.zip

Use a different bonding method. Likely you have now "round-robin", make this "active-standby" instead.

 

See network settings.

 

Edited May 29, 20179 yr by bonienl

Bonding was set to no, changed it to "active standby". Monitoring now to see if it returns.

Sent from my HTC 10 using Tapatalk

Now with bonding set to "active standby", I'm getting this - just changed from "eth0" to "bond0". This goes away when I remove the "Enable Bridging" of course......

 

May 30 07:17:08 Tower_2 kernel: br0: received packet on bond0 with own address as source address
May 30 07:19:17 Tower_2 kernel: br0: received packet on bond0 with own address as source address
May 30 07:21:27 Tower_2 kernel: br0: received packet on bond0 with own address as source address
May 30 07:23:31 Tower_2 kernel: br0: received packet on bond0 with own address as source address
May 30 07:25:28 Tower_2 kernel: br0: received packet on bond0 with own address as source address
May 30 07:27:34 Tower_2 kernel: br0: received packet on bond0 with own address as source address

Having the same issue with single NIC, bonding = no, bridging = yes