This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
For me, I always keep a copy of proven good f/w to fall back. For certain f/w release which involves new whole module like radio chip driver coming out of Broadcom, or Qualcomm, new versaion of Linux Kernel, I'd hard reset before and after flashing(just like treating router is just out of box) I manually reconfigure. Other times I just restore saved config. file. Doing this, I never ran into a dead router
or anything like it. Well if router is dead, then I'll unbrick it taking time. If router is little old one, I don't care. I'll just get another equal or better one. Also I always keep spare stand by router for temporary use handy. This way our home network up time is ~100%.
Now, I am scared to try 1.0.5.70_1.1.91, which my router wants me to upgrade to. Is anyone running this for some time without issues already?
Won't it depend on the release note? Is there anything relevant to your router useage? Anything interesting? If it is not to your liking after flashing, have a fall back plan?
There are a few ways to do the allocation for saving settings. One way would be independant locations. Those can possibly change during a build. Another safer way is to allocate a block of storage at a known location and manually assign stuff sequentially to it. Always adding new data after the old. That way unless the setting should grow for some reason other settings would not change, but the rub then is the old setting might not be good either.
Of course that assumes source code is controlled and the programmer(s) know what they are doing.
Also when the flash is performed ONLY the code portion should be replaced, in its entirety. Not the data, nor should the data be damaged.
You do have some different parts though in a flash. The basic router code, the GUI, and the OS. It is quite possible new versions of those could make the data subject to being changed. However one would expect NG to CLEARLY state this and declare the need to re-install settings manually. However I would still think there is NO GOOD reason why the router code couldn't read the same settings data and store it in the proper place. Format of the saved settings really doesn't matter as long as the router code can read it and store it properly. If it can do it for the existing flash without a problem I don't understand why another version can't? I can understand a downgrade as it might have a new setting the lower version can't understand/handle, but even in this case why can't it just 'throw it away' if it doesn't recognize it. Laziness on NG's part or poor code management?
================
I've been use .70 since release and have NO problems with it, but I have found errors along the way. Of course there is no way for me to verify every single possible combination of settings and LAN/WAN configurations either. All I can say is that it works for me I guess.
I'm using a WNDR3700 V2 router, that is showing exactly the same problem as described here : no internet access for 2.4GHz, but working well for the 5GHz.
Any chance for a firmware update ?? Yes,, I know it's a stablized model...
I noticed 2.4 is not working on short ranges when 5.8 is enabled. Long range - 2.4 works fine. 5.8 signal is short, but they both use 20Mhz channel width by default.
Looks like 5.8 signal overlaps 2.4 on short range. I changed channel width to 80MHz on 5.8 and kept 2.4 on 20MHz (because all my home applience is generic and it's using 2.4 and 20Mhz) I use 5.8 only for my laptops. Both 2.4 and 5.8 work fine.
I wanted to know i have the same problem but this problem is not on my community for my Net600 Western Digital and they won't help me could it be a Firmware problem?
and woudl the link for netgear work, , this part sounds kind of desperate but
I have already purchased and returned three modem/slash routers motorola and I purchased a TP LINK coming to give it one more try after a long talk with my tech support modem router specialist at comcast to see if it works ? non in my case the 2.4 GHZ works just much much slower then used to
Has anyone installed the new firmware release 1.0.76 whis has the fix for Security Advisory VU 582384? Due to the 2.4 Ghz issue I have been running old firmware for a long time. I want to know if this new release has any 2.4 Ghz issues before I install it. Many of my wireless devides do not support 5Ghz.
Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
RoadyBoy, my thoughts exactly! I hope the new firmware fixes the security issue as well as maintains function of the 2.4 Ghz band. But I am unwilling to invest the time and effort to find out. Dealing with the loss of 2.4 Ghz band a year ago was a huge time waster. I've been on firmware V1.0.4.28_1.1.64 ever since I found out that solved the problem. It has been unclear whether any firmware since then has restored function.
Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
