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.
So I did some more testing.
I've reset the router several times to start from default.
Each time testing the DHCP settings and reservations.
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.
I have other Netgear routers that do not exhibit this behavoir. The router that this one is replacing is a DGND3700v2 and it performs just fine with these settings. As a matter of fact, I've used these settings for a majority of my "LAN" life....
And now this Netgear router chokes. Possibly it's the Firmware Version? Maybe I need to reinstall an earlier version?
Otherwise I guess I'll have to become a new customer of a different brand of equipment.
Does anyone know where I can get files to downgrade my firmware?
> [...] 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....
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.
shadowsports wrote:
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.
Welcome to the wonderful world of crap firmware!!
Netgear does not seem to be able to put out a good firmware build. Problems that have been identified for months are still not fixed. Seems they do not even test for known issues before they post a new build. Not a good way to run a company IMHO.
Thanks. I have .42 installed now, so the suggestion is not to upgrade?
What would be the reason or a link to the conversation about why not to upgrade?
I have always used the "Outside of the DHCP Pool" for static IP's and I typically keep my DHCP pool to a minimum just as another layer of security. I know how many clients should be on my LAN.... Each one has a reserved address. We don't need to serve more IP's than than we have MAC addresses. It's a way of MAC address filtering.
I'll try the above/below concept. Reservations were working as long as the Router IP was a x.x.x.1
If that doesn't fix anything, I have created a support ticket for it and now my plan is to keep the Router IP at x.x.x.1 and manually enter all my settings and then create a configuration file. Then change the Router IP to x.x.x.2 and move on.... if I need to update the configuration in the future, I'll need to reload the configuration file first to get my x.x.x.1 back and then do my update and save that config file and then change the router back to x.x.x.2
I can't believe that a company like NetGear is allowing DHCP and IP issues like this to happen.
Thanks Again.
I've received a reply back from Tech Support.
"May i know why you are trying to change the IP address, why you are doing IP reservation, may i know the main issue you are facing with the device?"
I'm trying to be nice...and I opened the support ticket with a very sensible description of the problem.....
..... and support asks me why do I want to make changes to the router?
I went to a Doctor once and told the Doc that my arm hurts when I move my arm to out to the side.....
The Doc told me, "Well then, I suggest that you don't do that movement with your arm and you will cease to experience that problem"...
I wonder where support is going with these kinds of questions.....
