Pedan Posted April 14, 2021 Posted April 14, 2021 (edited) Apr 14 10:44:23 Tower kernel: br117: received packet on eth117 with own address as source address (addr:40:8d:5c:58:f1:2a, vlan:0) Apr 14 10:44:23 Tower kernel: br117: received packet on eth117 with own address as source address (addr:40:8d:5c:58:f1:2a, vlan:0) Apr 14 10:44:25 Tower kernel: br117: received packet on eth117 with own address as source address (addr:40:8d:5c:58:f1:2a, vlan:0) Apr 14 10:44:32 Tower kernel: br0: received packet on bond0 with own address as source address (addr:40:8d:5c:58:f1:2a, vlan:0) Apr 14 10:45:24 Tower kernel: br0: received packet on bond0 with own address as source address (addr:40:8d:5c:58:f1:2a, vlan:0) Apr 14 10:45:32 Tower kernel: br117: received packet on eth117 with own address as source address (addr:40:8d:5c:58:f1:2a, vlan:0) I had moved from two interfaces on two different vlans to an active-backup bond. My log gets flooded with this entry. Does anyone know how to fix this? I attached a minimal network overview Edited April 14, 2021 by Pedan Quote
Vr2Io Posted April 14, 2021 Posted April 14, 2021 (edited) Problem are eth117 / br117, suspect cause by dirty setting in network config file. A simple way was delete whole config file or edit yourself. Edited April 14, 2021 by Vr2Io 1 Quote
Pedan Posted April 14, 2021 Author Posted April 14, 2021 That did the trick! I edited the /boot/config/network.cfg file and got rid of the messages. Thank you very much! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.