Posted: Tue Oct 13, 2020 19:53 Post subject: R6300v1: br0: received packet on eth2 with own addr as src
the following message appears a few times a day in my syslog:
Oct 13 13:37:19 DD-WRT kern.warn kernel: br0: received packet on eth2 with own address as source address
Is this something to be concerned with? I have been having some random disconnects lately but I am not sure if this is related. This is on v3.0-r44467 running in AP/switch mode.
If this is problematic, how can the problem be fixed? Thanks!
I did perform a full reset when moving from stock firmware a few months back but not for the last few updates.
This is what ifconfig shows:
root@DD-WRT:~# ifconfig | grep HWaddr
br0 Link encap:Ethernet HWaddr 84:1B:5E:E8:36:BC
eth0 Link encap:Ethernet HWaddr 84:1B:5E:E8:36:BA
eth1 Link encap:Ethernet HWaddr 84:1B:5E:E8:36:BC
eth2 Link encap:Ethernet HWaddr 84:1B:5E:E8:36:BD
vlan1 Link encap:Ethernet HWaddr 84:1B:5E:E8:36:BA
vlan2 Link encap:Ethernet HWaddr 84:1B:5E:E8:36:BA
I read the posts you linked to and I can confirm that my 2.4 GHz and 5 GHz networks are using different SSIDs.
I also went through the AP settings and everything appears to be configured as listed.
The issue only appears to happen when my work laptop is connected to the 5 GHz network - other devices appear not to trigger it. The work laptop uses Sophos Connnect VPN - maybe this is what is confusing the AP.
I might try nvram erase later but I will probably wait till the weekend as it is a PITA to set everything up from scratch.
Well, I have good news and bad news. The good news is that after the this deep reset the connection seems to be more stable. Working from home my work laptop was semi-regularly dropping the wifi connection, this seems to be no longer happening.
The bad news is that the warning is still appearing in the syslog, albeit with subjectively lower frequency. After 3,5 days uptime I had it come up 3 times yesterday and once today.
Alright. I was hoping for a simpler solution. Erasing the nvram on the stations and manually configuring those won't be a big problem but if I had to do that on the master router it would take me the better part of an hour to get that up and running since I don't have a spare router. I guess I'll have to get a spare router and configure it manually and then swap them when ready so that the pitchforks don't come out and hope I didn't miss anything during the configuration.