NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ORBI not properly associating static IP
Hello! I've been trying to use the Address Reservation feature under Advanced -> Setup -> LAN Setup. I have a PC that is hardwired (Ethernet, not wireless) to the RBS50 satellite (not the base RB...
I know this is an old thread but I was having the same problem with reserved addresses not getting assigned. I tried the "trick" of changing the DHCP addresses from x.x.x.21 to x.x.x.254 TO x.x.x.21 to x.x.x.100.
Restarted the devices that were not getting the addresses I wanted and it all worked. I had tried restarting the devices prior to changing the auto assigned addresses range and it did not work at that time. Only after changing the range of the auto addresses.
I know enough to know that should not change the addresses I wanted reserved. Nothing was assigned in the >100 range in the first place. All I know is it solved my problem.
Lets remember that for "Static" IP addresses, these are configured and placed ON devcies themselves. So if static IP addressed devcies are being used and connected, then these static IP addressses need to be outside of the default DCHP IP address pool. For NG routers, NG defaults to max pool size, so users need to reduce the pool size to allow for static IP addresses to be used OUTSIDE of the IP address pool.
For IP Address "Revervations", these are set ON the Router for devices and these are always with in the DHCP IP address pool.
Let's remember that the word "static" just means "not changing". Whether an IP is not changing because it is configured at the host or because the IP is reserverd for a specific MAC at the DHCP server, it would still be a "static IP". However, that leads to confusion, so I've tried to avoid that phraseology. In my post, I tried to be carefull to use the phrase "statically assigned" to refer to IP reservations on the DHCP server. If there's an accepted standard terminology to discriminate between those two, I'd love to hear it.
Cisco uses the term static DHCP.
I also see DHCP reservation used by vendors.
Your term of statically assigned seems equally fine.
I agree with FURRYe38 that static IP without any qualifier generally implies "set on the device itself".
It's not clear to me if the "problem is solved" and the discussion has moved on to semantics, or.....
