NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Cannot Update Settings
Brand New Nighthawk R7000 right out of the box.
Got it setup basically, username/password/ssid/WiFi/Lan/WAN and it connects to the Internet.
Login and update the firmware to the latest V1.0.9.64...
I've seen address reservation work differently (at times) on all 4 of my routers with various FW versions.
My reservations live below my DHCP pool. On the Orbi however, I believe my reservations had to live within the DCHP pool range. Don't remember, sorry.
antinode hit the nail on the head. Its a bug. A silly one most of us just deal with. He is also correct about 1.0.9.42 thats the FW you want to use with your R7000. Suggest you downgrade and disable Automatic Update.
> [...] and update the firmware to the latest V1.0.9.64_10.2.64 [...]
So, no longer "right out of the box".
A Web or forum search for terms like, say:
R7000 1.0.9.64 [or "V1.0.9.64" or "V1.0.9.64_10.2.64"]
might be informative/depressing. ".42" might work better.
Visit http://netgear.com/support , put in your model number, and look
for Downloads. (For older versions, under Firmware and Software
Downloads, look for "View Previous Versions".) Find the kit(s).
Download the kit(s) you want. Read the "Release Notes" file for
instructions.
> I updated the Lan to: 192.168.0.2 as routers IP, [...]
Why the odd-ball (not ".1") LAN IP address?
> [...] The IP address should be within the DHCP range... [...]
> [...] and my IP changes didn't update. [...]
Sounds like a firmware bug and/or scrambled settings. Especially
after a firmware update, I'd try a settings reset, and manual
reconfiguration.
> [...] Reservations will work as long as the router is on 192.168.0.1,
> but if the router is on a different address, like 192.168.0.2, the
> reservations fails with the Must Be In Range Error. [...]
Sounds like a bug, but why you'd want use that address is a mystery
to me.
Thanks for the feedback. I've already looked for a firmware update of previous versions but I didn't see anything......
I'll go look again....
I just finished another experiment of leaving the router on 192.168.0.1 and adding several reservations which worked just fine.
Then I set the router to 192.168.0.2 and it rebooted just fine and I logged into the new IP. But it wouldn't allow me to add anymore reservations. I tried returning it back to 192.168.0.1, but after reboot it was stuck on 192.168.0.2 and wouldn't process reservations.
Yes, I agree, I think it's a bug. There are about 60 pieces of equipment on that LAN... mixed with static IP's and with dynamic and at one time, there was a static 192.168.0.1 XEON machine on the LAN.
But it should work...regardless.
I also want to avoid a massive update session...especially if it's related to a software bug in a router.
I found previous versions.... I overlooked it last time....