R7000 New Firmware 1.0.6.28 released

They always done it if FW has many fixes or changes, also in brief "what is changed or new" they has a warning that it is reccomended to do a hardware reset after an update. The problem in that not all read that or read not carefully.

---

Cat6aPlease wrote:

---

LeKeiser wrote:

---

---

Actually he is right. No other way to get rid of old configuration and garbage. 

But if you're so sure, why don't you explain why it's factually false?

---

 

 

I suggest you pose your question to the developers and ask why they don't make a reset mandatory for all customers at every upgrade.  I also suggest you ask that question to any software developer or developer of embedded systems, generally speaking.

---

well I'm asking you, because you said "that's factually false" so when using those terms, it means you know exactly what you're talking about. So please, since you do, share. Enlighten us.

Otherwise, please stop being so condecendent and do try a factory reset before and after a new firmware...

---

LeKeiser wrote:

---

 do try a factory reset before and after a new firmware...

---

The issues still continued to occur for people after performing a factory reset.  That was the point of all this.

---

Cat6aPlease wrote:

---

LeKeiser wrote:

---

 do try a factory reset before and after a new firmware...

---

 

 

The issues still continued to occur for people after performing a factory reset.  That was the point of all this.

---

I had the same problem as the others when I upgraded to the latest available firmware, but wanted to do it fast so skipped the factory reset after the upgrade. Ran into some troubles, was pissed off, wanted to throw the router to the wall. But decided to spare my wall, so I did a factory reset *before* and *after* the upgrade, and since then, my router has been running great and my wall feels better.

Just sayin'.

---

LeKeiser wrote:

---

upgrade, and since then, my router has been running great and my wall feels better.

---

That is another data point, however people on this message board should not apply their own anecdotal experience to everyone, much like my anecdotal experience of continued failure after factory reset does not apply to you.

---

Cat6aPlease wrote:

---

LeKeiser wrote:

---

upgrade, and since then, my router has been running great and my wall feels better.

---

That is another data point, however people on this message board should not apply their own anecdotal experience to everyone, much like my anecdotal experience of continued failure after factory reset does not apply to you.

---

This is a forum, people share their experience so that they can solve their problems with their router...

What do you expect to read on this forum but bad experiences? When people are satisfied, they don't come here. 

Or when they do, it's to help others. That's what I'm trying to do. I've had a good experience with this upgrade, so I share. 

What do you do yourself?

---

shamarin wrote:

They always done it if FW has many fixes or changes, also in brief "what is changed or new" they has a warning that it is reccomended to do a hardware reset after an update. The problem in that not all read that or read not carefully.

---

Here is the link for the LAST OFFICIAL F/W, http://kb.netgear.com/app/answers/detail/a_id/29273, where does it say to do that?

However for the latest Beta, https://community.netgear.com/t5/Nighthawk-WiFi-Routers/R7000-Beta-FW-1-0-5-60/m-p/1070857#M30302, it does say it, at the bottom. It does NOT say you must either, used 'kindly'.

There is NO hard and fast rule.

There might not be a rule, but it's been said here over and over that it was best to do a reset before and after.

People can do whatever they want after that...

---

LeKeiser wrote:

There might not be a rule, but it's been said here over and over that it was best to do a reset before and after.

People can do whatever they want after that...

---

Well I guess I look at it logically... I don't know the code but I made some assumptions.

First the R7000 is using NVRAM, that is it is like a phone or tablet. After powering off it retains the settings and 'private' data. Secondly, the h/w is a known factor, the size of NVRAM is known and never changes. There is an entry point the h/w jumps to to load on power on. Another for reset. Both are handled by the h/w or rudimentary OS running the h/w.

