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.
I agree with Mstrbig that one "sure fire" method is to (a) assign a static IP in the PC control panel (with the correct subnet mask, gateway, DNS server, etc.) and (b) make sure that this IP is NOT in the range of IP's that the Orbi DHCP server is giving out.
There are some definite issues with the way Orbi handles DHCP. For example, it appears to allow devices to renew an existing IP that is not the IP in the reservation table. Seems like "you already have it, so you can keep it." takes precedence over, "Hey Buddy. That IP does not belong to YOU." There have been other posts about errors in Orbi DHCP management.
That said, my Orbi correctly handles all of the devices that have assigned IP's. All of the devices use DHCP and once I got them on the correct IP they have stayed for months. Being attached to the router or satellite has never made a difference.
There have been issues come up when it turned out there was a second DHCP server in the network. This computer that is a "server", for example, is not doing DHCP is it? There are some odd-ball devices that do DHCP.
CrimpOn isn’t it a good (easier) practice to have a range of addresses that the router will not use/assign? Then, whatever address the user assigns to a device (from that router excluded range) will never create a conflict?
I think Linksys routers always came with such a range and I would pick fixed addresses from it without issues (without having to do anything on the router).
Or are the Orbit routers more intelligent and automatically recognize fixed addresses in devices and leaves them alone?
That's probably a sensible methodology, but I'm not sure that the appliance should be forcing the user to do that, as there might be reasons why the user doesn't want to move a device's IP to another range. Maybe it took them a long time to get some other devices to interact with it, and they don't want to risk another slew of configuration changes they'd need if they changed it's address.
Also, I believe some DHCP daemons do the opposite of what the ORBI does, where manual IP assignments must be within the overall pool of IP's which the daemon is allowed to assign. So, for me, anyway, it's counter-intuitive.
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.
Thanks for the insight CrimpOn. You know I don’t mind the rant. 🙂
BTW, where did the “quote” function go? 💁♂️
The Quote button has been replaced by that ginormous double quote mark on the menu bar. and the other options only show up if you click those three dots (...) and there appears to be no way to "go back" (sigh)
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