NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Problem with LAN Setup, Address Reservation
Hello,
Nighthawk X10 R9000 - Router Firmware Version V1.0.4.28
The router is functioning perfectly: fyi...
However, I have three devices that I add to the LAN Setup, Address Reservation -->...
Use this as a guide, modify accordingly.
LAN address of router: 192.168.1.1
DHCP Pool 192.168.1.100 ~ 192.168.1.200
Assign a static IP, subnet mask and gateway to the Dell's NIC which is above or below the DHCP pool range specified above.
or
Re-enable the Address Reservation. Assign an IP which is (again) above or below the DHCP pool you've specified to the Dell's NIC MAC address. Leave DHCP enabled on the NIC, disable / enable the interface. It will grab the IP you specified in the reservation.
If you use my suggestion(s), the IP will never change, no device will ever get the Dell's IP and your port forwarding will work without issue.
Hello,
Use Router as DHCP Server
Starting IP Address 192.168.10.2
Ending IP Address 192.168.10.254
Tried to go with your Option #2 -->
assigned 192.168.10.300 to the Address Reservation
The Netgear Nighthawk X10 R9000 did not allow this....
Tried to go with your Option #1 -->
assigned the Dell NIC as 192.168.10.300
The Dell NIC gave me a red box -- so I could never save it ?
I tried as a static IP the IP the Netgear router gave me: 192.168.10.21
It seemed to catch after reboot -- however, a browser could not browse etc -- so I went back to DHCP
So far the router has kept the IP address of 192.168.10.21 -- but who knows - :)
I have to admit -- all other routers - when I specified Address Reservation -- it was solid -- and it kept that address!!
!!!!!!!==> I think this is a bug in the firmware (hello Netgear admins!!!!) <==!!!!!!!
Thank you 'shadowports' - any other ideas will be appreciated
Read the response to you again.
192.168.10.300 is NOT 192.168.1.200.
Two things here...
- The router can only have 255 IP Addresses, it takes 1 and 192.168.1.255 is the last and used for logging. The whole idea is to have 2 pools of IP Addresses so there is no collision between DHCP handed out and Reserved/Static IP Addresses, Setting the pool to start at 100 usually will fix that problem.
- You have to set the pool to start with a VALID Router IP Address. Usual default IP Address would be 192.168.1.1 or 192.168.0.1. 192.168.10.1 is NOT a normal IP Address for the router.
You can find the IP Address of the router when you SIGN INTO IT... that URL is the IP Address of the router. You'll also find that on the GUI Advanced tab in the Router Information box. Use the first 3 octets and then add .100 and 200 for the fields starting and ending address for the DHCP server (this first 3 octets should already be filled in), but in any case the ending address can't be greater than 254 (which should have been set to). All you needed to do was change the START>
> The router can only have 255 IP Addresses, it takes 1 and
> 192.168.1.255 is the last and used for logging.A "255.255.255.0" _subnet_ can have only 256 addresses, ".0" -
".255". ".0" and ".255" are reserved, and the router needs one for
itself (by default, ".1", but you could change it if you really wanted
to). That's why the default DHCP pool range is ".2" - ".254".".300" is too large (> 254), hence "did not allow this....".
> 192.168.10.1 is NOT a normal IP Address for the router.
Not really. As a router LAN address, "192.168.10.1" is just fine.
antinode, yes, should have said 256.
As for 192.168.10.xxx, that is not the normal default though. If that is what in use, either the OP changed it for some reason, there was a typo (as in the fields that need to be changed the first 3 octets are filled in on the LAN SETUP page.
Of course 300 can't be used, but it was never suggested, so it too might have been a typo.
Yes, these are all possible for a Private LAN IP Address:
RFC1918 name IP address range host id size 24-bit block 10.0.0.0 – 10.255.255.255 24 bits 20-bit block 172.16.0.0 – 172.31.255.255 20 bits 16-bit block 192.168.0.0 – 192.168.255.255 16 bits If the OP changed the default one would expect that the range of valid addresses would be known? If it was done automatically I wonder what is in front of the router? Could be part of the problem here?
> As for 192.168.10.xxx, that is not the normal default though. [...]
So what? "the default" and "the only possible" are spelled
differently for a reason.> If the OP changed the default one would expect that the range of valid
> addresses would be known? [...]Your expectations may be too high.
> [...] If it was done automatically I wonder what is in front of the
> router? Could be part of the problem here?I doubt that it was automatic, or that it is significant.
So far as I can see, the "300" was the biggest problem here. When
that gets straightened out, then perhaps Address Reservation will work
as expected, and we can get back to whatever the original problem might
have been with the "A older DELL machine".
1) My Starting IP Address 192.168.10.2
My Ending IP Address 192.168.10.254==>>> Actually I did choose '10' instead of the default '1' (e.g. xxx.xxx.10.xxx) -> That works fine...
2) In the original post it stated: "...the Dell's NIC which is above or below the DHCP pool range specified above..."
==>>> I do not know what the hell I was thinking!! ;) I was think that was saying higher than 254....
3) I have now implemented Option #2 in the original post -- Which is what I have been doing without the "enable/reenable NIC" part -- However, I am still not sure of this yet, since when I would reboot the Dell machine, the NIC was reenabled on startup: AND this is where I was seeing the issue (a hanging not connecting, etc)
4) I suppose if I still have issues, I should try the static IP test....
Thanks to IrvSp and Antinode for the extra help!!