Received packet with own address

[RocketJSquirrel]

I am getting this in my RT-N66U log from time to time. I have searched and failed to find the solution to this. Googling the text of the log message shows many questions and no answers.

Feb 22 13:11:32 kernel: eth1: received packet with own address as source address

I am running 3.0.0.4.374.33_0-sdk5. I have tried the obvious, namely ensuring that no 2 devices have the same LAN IP address. Beyond that, I don't know what to do.

Anybody know the remedy?

 

[r00t4rd3d]

Are you using a range extender? Google says this was some peoples issue with that error.

This says its a firmware problem, I dont think you should be using the sdk5 stuff any more:

http://forums.smallnetbuilder.com/showthread.php?t=8953

For the N66U the 39_0 em build is what Merlin says is best to run.

 

[antdes45]

Not just a wireless extender but a wireless bridge as well I guess?

I'm in the same situation. All the clients connected to my EA-N66 bridge have different IPs, but they all appear to the RT-N66U's client list with the same MAC address.

 

[Pericynthion]

I get it all the time - my initial thoughts was it might be a device roaming between the 2GHz and the 5Ghz radio but it happens even with fixed SSIDs.

My guess is it's something to do with the virtual bridge for the LAN switch when it passes traffic to the firewall for inspection - but that's a guess.


Either way other than filling the log it doesn't seem to do any harm.


Sent from my iPhone using Tapatalk

 

[RocketJSquirrel]

Hmm, I did add a wireless access point at the far end of the house where signal was weak.

I'm finally building the home theater in a previously unused room, yay! But the Sony tablet for controlling the 4K video server wasn't getting a strong WiFi signal. I had an old Netgear wireless access point lying around, so I decided to use it in that room. I believe that's when the messages started. I am not using the 5 GHz band at all.

Thanks for the replies. I've upgraded to the 3.0.0.4.374.39_0-em firmware as suggested, and will see whether that provides a good enough signal without the access point or whether just to live with the messages.

 

[ScottW]

Seems harmless

I get these messages frequently, and they seem to occur when mobile devices "roam" (switch) between the router at North end of house and the AP at the South end of the house.

I've posted about it a couple of times, but all I have are "theories" (guesses) about what causes it. Whatever it is, it doesn't seem to cause any problems.

I have seen these messages with every N66U firmware I have used (stock and Merlin) over the last couple years. And I have seen other posts about it from people using other WRT variants. I currently use N66U's for the Router and the AP; but also got these messages when the AP was a dedicated Dlink Access Point.

A couple older threads:
http://forums.smallnetbuilder.com/showthread.php?t=14892
http://forums.smallnetbuilder.com/showthread.php?p=66214#post66214

 

[jlake]

I get these messages frequently, and they seem to occur when mobile devices "roam" (switch) between the router at North end of house and the AP at the South end of the house.

I've posted about it a couple of times, but all I have are "theories" (guesses) about what causes it. Whatever it is, it doesn't seem to cause any problems.

I have seen these messages with every N66U firmware I have used (stock and Merlin) over the last couple years. And I have seen other posts about it from people using other WRT variants. I currently use N66U's for the Router and the AP; but also got these messages when the AP was a dedicated Dlink Access Point.

A couple older threads:
http://forums.smallnetbuilder.com/showthread.php?t=14892
http://forums.smallnetbuilder.com/showthread.php?p=66214#post66214

I agree with your theory. I have a similar setup as y'all with a wired "smart" bridge AP, but I don't get those messages in log. I do use different/unique SSID's. I'm assuming you all use the same SSIDs and that is why you get the messages in log and I don't?

 

[ScottW]

I agree with your theory. I have a similar setup as y'all with a wired bridged AP, but I don't get those messages in log. I do use different/unique SSID's. I'm assuming you all use the same SSIDs and that is why you get the messages in log and I don't?

Very possible the SSID identification has something to do with it. I do use the same SSID's on the Router and the AP (one SSID for 2.4GHz, another for 5GHz).

 

[jlake]

Very possible the SSID identification has something to do with it. I do use the same SSID's on the Router and the AP (one SSID for 2.4GHz, another for 5GHz).

All four of my SSIDs are unique so I'm 99% percent sure that's the reason.

Linksys warns against using the same SSIDs if the connection is a bridge with their newer routers in AP mode (a.k.a bridge mode). An Asus in AP mode is also a smart bridge, but they don't warn against using the same SSIDs probably because it's not that big of a deal (other than the seemingly harmless conflicts and errors in log). I know people that use linksys in bridge mode with same ssid against the advice of linksys with no ill effects.

I guess if it's working fine......nothing to worry about.

Edit: and for those where it's not working fine, you're probably going to have to use different/unique SSID's

 

[RocketJSquirrel]

I think you nailed it. I do use the same SSID (and same 2.4 GHz channel) on both APs. This is mainly to avoid family members asking "which of these networks do I need to be on?" all the time. (I turned off 5 GHz largely for the same reason. Simplify, simplify.) The remote AP doesn't broadcast the SSID; only the router does.