Testing - received packet on vlan1 with own address as source address

[RMerlin]

Anyone here who can easily reproduce these error messages (unfortunately they keep coming and going randomly for me)? I'd like to test a theory... Please specify which router model you have.

 

[mattiL]

Anyone here who can easily reproduce these error messages (unfortunately they keep coming and going randomly for me)? I'd like to test a theory... Please specify which router model you have.

I have an RT-AC87U with the latest Merlin release, 376.49_4, and see these messages, but I have no idea at all what triggers them.

376.49_4 flashed today, uptime 7h 30m at the moment.

 

[jgrove]

AC87 Merlin Firmware Point Release 4,

Don't use any of the more fancy features of the router, i use the standard settings for 2.4 and 5ghz

I can say that i don't see the error as often with the .4 release though

Dec 28 14:09:28 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Dec 28 14:09:28 kernel: IDPfw: TrendMicro forward module ver-1.0.25
Dec 28 14:09:28 kernel: IDPfw: Apply module param dev_wan=eth0
Dec 28 14:09:28 kernel: IDPfw: Apply module param sess_num=30000
Dec 28 14:09:28 kernel: IDPfw: Init chrdev /dev/idpfw with major 191
Dec 28 14:09:28 kernel: IDPfw: IDPfw is ready
Dec 28 14:09:28 kernel: sizeof forward param = 160
Dec 28 14:09:43 kernel: IDPfw: Exit IDPfw
Dec 28 14:09:43 kernel: Stop the IPS/AppID engine...
Dec 28 14:09:43 kernel: mod epilog takes 0 jiffies
Dec 28 14:09:43 kernel: IDPfw: Exit IDPfw
Dec 28 14:09:43 kernel: Stop the IPS/AppID engine...
Dec 28 14:09:43 kernel: IDPfw: Exit chrdev /dev/idpfw with major 191
Dec 28 14:10:54 dnsmasq-dhcp[4080]: DHCPDISCOVER(br0) cc:3a:xxxx:9b:8f
Dec 28 14:10:54 dnsmasq-dhcp[4080]: DHCPOFFER(br0) 192.168.1.123 cc:3a:61:ce:9b:8f
Dec 28 14:10:54 dnsmasq-dhcp[4080]: DHCPREQUEST(br0) 192.168.1.123 cc:3a:61:ce:9b:8f
Dec 28 14:10:54 dnsmasq-dhcp[4080]: DHCPACK(br0) 192.168.1.123 cc:3a:61:ce:9b:8f android-5c8529d6b722ce75
Dec 28 14:29:39 dnsmasq-dhcp[4080]: DHCPDISCOVER(br0) 40:f4:xxxx:47:33
Dec 28 14:29:39 dnsmasq-dhcp[4080]: DHCPOFFER(br0) 192.168.1.18 40:f4:xxxx:47:33
Dec 28 14:29:39 dnsmasq-dhcp[4080]: DHCPREQUEST(br0) 192.168.1.18 40:f4:xxxxx:47:33
Dec 28 14:29:39 dnsmasq-dhcp[4080]: DHCPACK(br0) 192.168.1.18 40:f4:07xxxxx:33
Dec 28 15:11:46 dnsmasq-dhcp[4080]: DHCPDISCOVER(br0) 40:f4:xxxx:47:33
Dec 28 15:11:46 dnsmasq-dhcp[4080]: DHCPOFFER(br0) 192.168.1.18 40:f4:xxxxx:33
Dec 28 15:11:46 dnsmasq-dhcp[4080]: DHCPREQUEST(br0) 192.168.1.18 40:xxxxx47:33
Dec 28 15:11:46 dnsmasq-dhcp[4080]: DHCPACK(br0) 192.168.1.18 40:f4:xxxx33
Dec 28 15:27:26 kernel: br0: received packet on vlan1 with own address as source address

 

[ScottW]

I get a similar message -- not sure if it is the same condition you are trying to test. Pretty sure I can "force" one of these to occur by simply walking to the other end of the house, thus "roaming" from the router to the AP.

Both router and AP are N66U, both running RMerl 376.48_3.

Dec 27 22:30:42 kernel: eth2: received packet with own address as source address
Dec 27 22:34:53 kernel: eth2: received packet with own address as source address
Dec 27 22:39:52 kernel: eth2: received packet with own address as source address
Dec 28 02:39:20 kernel: eth2: received packet with own address as source address
Dec 28 02:42:45 kernel: eth2: received packet with own address as source address
Dec 28 03:22:55 kernel: eth2: received packet with own address as source address
Dec 28 06:25:11 kernel: eth2: received packet with own address as source address
Dec 28 06:30:01 kernel: eth2: received packet with own address as source address
Dec 28 06:34:50 kernel: eth2: received packet with own address as source address
Dec 28 06:42:16 kernel: eth2: received packet with own address as source address
Dec 28 06:58:16 kernel: eth2: received packet with own address as source address
Dec 28 07:59:17 kernel: eth2: received packet with own address as source address
Dec 28 08:18:44 kernel: eth2: received packet with own address as source address
Dec 28 08:22:09 kernel: eth2: received packet with own address as source address
Dec 28 08:29:39 kernel: eth2: received packet with own address as source address
Dec 28 08:48:58 kernel: eth2: received packet with own address as source address
Dec 28 09:02:18 kernel: eth2: received packet with own address as source address
Dec 28 09:20:33 kernel: eth2: received packet with own address as source address
Dec 28 09:21:39 kernel: eth2: received packet with own address as source address
Dec 28 09:24:38 kernel: eth2: received packet with own address as source address
Dec 28 09:29:23 kernel: eth2: received packet with own address as source address
Dec 28 09:37:47 kernel: eth2: received packet with own address as source address
Dec 28 10:16:04 kernel: eth2: received packet with own address as source address
Dec 28 11:04:47 kernel: eth2: received packet with own address as source address
Dec 28 11:10:12 kernel: eth2: received packet with own address as source address
Dec 28 11:29:32 kernel: eth2: received packet with own address as source address
Dec 28 12:07:58 kernel: eth2: received packet with own address as source address

 

