received packet on eth2 with own address as source address

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 453

PostPosted: Fri Dec 26, 2014 17:18    Post subject: received packet on eth2 with own address as source address Reply with quote
hello - i've got an r6300v2 that i recently put ddwrt/kong (25700m) on. i have some lags and drops which i think might be related to these messages which as you can see are overloading the syslogs (see below this just a fragment - these are generated 10-100 times per minute)

my interfaces are:
WAN - to cable modem
LAN - to two AP's, that duplicate 2.4g SSID's to extend range thoughout house and yard. (the AP's are archer C&'s also with dd-wrt,r35309. just in dumb AP mode, no dns, no dhcp, no services)
WLAN: 1 AP on 2.4ghz, 1 virtual AP on 2.4 ghz, 1 AP on 5ghz

dnsmasq for dhcp, some port-forwards to local printer and to allow remote access to my AP's.

a number of raoming wifi clients (notebooks, ipads, rokus, whatever)

syslog/dmesg output:
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
Dec 26 16:55:41 hoffman1 kern.warn kernel: br0: received packet on eth2 with own address as source address
-------------------

any thoughts on what i can do to track this down? \
thanks


[/code]
Sponsor
MikeMcr
DD-WRT User


Joined: 28 Aug 2009
Posts: 54

PostPosted: Fri Dec 26, 2014 18:30    Post subject: Reply with quote
Do you have the same SSID on all WLAN interfaces? If so, I previously read that is the reason for the messages.

Change the SSID names to be unique as a test if you want to prove this.

I get those messages too for the same reason but was told they are harmless?
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 453

PostPosted: Fri Dec 26, 2014 19:11    Post subject: Reply with quote
MikeMcr wrote:
Do you have the same SSID on all WLAN interfaces? If so, I previously read that is the reason for the messages.

Change the SSID names to be unique as a test if you want to prove this.

I get those messages too for the same reason but was told they are harmless?


EDIT. thanks. they decreased, but did not go away when i made my 5g ssid different from my 2.4g ssid.

i think this also has to do with the MAC addresses that dd-wrrt assigns to the interfaces, which are slightly different from the default netgear MAC's. specifically, the wl0.1 virtual ap has the same MAC as the 5g wlan. this is specific to dd-wrt.
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 453

PostPosted: Sat Dec 27, 2014 15:15    Post subject: Reply with quote
there is definitely a problem with mac addresses on the r6300v2 and dd-wrt (kong builds and BS)

the MAC address for the WL1 (5G) radio is the same and the LAN MAC address. this creates problems!
Acumen
DD-WRT User


Joined: 15 Nov 2014
Posts: 221

PostPosted: Fri Sep 23, 2016 12:28    Post subject: Reply with quote
This seems still the case now a days.
Code:
Sep 23 12:12:59 R6400 kern.warn kernel: br0: received packet on wl0.1 with own address as source address
Sep 23 12:12:59 R6400 kern.warn kernel: br0: received packet on wl0.1 with own address as source address
Sep 23 12:13:03 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 23 12:13:03 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 23 12:13:06 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 23 12:13:06 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 23 12:13:06 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address

I noticed over 700 of these warnings and as you can see in the ifconfig output, there are duplicated MAC addresses, but wl0.1 is no dup of br0.
Code:
ifconfig | grep HWaddr
br0       Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
br0:0     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
br1       Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
vlan1     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
vlan2     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:52
eth0      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
eth1      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:53
eth2      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:54
wl0.1     Link encap:Ethernet  HWaddr 2E:XX:XX:XX:XX:54
wl1.1     Link encap:Ethernet  HWaddr 2E:XX:XX:XX:XX:55

Is there something I can do about this?

_________________
Netgear WNDR4300v1 DD-WRT v3.0 BS r29837 | Netgear R6400 DD-WRT v3.0 KB r33525M | Tickets: 5429
IPv4 & IPv6-PD | ProFTP & Samba to USB thumb | DNSMasq DHCPv6 | Pi-Hole on RasPi

