NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DHCP reservations not working
Yesterday I added a raspberry pi to my network (running Nagios/NEMS). Every time it rebooted it took the next IP in sequence. That shouldn't happen... Instead of fighting with it, I created a reserva...
I likewise had this issue, and a reboot of the router corrected it. I reported the issue to NG support, and they claimed the system firmware is "glitching" causing this. They admit that the firmware is still a bit buggy with v2.5.1.8 on the RBR50, but have no ETA on when they will have a stable and reliable mesh network.
OrbiPhilip some RasPi distros or redy-to-run environments are configured to change the network interface MAC addresses with every boot.- try some search, we had this issue (which is not an Orbi problem) several times in the Netgear community already.
One example here: https://community.netgear.com/t5/Orbi/ORBI-RBR50-not-honoring-reserved-IP-addresses/m-p/1839574/highlight/true#M78798
That was the first thing I checked. MAC is consistent. Reboot fixed the problem, but the DHCP entry still does not appear in the logs.
It appears these things now need daily reboots. Unforunately, no scheduled reboot feature exists. Or a log of DHCP reservations. Or....
schumaku wrote:OrbiPhilip some RasPi distros or redy-to-run environments are configured to change the network interface MAC addresses with every boot.-
OrbiPhilip wrote:That was the first thing I checked. MAC is consistent. Reboot fixed the problem, but the DHCP entry still does not appear in the logs.
Can you please clarify:
- The Orbi log contains DHCP assignments for every device except this one, or
- The Orbi log contains no DHCP assignments for any device
Thanks
Can you please clarify:- The Orbi log contains DHCP assignments for every device except this one, or
- The Orbi log contains no DHCP assignments for any device
Before reboot the log contained many DHCP entries in the form of:
[DHCP IP: 192.168.1.xx] to MAC address xx:xx:xx:xx:xx:xx, Friday, February 21, 2020 17:35:58
Not none matched the IP or MAC of the Pi.
After reboot I connected to the Pi on 192.168.1.59 and rebooted it. It leased the address listed in the reservation (192.168.1.56). The log after reboot contains *no* DHCP entries.One problem that the Orbi system seems to have is the lack of ability to manually drop a DHCP entry from the table. As such, any device getting a DHCP address will continue leasing that address until the router is rebooted.
This is especially problematic when you give a device (including the Satellites) a DHCP reservation for an address other than the one auto-assigned. Anytime a given MAC is added to the reservations list, it should be dropped from the database if the IP changes.
