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.
SdeGat wrote:
CrimpOn isn’t it a good (easier) practice to have a range of addresses that the router will not use/assign?
Or are the Orbi routers more intelligent and automatically recognize fixed addresses in devices and leaves them alone?
It is uncommon in a forum post to see "Orbi" and "intelligent" in the same sentence. There are constant complaints about the way the router fails to honor assigned IP's. I personally struggle when I get a new device and know what IP I want it to have but the manufacturer has failed to put the MAC address anywhere on the product or the packaging. Once it gets connected, the *&*%^* Orbi allows it to keep that first IP even though I have created an entry in the IP assignment table and then powered the device off and back on. My practice with these devices is to connect it to a junk WiFi router that I keep sitting around, just so I can learn the MAC address before connecting it to the Orbi.
(enough Rant. sorry)
In general, the accepted practice is as you described. Set aside a set of IPs for device assignments and a separate set of IPs for the DHCP pool. With 250 IPs to choose from, there is no fear of "running out" of either. For example, 2-100 for assignments and 101-250 for DHCP is a common practice.
CrimpOn wrote:In general, the accepted practice is as you described. Set aside a set of IPs for device assignments and a separate set of IPs for the DHCP pool. With 250 IPs to choose from, there is no fear of "running out" of either. For example, 2-100 for assignments and 101-250 for DHCP is a common practice.
Going back to this, it looks like the RBR50 does not support the setting up of a range, does it?
- On the web interface, LAN setup menu
Well.... actually 0 doesn't exist and 192.168.1.1 is taken already by the router, leaving 2 - 100. Still plenty of IPs to use.
Static routes are an entirely different concept than assigned IP's.