NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DHCP Address Reservations not Working
Hello all...
My setup:
AT&T GigaPower Fiber (1000/1000) with 5 Public Static IP Addresses
The RBR50 is hooked into the modem and is assigned one of those PUBLIC STATIC IPs, and bypasses the...
Have you done a factory reset and set up the router from scratch and then set a IP address range .100 to .200?
If this still fails, you might try a manual re-load of the FW file on the router, factory reset after the FW load and try again to set a IP address range of .100 to .200 and test.
If the router doesn't honor the new IP address range and keeps giving out IPs outside of this range, I recommend that you get ahold of NG support and have them RMA the router.
junktrunk wrote:
I came across this page while searching for a solution to a problem I was having with my Orbi (RBR20 with 2 RBS20 sats) and their lack of honoring DHCP reservations. Given the lack of SNMP support in this router (unless I'm mistaken?) it was unnecessarily difficult to diagnose, but I found through using Wireshark that I was indeed correct that the router was making incorrect DHCP assignments. It turns out that my issue was resolved by changing the router's "Starting IP Address" and "Ending IP Address" range (within the "Use Router as a DHCP Server" setting under Advanced->Setup->LAN Setup) such that that range *includes* the IP addresses that I'm using in the reservation. When I had my range set to .100-254 and had a reservation set for .60, the router ignored that reservation and gave my device an address witin 100-254. When I opened the range to 60-254 and rebooted the device, the router gave it the correct .60.
This is not normally how DHCP reservations are implemented in other routers -- typically you can set the reservations to whatever address you want, and the range is only used to designate the pool to use for non-reservations. I'm a little worried that it'll end up assigning the same IP twice now (which is one reason to set the pool to avoid any conflicts) but I will hope for the best. I hope this solution works for someone else too who was confused and struggling to find an answer.
Thanks for the follow up. Just in case my previous post wasn't clear, it's not that the router was giving addresses outside of the start-end range. It was that if a reservation was created for an address that was outside that range, the router chose to ignore the reservation completely and instead give an address within the range. When I adjusted the range to be wide enough to include the reservation addresses, it correctly assigned those addresses to those devices. I don't see other routers interpret the range so strictly. At a minimum I think the user should receive a warning if the range and reservations are in conflict and will generate unexpected problems.
Just to be clear, IP address reservations need to be given while Inside the IP address range, not out side of it. Any IP addresses out side of the IP address range are meant for Static IP addressing that are set ON the connected devices only.
junktrunk wrote:
Thanks for the follow up. Just in case my previous post wasn't clear, it's not that the router was giving addresses outside of the start-end range. It was that if a reservation was created for an address that was outside that range, the router chose to ignore the reservation completely and instead give an address within the range. When I adjusted the range to be wide enough to include the reservation addresses, it correctly assigned those addresses to those devices. I don't see other routers interpret the range so strictly. At a minimum I think the user should receive a warning if the range and reservations are in conflict and will generate unexpected problems.- Yeah I got that. My point was that there's no reason for such a limitation to exist. I should be able to say I want dynamic IP assignments to be from a certain pool of addresses, but I want certain devices to be able to be assigned whatever address I set, whether inside the dynamic range or not. There's no technical reason why that shouldn't be possible, as I did it all the time before on D-Link equipment.
Also at the very least the Orbi should make more clear that that's not supported.Well since Orbi is a home class router, not much call for advanced DHCP addressing. I think most averages users just want simple addressing where needed. Anything beyond that is not useful for most and thus probably why NG isn't supporting anything advanced DHCP features like other mfrs. NG chooses to run there systems they way they see fit. DHCP Addresss Reservations IS working on Orbi. The behavior of DHCP and reservations is for only inside a pool range. Anything outside is not supported for reservations. Anything outside a pool range is meant for static IP addresses which are set ON devices. Not on a router. This is normal networking standards btw.
Good Luck.