Updated via webif. No 'nvram erase' this time, last one was in July 2018 (r36325).
Well you are in the 1% everyone else would have been pulling hairs out with the gremlins banging on the door Honestly no idea how that's even possible considering the insane amount of nvram changes and general firmware changes since r36325 which build doesn't exist on servers.
Well, I never planned to set any records I thought it's an interesting data point that resetting nvram isn't something I've had to do. This little Netgear R7000 / DD-WRT is a workhorse. I keep it on a UPS so, generally, it receives steady power. Having said that, it's high time I did a reset to at least clear out any wayward bits. _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
Didn't know it was recommended to do an nvram erase regularly, thought that was only needed if you run into issues.
Just to add to the data set: I've been running dd-wrt on my R7000 since 2016 (Kong builds, moved to BS builds after Kong stopped) and don't think I've ever done an nvram erase.
I suppose I should backup the config before doing an nvram erase, and re-import the config afterwards? Nothing else to worry about?
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon May 23, 2022 9:12 Post subject:
hurleyp wrote:
Well, I never planned to set any records I thought it's an interesting data point that resetting nvram isn't something I've had to do. This little Netgear R7000 / DD-WRT is a workhorse. I keep it on a UPS so, generally, it receives steady power. Having said that, it's high time I did a reset to at least clear out any wayward bits.
I appreciate the data and I would let it ride until you actually have no other option because of some issue that wont go away.
While a single device's data on non resets from really old builds vs incremental fw upgrades to newer builds, isn't sufficient to build any representative long term analyses of the possible gremlin states. It is still interesting in any case.
A proper experiment we would need to test groups of different routers per brand/model to have usable data on the other end after at least 100 consecutive flashes or staggered builds until reaching the very latest build and tests to confirm the given test setups work. The test setups would need to differ also, from basic to advanced setups.
But this is academic. who cares anyway of the long term lack of resets effects of operational condition of a home router. Bigger issues in the world and none cares about them either.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue May 24, 2022 8:11 Post subject:
ludovic wrote:
I suppose I should backup the config before doing an nvram erase, and re-import the config afterwards?
If you want a human readable config backup for later consultation do this via terminal
nvram show > /tmp/my-backup-whatever-build-date.txt then grab that file to your desktop or wherever you prefer.
Ive added this tip to the routers built in help file and is available on the latest dd-wrt public builds in the backup section of the router under more...
But restoring an old config to a new build, is generally not advisable, even though the process should in theory not restore incompatible settings, there is a risk of gremlins getting you, while re-configuring from scratch after upgrade and nvram reset, will ensure 100% clean state.
If you want a human readable config backup for later consultation do this via terminal
nvram show > /tmp/my-backup-whatever-build-date.txt then grab that file to your desktop or wherever you prefer.
Ive added this tip to the routers built in help file and is available on the latest dd-wrt public builds in the backup section of the router under more...
But restoring an old config to a new build, is generally not advisable, even though the process should in theory not restore incompatible settings, there is a risk of gremlins getting you, while re-configuring from scratch after upgrade and nvram reset, will ensure 100% clean state.
At the time of writing this there is already a newer build - r48954 with a ton of help file fixes and other firmware fixes and updates.
OK, thanks a lot!
Would be nice if there was a way to see only the settings that were user-modified (like how Firefox does it nowadays with about:config), but that's not a small feature to implement.
Honestly no idea how that's even possible considering the insane amount of nvram changes and general firmware changes since r36325
I thought it's an interesting data point that resetting nvram isn't something I've had to do. This little Netgear R7000 / DD-WRT is a workhorse. I keep it on a UPS so, generally, it receives steady power. Having said that, it's high time I did a reset to at least clear out any wayward bits. 
Thanks!