Howto change LAN MAC adress

[lbradio]

Setup:
1x ADSL router
2x Asus RT-AC-68U in AP mode.
Merlin Build 3.0.0.4.374.39

Errormessage: kernel: br0: received packet on eth1 with own address as source address

I get this messages a lot (multiple times a minute).

It seems that the LAN MAC adress and Wireless 2,4GHz MAC adress are the same.
(the MAC adress of 5GHz is different).

Is there any possibility to change the LAN MAC adress? Clone MAC on WAN page won't work since this is not available in AP mode.

 

[Adamm]

Setup:
1x ADSL router
2x Asus RT-AC-68U in AP mode.
Merlin Build 3.0.0.4.374.39

Errormessage: kernel: br0: received packet on eth1 with own address as source address

I get this messages a lot (multiple times a minute).

It seems that the LAN MAC adress and Wireless 2,4GHz MAC adress are the same.
(the MAC adress of 5GHz is different).

Is there any possibility to change the LAN MAC adress? Clone MAC on WAN page won't work since this is not available in AP mode.

This is normal shouldn't be anything to worry about, I get this to after booting. If your really intent on changing MAC addresses though they are all stored in the nvram and can be changed quite easily.

 

[lbradio]

Hello Adamm,
Thanks for your reply. Unfortunately it isn't during, of short after booting, but constantly.

I will try my luck with changing MAC.
You pointed me to nvram. I found the following line:
nvram set wan_hwaddr=x.x.x.x.x

Is this the correct way to change MACadress? Should I place this in any wan-startscript?

Thanx.


eb 27 12:00:10 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:00:27 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:00:44 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:02 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:19 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:37 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:54 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:12 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:29 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:46 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:03 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:20 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:37 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:54 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:12 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:29 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:46 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:04 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:21 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:40 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:56 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:07 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:14 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:31 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:48 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:05 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:23 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:40 kernel: br0: received packet on eth1 with own address as source address

 

[Adamm]

Hello Adamm,
Thanks for your reply. Unfortunately it isn't during, of short after booting, but constantly.

I will try my luck with changing MAC.
You pointed me to nvram. I found the following line:
nvram set wan_hwaddr=x.x.x.x.x

Is this the correct way to change MACadress? Should I place this in any wan-startscript?

Thanx.


eb 27 12:00:10 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:00:27 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:00:44 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:02 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:19 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:37 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:54 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:12 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:29 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:46 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:03 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:20 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:37 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:54 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:12 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:29 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:46 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:04 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:21 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:40 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:56 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:07 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:14 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:31 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:48 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:05 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:23 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:40 kernel: br0: received packet on eth1 with own address as source address

Not sure exactly what causes this, from what I see this only effects users who are running a bridge. It's been brought up as a known issue as early as 2012, personally I've never run into it and I'd only be guessing on a solution.

That being said, I'd wait for someone else here to give you more insight on the issue.

 

[ScottW]

This most often is reported by folks running a bridge or access point, and seems to happen when devices "switch" between them. For example, I see it every time one of our mobile devices (phones and laptops) "switch" between the N66U Router at the North end of our house and the N66U "AP" at the South end. At least in that context, it doesn't seem to have any detrimental effect on the network.

However, you seem to be getting much higher quantity of these messages than mobile devices would likely explain. Could you have a loop somewhere? Or a device that is simultaneously connected by Wired and Wireless?

 

[jlake]

Hello Adamm,
Thanks for your reply. Unfortunately it isn't during, of short after booting, but constantly.

I will try my luck with changing MAC.
You pointed me to nvram. I found the following line:
nvram set wan_hwaddr=x.x.x.x.x

Is this the correct way to change MACadress? Should I place this in any wan-startscript?

Thanx.


eb 27 12:00:10 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:00:27 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:00:44 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:02 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:19 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:37 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:01:54 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:12 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:29 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:02:46 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:03 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:20 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:37 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:03:54 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:12 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:29 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:04:46 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:04 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:21 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:40 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:05:56 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:07 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:14 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:31 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:06:48 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:05 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:23 kernel: br0: received packet on eth1 with own address as source address
Feb 27 12:07:40 kernel: br0: received packet on eth1 with own address as source address

I think you're getting more of those errors in log than most people because you have two APs and it's flip flopping between APs. Most people that have Asus in AP mode get those errors/conflicts because they are using the same SSIDs.

The only way you're going to get rid of those errors/conflicts is to use unique/different SSIDs. If you're not having any connectivity problems, I wouldn't worry about it.

When you use the same SSIDs, the Asus gets confused because it's a wired bridge. Having a (wired) bridge connection is a good thing. Because if it wasn't a smart bridge, you wouldn't be able to forward a port to a device connected to one of the APs.

Again, the only way to stop errors/conflicts is to use unique SSIDs.

 

[lbradio]

I did some tests, and messages indeed appear after "roaming" between AP's.
Of course I prefer to use same SSID, to make life easier, so I will monitor the performance for some days.

If it doesn't effect the performance to much, i will leave it that way.

Thank you all for replying.