NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WAX220 Client Connections Screen
Hello,
I have this AP as a standalone at home environment replacing an old dlink unit which was solid byt replaced it due to age and no longer receiving updates.
What Im seeing with he WAX220 is that clients will appear with No IP address as you see below even though they are working fine and clearly pulling a DHCP from the router.
Anyone else seeing the same and what causing this and is it an issue?
thank you
After being associated to the WAX220 for more than 48 hours, on reviewing the connection status, we find again some 0.0.0.0 in the IP address field however.
Yes, it's "just" a nice to have feature, and we have better ways for finding the device IP address - however it's part of the design and implementation, so we expect this works 24*7..
4 Replies
Randomly, I have seen the similar issue where a connected device does show up with an unresolved 0.0.0.0 IP address. Rarely, even two of my test devices are affected, and sometimes show up with an unresolved IP address 0.0.0.0.
Special MAC addresses (like randomized MAC) don't make the difference, so the result purely random.
Sometimes the IP does show up after roaming between the 2.4 and the 5 GHz association, even if there is no new DHCP association active.
Probably related - but clear why some devices refuse to provide a valid hostname or the like making these show up as an "unknown" device.
No effort taken to look into the Open Source code for hat probably well-known code is in use to propagate this table properly, certainly a little issue does exists.
DUT: WAX220, v1.0.3.3
After being associated to the WAX220 for more than 48 hours, on reviewing the connection status, we find again some 0.0.0.0 in the IP address field however.
Yes, it's "just" a nice to have feature, and we have better ways for finding the device IP address - however it's part of the design and implementation, so we expect this works 24*7..
Yes that's correct 1.0.3.3 however its been doing it since I had it in service (maybe two F/W revisions back as well). Its not that its causing any issues that I noticed yet , but still a weird bug.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
