NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Edit/Add new IP reservations
I have an RBR50v2 Orbi router and 2 satellites with FW ver 2.7.5.6. I have entered 15, or so, reserved internal IP addresses using "Advanced > Security > Access Control". All works well. The is...
So the "pool" is defined by "Use Router as DHCP Server" with a Starting and Ending IP Address range? And the "undefined" range is not used at all, correct?
FYI, Been a long standing standard networking practice for a long time, IP address RESERVATIONSs should be with in the DHCP IP ADDRESS POOL, i.e. 192.168.1.100 to 192.168.1.200 can be a pool range. STATIC IP addresses are set ON devices and are set outside of the DHCP IP ADDRESS POOL range. Either side of the afore mentioned example range is out side of the pool and can be used by STATIC IP addressed devices. IP address reservations are handled and managed by the DHCP service inside the pool, not outside of it. How it's designed. IP addresses are first Dynamically handed out to devices making a connection. If an IP address is already taken by another, then the next 1st available address it given out. Even if the IP address is already RESERVED in the DHCP pool range, then the next availble IP address is given out by the DHCP serivce, regardless if it's Dynamic or Reserved. How the DHCP system works and intended how to work for most home class router systems.
So the "pool" is defined by "Use Router as DHCP Server" with a Starting and Ending IP Address range? And the "undefined" range is not used at all, correct?
https://kb.netgear.com/25722/How-do-I-reserve-an-IP-address-on-my-NETGEAR-router
Even if the IP address is already RESERVED in the DHCP pool range, then the next availble IP address is given out by the DHCP serivce, regardless if it's Dynamic or Reserved.
I don't think this bit is correct. The reserved IP address is locked to a specific MAC address, and should not be given out to any other device.
If it didn't work this way, then rebooting the router would result in a big mess. The client devices request addresses in a pretty random order, so the reservations would largely be ignored.
While keeping the reserved addresses out of the pool eliminates any possibility of the DHCP server assigning a different address, this extra precaution really shouldn't be necessary. For instance, see this tutorial:
- https://www.manageengine.com/products/oputils/tech-topics/dhcp-reservation.html
- IP address reservation: Once you have identified the MAC address of the device, reserve IP addresses for each MAC address in the DHCP management console. This involves associating the MAC addresses within a fixed IP address in DHCP server's IP pool.
Yes the reserved IP address IS tied to the MAC address. However again, regardless if Dynamic or Reserved with MAC addresses, the DHCP system manages this. Dynamic can change if the lease time expires and the device hasn't asked or re-connected to get a new IP address. Hows it's designed to work with IP addresses IN the DHCP pool range. Reservation/Fixed are the same thing. Be sure you don't mix Reservation/fixed with Static. Static IS an IP address set ON a device, not the router and Static IP addresses are NOT with in the DHCP pool range. IP address Reservations are set ON the router/DHCP Service and within the DHCP IP pool range. About terminology here as well. You could say fixed is a static as well. Why I don't use fixed and be more exact. Reservation and Static are networking standards.
Been like this for years and trust me, have done lots of reboots with IP address reservations and static IP addressed devices. All my printers, cameras, controllers, AVR, Projector and NAS are all Static IP addressed, OUTSIDE of the DHCP IP address pool. I let the DHCP service handle all IP address reservations with in the DHCP pool range. Currenlty only have RBS set for IP address reservations, WITHIN the DHCP pool. All other devices, phones, PCs and IoT are Dynamic IP addressed. Also took networking education as well on this.
About terminology here as well. You could say fixed is a static as well. Why I don't use fixed and be more exact. Reservation and Static are networking standards.
FWIW, I use the terminology the same way (the tutorial I quoted used "fixed", but I don't myself). Though I always recommend reserving IP addresses and not using static addresses configured in the clients. One reason is that using static addresses makes it more difficult to switch to a different subnet (which often ends up happening when people get a new router). Another is that managing the addresses from one place (the router) makes it much easier to avoid address conflicts.
I don't think FCO100 is using static addresses (at least nothing in the discussion thread suggests that). But as you say static addresses do need to be outside the pool. With Netgear routers, reserved addresses can be either inside or outside the pool (as your KB article says, you can reserve any address in the subnet). But if you use static addresses also, then it is best to reserve addresses in the pool (as you are doing).
In your earlier post it sounded like you were saying that DHCP would assign an address reserved for one client to another client if correct client was not connected. Sounds like I misunderstood that.
