R7000 2.4ghz not working but 5ghz is fine

---

h_smith wrote:

I mentioned that months ago but it did not apparently deserve a response. To suggest that I have to re-enter all of my settings each time I upgrade the software is really unacceptable.

---

Well I suspect there is usually a reasonable reason for needing to do this. Don't forget the flash contains the OS, GUI, and router programming. In a perfect world the OS and GUI would not have any effect on the programming of the router. Therefore in some instances it is best to re-enter all settings after resetting the router after updating. Only NG would know when AND why, but lately I've noticed they have been 'suggesting' the reset/re-enter 'request'. Wish they said why?

Don't forget, s/w will do what it is directed to do for all users the same way. Of course no two routers are probably using the same exact set of settings, so issues could be caused by settings themselves or combination of them.

Two other things to consider besides most of the reports here are of errors/problems and most likely are a very small percentage of users, a majority of whom have no problems at all.

1. There could have been some faulty d/l's, no MD5 supplied to check the contents of the flash d/l, which could be contributing to the problem.
2. Not all routers might be the same. Although there are no version numbers associated with the h/w, it appears the routers are built by different vendors and more than likely with different component suppliers. Because of this some components might fail under some different settings, but I'd suspect this would not be the case alone. However we all have different line voltages and stability. Some could experience problems due to this as well.

Base settings can cause problems too. I have a neighbor that had a problem with his Laptop wireless adapter when it was upgraded from W7 to W10. While it had no problem connecting to the router under W7 it could not under W10. Hmm, why would that be, other devices had no problems connecting to the router, why this particular laptop? It was a Toshiba and they really didn't have a W10 driver but the h/w manufacturer did so I got that. Did NOT fix the problem? We purchased a NG USB Wireless adapter. Disabled the internal one and fired up the NG USB and installed the latest W10 driver. STILL could not connect. Discovered the problem, his router was set to "WPA-PSK [TKIP] + WPA2-PSK [AES]" for security. Why was it set to that? Because his ISP said to do that (it is the one to use if you have older equipment and works for most people). Just changed it to "WPA2-PSK [AES]" and both the NG and internal Toshiba devices worked. A simple security change. Just goes to show how a simple setting can make a difference between connecting and not.

Me, when I update I do nothing first and just TRY it. Have a problem, RESET/RE-ENTER is the way to go.

"RESET/RE-ENTER is the way to go"

 @IrvSp - Stop apoligizing for these guys. That may have been the case in the past, like storing data on cardboard with holes punched in. Technology and user-friendlyness evolve.

It is not rocket science to design a coherent settings file format - especially after being in the router business for decades.

How difficult is it to stick user configuration like port settings etc into a structured XML file? Reading such a file is no different than reading user input from the web form.

In fact, just for manufacturer testing they should have tools to reliably, consistently and repeatedly read settings.

You could probably create an industry standard for tedious to enter settings most of us here care about (ip reservation, port mapping etc).

I enter the same stuff into every router - and guess why? Because, without going into details, the 'internet' doesn't talk to a specific router but is based on standard protocols.

Not only that. Expecting users to re-enter a working configuration manually across several screens is error prone.

-------------------

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?

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%.

---

fishbone wrote:

"RESET/RE-ENTER is the way to go

 

-------------------

 

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?

 

 

---

fishbone, sure it is easy to do. Doesn't mean it was done that way. The source code IS available if you want to dig into it. You can get it here at http://kb.netgear.com/app/answers/detail/a_id/2649/~/netgear-open-source-code-for-programmers-(gpl)?cid=wmt_netgear_organic

and search for R7000 and pick the version.

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.