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...
Do you have any network switches in between the satellite and router or on your network?
I would probably return the unit or ask for an RMA. Something about DHCP services on this isn't working. Seems odd that your only experiencing this. Maybe others are and just haven't reported it. One users mentioned the other day that changing IP address pool to something smaller helped him as he seem to be seeing odd DHCP behaviors similar to what your seeing. Reason why I mentioned it.
Ethernet back haul is working for others so you may have just a bad package, I would see if NG would RMA it or go find something else.
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.
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.