New - XR1000 Firmware Version 1.0.0.68 Released

[laneyy · Accepted solution]

Looks like the issue for me is something to do with DHCP (yes I had the range set as 100-200) I set up my own DHCP server and set the lease time to 1 week and it's been stable ever since

[Netduma-Fraser]

Thanks for the update, good to know our theory is correct, it is something we've passed on before and will have to wait for NG to fix.

[laneyy]

Is there any updates for this? It's been 3 months now since I've raised the dhcp issue

[Netduma-Fraser]

We haven't heard anything from Netgear unfortunately, may be worth raising a ticket with them specifically.

[Ur3]

Hi!

Thank you for sharing this useful information.

[Raustal]

Hey Fraser. Would you mind explaining what is happening in regard to the DHCP issue? What is the rationale behind changing the range? What problems is it causing, etc.

Thanks for your time.

[Netduma-Fraser]

@Raustal sure thing, so the issue as far as I can tell is that when the DHCP lease renews it's kicking devices offline, now this isn't unusual if a device is getting a new IP but it should reconnect so quickly that it shouldn't be noticeable at all but that isn't happening. Leading me to believe there is an issue with the lease aspect of DHCP. Adjusting the range to a higher value provides a block of IP addresses that are unaffected by the lease, setting these as reserved for devices means they'll never change IP addresses.
You may think then that changing the range shouldn't matter but for some reason it still occurs if the IPs are within the range.

[FURRYe38]

New FW available:

https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/New-XR1000-Firmware-Version-1-0-0-72-R...