If the above are true, then the design of the Firmware should be straight forward. Once you come in via power up the router does what it needs to do, initialize as the s/w it needs too (what some call that 'drivers'), reads the store settings from NVRAM, clears out ALL 'live' data and then gets the 'live' data that it needs (making log entries, getting attached devices). If the first time you are doing customization and/or you change a setting, when you press 'apply' it writes that data to NVRAM. Probably at the top of memory (again, the s/w knows where this is as all R7000's have the same RAM size). This area is probably of fixed size with plenty of growth space for future needs. Below that would probably be the live data area and with a known size per F/W version. Only other 'buffer' is probably the area to load in the new flash for updating. I'm sure there is enough space to do all this as well as more than enough buffer space for future growth.

Only basic difference on a RESET or via the ERASE from GENIE would be that entry point would ERASE the stored settings in NVRAM and then branch to the power up.

If the above is true then the only 'problem' might be some later version mixing the order of the stored settings. Going back to an older version or loading saved settings from and older version over a new version could cause problems.

Lastly a possible NVRAM byte changed value over time (rare) and it wasn't really 'clearing'. Maybe the s/w could tell that and 'fix it' using a different area, but possibly only when run via reset?

Like I said, have not seen the code, but I don't think 'drivers' exist at all. It is ALL on firmware load to NVRAM.

It is also possible that some code in the firmware might not even be replaced during and upgrade? Doubt it, but a RESET should only clear the saved settings, not much else I'd think that was different from the power on?

RESET both before and after? I can understand the before to know you've cleared all settings. After seems redundant?

---

IrvSp wrote:

---

RESET both before and after? I can understand the before to know you've cleared all settings. After seems redundant?

---

And then there's also cases where 2 resets are required AFTER the upgrade.  How messed up is that.

I think what some people forget here is that when testing BETA versions, we're predominately looking at a new fimrware with the intent of providing feedback on bugs, errors or new features. We're not expected to be the troubleshooters as well...although I'm sure Netgear would appreciate the effort it if anyone feels inclinded to take that next step.

---

IrvSp wrote:

---

LeKeiser wrote:

There might not be a rule, but it's been said here over and over that it was best to do a reset before and after.

People can do whatever they want after that...

---

 

RESET both before and after? I can understand the before to know you've cleared all settings. After seems redundant?

---

Actually AFTER is the right way to go. This is because the hard reset doesn't just clear the settings, it sets defaults into the settings. The only thing that can know what defaults to put in place for a specific firmware is that firmware itself. When something like the new Arlo support was added in 1.0.6, it needs a new area of settings for the Arlo functionality. When people reverted back to 1.0.4 without doing a hard reset, they reported that the Arlo SSID still showed up, even though it doesn't support it. This means that the area where the settings were stored for Arlo conflicted with what 1.0.4 knows about and caused phantom issues. Running a hard reset after loading the older firmware makes sure that sensible values are in the right places for that firmware version.

---

rpoffen wrote:

---

IrvSp wrote:

---

LeKeiser wrote:

There might not be a rule, but it's been said here over and over that it was best to do a reset before and after.

People can do whatever they want after that...

---

 

RESET both before and after? I can understand the before to know you've cleared all settings. After seems redundant?

---

Actually AFTER is the right way to go. ...

 

When people reverted back to 1.0.4 without doing a hard reset, they reported that the Arlo SSID still showed up, even though it doesn't support it. This means that the area where the settings were stored for Arlo conflicted with what 1.0.4 knows about and caused phantom issues. Running a hard reset after loading the older firmware makes sure that sensible values are in the right places for that firmware version.

 

---

Either would do, clears out the OLD settings. Just to me, NOT knowing the code, before removes and problems for the new flash. I'm pretty sure the code that installs the new f/w doesn't clean out anything but just overwrites the code area and then basically reboots. That way whatever was in settings are used.

Again, not knowing the code I would 'assume' that the same specific addresses are use for ALL versions of the fw. Otherwise more problems would exist after installing if those settings addresses were to change. When new settings need to be added, they go to new reserved addresses.

Arlo problem could be very simple. That old recalled/deleted fw put the data in. Depending how the fw determines what SSID's to use it could very well be code that was written a long time ago and it had a planned expansion of more than 4 SSID's. It read a list at a specific location and if the data was NOT '0' it put out that SSID. That means the present 4 SSID are written to a buffer that the code expects to see the end of the list as a 0. As it reads it if non-zero, that SSID is started and used. After all, some, like me for instance, do NOT use the GUEST SSID's so only 2 come up on my router.

Again, without seeing the code this is ALL speculation and guessing how one would write the code.

All in all, I don't know 'why' any reset need be done, but if one could look at the code one could make a case with real data. Some code is probably available somewhere as 3rd parties have it. Looks like it is here, http://kb.netgear.com/app/answers/detail/a_id/2649/~/netgear-open-source-code-for-programmers-%28gpl%29 but the 1.0.4.30 file it seems can't be read?

There apparently is a just released new beta, 1.0.5.62, that specifically states it clears out the old Arlo settings possibly left over by a FW version that supported it.

I agree that the FW SHOULD do a better job when upgrading or downgrading to disable or clear out non-relevant settings, however this is exactly the problem, the FW was probably not taking into account different use models.

However, I reiterate that to be safe, unless overwhelming diffcult to do, the user would be safer to do a hard reset and reconfigure after changing FW to make sure it is more of a clean slate.

Will try it.

1.0.5.64 released today: https://kb.netgear.com/app/answers/detail/a_id/30695 .. http://www.downloads.netgear.com/files/GDC/R7000/R7000-V1.0.5.64_1.1.88.zip

Good news. Allready updated my router.

I have updated also. 

I have question because i have two R7000 and on one of them i have icon of program Netgear  Downloader Beta. Can You explain me this ?

I updated two and now shows on both the same that is means is ok : 

sorry and Regards 

Will I loose all my port forward settings with this update? 

Really nervous of updating this router as the past one killed the whole network.