What's new

RT-AC68U Incorrect/ghost IP address

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

DennyD

New Around Here
2 68Us running mesh at firmware _45713 (problem also at previous version)
iPads & iPhones at IOS 12.2
ASUS IOS Router app 1.0.0.1.49 (most current)

All my ip addresses are 192.168.0.xxx so I will abbreviate to .xxx

I have over 30 devices on the router and EVERYTHING seems to be working correctly.

I have a MAC/IP binding entry in the router to link my wife’s iPhone to ip .020, plus a dozen other entries.

The .020 address show in the iPhone’s WiFi settings, in the ASUS IOS app and in numerous windows 10 programs.

However, on the router’s web page in the Client Status panel the iPhone shows up as .117. Additionally the device icon has a superscript 2 on it. I only noticed the superscript after the last firmware upgrade. Over the last couple of months I had been intermittently fiddled with trying to get the MAC/IP binding to work on that iPhone. Apparently it does work. I trusted the browser page and did not actually check the device until I saw the superscript.

Now it gets weirder. While researching I found the dos ARP command.

ARP -a -v shows all the ips in use on the network. Both .020 & .117 show up. .020 has the iPhone MAC. .117 has a MAC of all zeros and a type of INVALID.
I tried ARP -d 192.168.0.117 to delete it and it immediately reappeared.
ARP -d -a to delete all did no good.
I can ping .020 but not .117 so I assumed .117 is a bad table entry and not a physical device.

Why does only the ASUS web page (iOS Safari and Win 10 Firefox) and dos ARP show the ghost .117 device? Why is .117 tied to a specific iPhone? I am fairly confident that this issue persisted across a factory reset on the 68U and several firmware upgrades.

If I understand this ARP table correctly, it is built in memory via broadcast from devices in the network. So what is broadcasting the .117 address with a MAC of all zeros?

After writing all this up, I’m now wondering if it is an ASUS issue.
 
I believe this is normal for mesh and AP's.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top