NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
R6400 - Device Name in Attached Devices vs LAN Setup?
On my LAN managed by an R6400 router, I assign static IP addresses to virtually everything. I want to KNOW what devices are on what IP. Using the LAN Setup page in the router's firmware I have done t...
Static IP addresses are given to the device(s) itself, not on the router which are called "reserved IP addresses". DHCP does this. Do you really mean static or reserved IPs?
Which firmware version? (not "the latest", a number)
If Attatched Devices can't get a meaningful name from a device (eg, device returns nothing), it gives it a double dash
Thanks microchip8!
You write: Static IP addresses are given to the device(s) itself, not on the router which are called "reserved IP addresses". DHCP does this. Do you really mean static or reserved IPs?
I may have my terminology a bit messed-up. In the router's admin pages, under Advanced->LAN Setup it calls it Address Reservation and this is under DHCP (which is enabled). This is what I am talking about. Sorry...
To me, this seems like assigning a static IP to a MAC address. None of these devices ever end up with some IP other than what I have specified here. I imagine that the router has a table of MAC addresses (along with the other info I have entered) and that when a DHCP request comes in from a given MAC, this table is consulted first and, if a matching MAC is found, the IP I have specified is returned/assigned. Perhaps nothing like this happens and I am all wet. But it sure seems this way.
Given the above imagining, it would seem like the device name I have given (so long as it conforms to hostname requirements) would be used by the router's DNS to resolve local hostname references (as in my ping requests). It appears to do this in some cases but does not in most. This inconsistent behavior is what I find confusing. If it simply did not ever work, I would have concluded that either I am an idiot (which remains quite possible) or that the router just does not do what I imagine it would be logical for it to do.
I am firmware V1.0.1.42_1.0.28. I know this is old but when I tried to update some time ago things got quite hosed up and I have simply avoided doing so since then.
Cheers