384.4_2 repeater mode error ac88u - received packet on eth2 with own address as source address

[agilani]

Hi,
I have a brand new ac88u that i installed asus merlin and setup in repeater mode with a brand new config and I'm seeing this over and over in my logs. Anyone else seen this? There is nothing directly attached to any of the ethernet ports and there are zero wireless clients to cause this error.

Apr 25 11:28:31 kernel: br0: received packet on eth2 with own address as source address
Apr 25 11:28:31 kernel: br0: received packet on eth2 with own address as source address
Apr 25 11:38:30 kernel: br0: received packet on eth2 with own address as source address
Apr 25 11:38:30 kernel: br0: received packet on eth2 with own address as source address
Apr 25 11:38:30 kernel: br0: received packet on eth2 with own address as source address
Apr 25 11:38:30 kernel: br0: received packet on eth2 with own address as source address
Apr 25 11:48:29 kernel: br0: received packet on eth2 with own address as source address
Apr 25 11:48:29 kernel: br0: received packet on eth2 with own address as source address
Apr 25 11:48:29 kernel: br0: received packet on eth2 with own address as source address

 

[agilani]

In case anyone else has the same problem, i plugged into Ethernet 1 and 2 and lost wireless altogether. I ended up flashing stock firmware - wiped again and this time it wouldn't connect via repeater mode and wireless was still out. Then i installed 380.70 and wiped and then got back wireless and was able to get repeater mode working. Then flashed back to stock, repeater mode working no errors - dirty flash. Upgraded back to 384.4_2 - dirty flash and for now it looks like I'm still getting the same errors with 384.4_2

Letting it soak to see if anything else changes. I should have checked to see if stock firmware changed the CFE.

Plugged my laptop into eth2 to see if it makes any difference.

Interesting thing is, it happens almost every 10 minutes exactly. I checked my other repeaters, this is the only one getting the error.

Looks like I'm getting the same error on stock 384_20379. Back t 380.70 to see if it still happens.

Looks like backtracking to 380.70 fixed the error. Still not sure what is causing it.

 

[Kingp1n]

Do u have guest network enabled? Per this thread, disabling seems to remove message.

kernel: br0: received packet on eth1 with own address as source address | Page 4 | SmallNetBuilder Forums
https://www.snbforums.com/threads/k...th-own-address-as-source-address.21877/page-4

 

[agilani]

Do u have guest network enabled? Per this thread, disabling seems to remove message.

kernel: br0: received packet on eth1 with own address as source address | Page 4 | SmallNetBuilder Forums
https://www.snbforums.com/threads/k...th-own-address-as-source-address.21877/page-4

No guest networks, I still get the error occasionally, not as often as before. it happens on an regular interval though. For example it may start at 14:04 and then the next one will be at 14:14 and then 14:24. Almost like some sort of scheduled cron job is kicking it off or something.

 

[geff078]

Hi,

Sorry to dig into this old post, but I am having the same issue running AC86U under 384.8_2.
Do you have found any solution for that warning?
One thing I have notice is that all interfaces (br0, bcmsw, eth0-5) are having the same MAC address. Could it be the cause of this?

Thank you for your feedback.

 

[Jeremy R Fender]

Hi,

Sorry to dig into this old post, but I am having the same issue running AC86U under 384.8_2.
Do you have found any solution for that warning?
One thing I have notice is that all interfaces (br0, bcmsw, eth0-5) are having the same MAC address. Could it be the cause of this?

Thank you for your feedback.

Did you ever find a solution to this?