RBR750 Firmware Bug Report: DHCP Table Fails to Rebuild Automatically After Power Outage

This does not match my experience.

One RBR750 and one RBS750, both running firmware v7.2.8.8_5.1.24.  There was no Factory Reset after the firmware was updated.

This RBR750 is connected to my primary network, and thus the router creates its LAN as 10.0.0.x, with DHCP pool from 10.0.0.10 through 10.0.0.254

Windows laptop connected running Wireshark to capture Ethernet connection to the router, with display filter to show only DHCP packets.

The laptop had IP of 10.0.0.13.

When the power to the router was disconnected, both the laptop and the satellite lost connection.

Power was restored, and after a few seconds the laptop began sending DHCP requests to the router (and getting no response).

Each of the requests was asking for the IP address that the laptop was using (10.0.0.13)

A total of 18 requests went by, for a total of about 100 seconds (not precise)

The 19th request got a response from the router, offering the IP 10.0.0.13.

This is exactly what one would expect to happen.

• When power is applied to the router, the Ethernet module becomes active electrically, but the router has not finished booting up and thus there are no responses.
• When the router begins to process DHCP requests, it sees that 10.0.0.13 is "available" because no other device is using it, and thus assigns it to the laptop.

Netgear61 wrote:

connected local network devices fail to automatically obtain IP addresses or reconnect to the network.

This is not my experience.  True, I have only one satellite and one laptop connected to the RBR750 router.

Does this happen to every device on the network? (both Ethernet and WiFi?)

Is it possible to set up Wireshark on one of the local connected devices and monitor what happens when power is cut to the RBR750?  It would be really interesting to see the actual DHCP traffic.

Some years ago, I had a laptop that I would "put to sleep" by closing the lid (to keep the cat off the keyboard).  When I opened the lid, it would have no internet.  Drove me CRAZY.  Had to go into the Windows Troubleshooter or restart to get a network connection.  Finally, I used Wireshark to capture the Ethernet connection and found that the laptop was broadcasting DHCP requests, the router was responding to every one, but the laptop just ignored the responses and asked again (and again, and again).  A year later, software update on the laptop and the problem went away.