NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DHCP issues on RBR350
Dear community. I purchased an RBR350, with 2 satellites, and I have had issues with it ever since the start. I'm currently running the latest FW. I have one satellite wired and one Wi-Fi. Th...
kingkevbo wrote:
I connected using a static IP, logged into the router's debug page and enabled logging. I then put my PC back in DHCP mode and tried to connect to the Orbi a number of times to no avail. I then connected via static IP and downloaded the log.
If you enabled the feature "Enable LAN/WAN Packet Capture", then the debug log will include two files: wan.pcap and lan.pcap.
Open lan.pcap with Wireshark and it should contain the DHCP conversation between the laptop and router.
I had a similar (but not exactly identical) problem with a Windows 10 laptop which was connected to an Orbi with Ethernet. I never turn my computers "off", but did close the lid when away from the laptop (cat walks on the keyboard). Every time I would open the lid, there would be no network and I would have to either (a) use the Network Troubleshooter, (b) open Network Settings to disable/enable the adapter, or (c) restart the laptop. Finally I captured the DHCP packets and discovered as you did with the switches that the laptop sent DHCP requests over and over and ignored the DHCP response from the router. A subsequent software update on the laptop resolved the issue.
I am not a fan of Netgear's DHCP software, but when it is one device having a problem....... well.
CrimpOn wrote:
kingkevbo wrote:I connected using a static IP, logged into the router's debug page and enabled logging. I then put my PC back in DHCP mode and tried to connect to the Orbi a number of times to no avail. I then connected via static IP and downloaded the log.
If you enabled the feature "Enable LAN/WAN Packet Capture", then the debug log will include two files: wan.pcap and lan.pcap.
Open lan.pcap with Wireshark and it should contain the DHCP conversation between the laptop and router.
I had a similar (but not exactly identical) problem with a Windows 10 laptop which was connected to an Orbi with Ethernet. I never turn my computers "off", but did close the lid when away from the laptop (cat walks on the keyboard). Every time I would open the lid, there would be no network and I would have to either (a) use the Network Troubleshooter, (b) open Network Settings to disable/enable the adapter, or (c) restart the laptop. Finally I captured the DHCP packets and discovered as you did with the switches that the laptop sent DHCP requests over and over and ignored the DHCP response from the router. A subsequent software update on the laptop resolved the issue.
I am not a fan of Netgear's DHCP software, but when it is one device having a problem....... well.
I got the capture files. It seems there is a DHCP offer that that the PC did not take for some reason. This was the same as what the Tasmota devices were doing. If there is someone that would offer to take a look at the logs that would be great.
Understand that when one device is having an issue, then it likely points to that, but how would it be explained that after a reboot of the PC and multiple adaptor disables/enables didn't fix it, but a reboot of the orbi did, that it is not the orbi that is the issue? Could the offer packet be malformed or something? This would also explain the earlier behavior of the Tasmota devices.
kingkevbo wrote:
Understand that when one device is having an issue, then it likely points to that, but how would it be explained that after a reboot of the PC and multiple adaptor disables/enables didn't fix it, but a reboot of the orbi did, that it is not the orbi that is the issue? Could the offer packet be malformed or something? This would also explain the earlier behavior of the Tasmota devices.I am no expert, but really enjoy going "down the rabbit hole" on technical issues. Would like to compare the DHCP conversation from normal operation against when the router is powered up (and the whole network gets DHCP assignments). If the laptop ignores one offer and responds to another offer, there ought to be something different between the offers.
One thing about Netgear's DHCP process that annoys me is that it does not prioritize the LAN assignment table. Got a new camera yesterday and (before connecting at all) put it in the LAN assignment table, but made a typo on the MAC address. (teeny tiny print is my excuse.) ) So, the camera got a random IP from the pool. Corrected the typo and restarted the camera... same IP from the pool. "No, problem." Powered off the camera and set a laptop to that IP (Static assignment on laptop). Powered up camera, next sequential IP from the pool. The only guaranteed way to get the correct IP assigned is to reboot the router.
I think you are correct that Netgear's DHCP process is doing something not obvious.