[mattiL]

This is todays harvest (RT-AC87U on 376.49_4):

Dec 28 15:15:08 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 15:15:08 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 16:15:06 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 16:15:06 kernel: br0: received packet on vlan1 with own address as source address

Dec 28 20:14:51 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:14:51 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:14:52 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:14:53 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:14:54 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:14:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:14:57 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:14:58 kernel: br0: received packet on vlan1 with own address as source address

 

[vnangia]

I see it on 376.48_1 on the AC68U. Occurs in groups of three for me - two within 15 seconds, and one about an hour later.

 

[brad0]

Using a RT-AC68U.

I am seeing these messages all the time.

I was also seeing very strange behavior when using the stock ASUS firmware where the management access to the router would cut out for a few mins at a time on and off non-stop but network access to/from the devices connected to Wifi would work perfectly without interruption and I was thinking this might be related. I haven't seen this odd behavior since switching to 376.49_2 from 3.0.0.4.376.3626, but that might not have anything to do with the Merlin firmware so much as something that has been merged from the unreleased newer ASUS codebase.

Dec 27 06:28:21 kernel: br0: received packet on eth1 with own address as source address
Dec 27 07:51:05 kernel: br0: received packet on eth1 with own address as source address
Dec 27 08:20:29 kernel: br0: received packet on eth1 with own address as source address
Dec 27 13:47:57 kernel: br0: received packet on eth1 with own address as source address
Dec 27 14:56:41 kernel: br0: received packet on wl0.1 with own address as source address
Dec 27 16:42:42 kernel: br0: received packet on wl0.1 with own address as source address
Dec 27 16:45:40 kernel: br0: received packet on wl0.1 with own address as source address
Dec 27 17:04:03 kernel: br0: received packet on wl0.1 with own address as source address
Dec 28 02:14:33 kernel: br0: received packet on wl0.1 with own address as source address
Dec 28 06:56:03 kernel: br0: received packet on eth1 with own address as source address
Dec 28 08:29:34 kernel: br0: received packet on eth1 with own address as source address

 

[Skirk]

Rt-AC87U running Merlin 376.49.

I seem to get this message daily, usually around 10 minutes after my Wifi turns off at night via cron jobs. I have checked and double checked that all of my wired clients have their wifi disabled.

Just a coincidence?

 

[RMerlin]

Those who can easily repeat the message, can you try the following over SSH?

1) Retrieve your 2.4 GHz MAC address:

nvram get 0:macaddr

2) Set it to a MAC that's two numbers higher. For instance, if it was 10:00:10:20:30:40, then set it to 10:00:10:20:30:42:

nvram set "0:macaddr=10:00:10:20:30:42"
nvram commit
service restart_lan
service restart_wireless

Let me know if it makes any difference in the long term (i.e. after a few hours).

 

[Skirk]

This is the log after running the commands and restarting the services (ac87u f/w merlin 376.49):

ec 29 21:25:43 rc_service: service 21266:notify_rc restart_lan
Dec 29 21:25:55 rc_service: service 21269:notify_rc restart_wireless
Dec 29 21:25:58 dropbear[21209]: Exit (stephen): Disconnect received
Dec 29 21:26:01 kernel: br0: port 2(eth1) entering forwarding state
Dec 29 21:26:01 kernel: device eth1 left promiscuous mode
Dec 29 21:26:01 kernel: br0: port 2(eth1) entering disabled state
Dec 29 21:26:05 kernel: wl_module_init: passivemode set to 0x0
Dec 29 21:26:05 kernel: wl_module_init: txworkq set to 0x1
Dec 29 21:26:05 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
Dec 29 21:26:06 dnsmasq-dhcp[12036]: DHCPREQUEST(br0) 192.168.1.209 f4:1b:a1:xx:xx:xx
Dec 29 21:26:06 dnsmasq-dhcp[12036]: DHCPACK(br0) 192.168.1.209 f4:1b:a1:xx:xx:xx Tom-iPod
Dec 29 21:26:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:11 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:11 kernel: device eth1 entered promiscuous mode
Dec 29 21:26:11 kernel: br0: topology change detected, propagating
Dec 29 21:26:11 kernel: br0: port 2(eth1) entering forwarding state
Dec 29 21:26:11 kernel: br0: port 2(eth1) entering forwarding state
Dec 29 21:26:14 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:14 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:17 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:17 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:17 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:18 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:19 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 21:26:20 kernel: br0: received packet on vlan1 with own address as source address

 

[jgrove]

I haven't tried that code that RMerlin has posted mainly because the 2.4ghz radio was off by schedule during the time the error occurred.

Dec 28 23:35:50 dnsmasq-dhcp[1865]: DHCPACK(br0) 192.168.1.120 d0:xxxxxxxxb1 Jamess-iPad
Dec 28 23:53:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:46 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:46 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:47 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:47 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:48 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:48 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:49 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:49 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:51 kernel: net_ratelimit: 2 callbacks suppressed
Dec 28 23:53:51 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:51 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:52 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:53:52 kernel: br0: received packet on vlan1 with own address as source address

 

[mattiL]

Nope, the change does not seem to do any good:

Dec 29 12:06:58 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 12:06:58 kernel: br0: received packet on vlan1 with own address as source address

 

[RMerlin]

Ok, was worth a shot. Thanks for trying it out.