Found a bug, report it so the it can be fixed: http://svn.dd-wrt.com/
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Fri Sep 23, 2016 13:49    Post subject: Reply with quote
Acumen wrote:
This seems still the case now a days.
Code:
Sep 23 12:12:59 R6400 kern.warn kernel: br0: received packet on wl0.1 with own address as source address
Sep 23 12:12:59 R6400 kern.warn kernel: br0: received packet on wl0.1 with own address as source address
Sep 23 12:13:03 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 23 12:13:03 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 23 12:13:06 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 23 12:13:06 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 23 12:13:06 R6400 kern.warn kernel: br0: received packet on eth2 with own address as source address

I noticed over 700 of these warnings and as you can see in the ifconfig output, there are duplicated MAC addresses, but wl0.1 is no dup of br0.
Code:
ifconfig | grep HWaddr
br0       Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
br0:0     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
br1       Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
vlan1     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
vlan2     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:52
eth0      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
eth1      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:53
eth2      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:54
wl0.1     Link encap:Ethernet  HWaddr 2E:XX:XX:XX:XX:54
wl1.1     Link encap:Ethernet  HWaddr 2E:XX:XX:XX:XX:55

Is there something I can do about this?


Your macs are all wrong and indicate, that you have not erased nvram, or you played so much in the gui that you messed everything up.

I told you before, that you can expect instabilities if there are left overs from other fw in nvram. The factory default in webif just does not clear out everything, as not every model fully restores it's mandatory vars. Thus some params are just not set to dd-wrt defaults, but kept at original values.

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Acumen
DD-WRT User


Joined: 15 Nov 2014
Posts: 221

PostPosted: Mon Sep 26, 2016 12:00    Post subject: Reply with quote
<Kong> wrote:
Acumen wrote:
This seems still the case now a days.
...
Is there something I can do about this?


Your macs are all wrong and indicate, that you have not erased nvram, or you played so much in the gui that you messed everything up.

I told you before, that you can expect instabilities if there are left overs from other fw in nvram. The factory default in webif just does not clear out everything, as not every model fully restores it's mandatory vars. Thus some params are just not set to dd-wrt defaults, but kept at original values.


You did not told me, you replied on someone else his post in the same thread. The fact however is that I erased the NVRAM based on that post. The accusation of me playing to much in the GUI and messing things up is based on nothing, but I apparently hit a nerve somewhere...

Never the less, I will give it a complete rebuild to make sure all leftovers are gone, starting with nvram erase.

_________________
Netgear WNDR4300v1 DD-WRT v3.0 BS r29837 | Netgear R6400 DD-WRT v3.0 KB r33525M | Tickets: 5429
IPv4 & IPv6-PD | ProFTP & Samba to USB thumb | DNSMasq DHCPv6 | Pi-Hole on RasPi

Found a bug, report it so the it can be fixed: http://svn.dd-wrt.com/
Acumen
DD-WRT User


Joined: 15 Nov 2014
Posts: 221

PostPosted: Tue Sep 27, 2016 16:57    Post subject: Reply with quote
For (everyones) information:
1. Starting with: Firmware: DD-WRT v3.0-r30356
2. nvram erase; reboot
3. Restore factory defaults
4. Connect to SSID dd-wrt
5. Set password
6. Install '160925 - r30695M KB', Reset to Default
7. Connect to SSID dd-wrt
8. Set password
9. Services –> Services –> SSHd: Enable
10. Putty 192.168.1.1
11. Nvram erase; reboot
12. Connect to SSID dd-wrt
13. Started a complete fresh manual install.

Issues seem to be disappeared. MAC addresses seem to be unchanged:
Code:
ifconfig | grep HWaddr
br0       Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
br0:0     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
eth0      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
eth1      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:53
eth2      Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:54
vlan1     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:51
vlan2     Link encap:Ethernet  HWaddr 2C:XX:XX:XX:XX:52
wl0.1     Link encap:Ethernet  HWaddr 2E:XX:XX:XX:XX:54
wl1.1     Link encap:Ethernet  HWaddr 2E:XX:XX:XX:XX:55

_________________
Netgear WNDR4300v1 DD-WRT v3.0 BS r29837 | Netgear R6400 DD-WRT v3.0 KB r33525M | Tickets: 5429
IPv4 & IPv6-PD | ProFTP & Samba to USB thumb | DNSMasq DHCPv6 | Pi-Hole on RasPi

Found a bug, report it so the it can be fixed: http://svn.dd-wrt.com/
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum