For someone that stays pretty current and often flashes the latest build without performing a "nvram erase && reboot" and configuration, how often is a erase and configuration recommended? Does DD-WRT generally transition a configuration gracefully when flashing over a recent version, or should a user erase and reconfigure after a certain period of time or a certain number of flashes? Generally, I won't erase and configure unless I have waited a long time between flashes, I am having a problem, or I plan to post about a problem and am asking for help.
I'd love to know the answer to this question as this is exactly what I do as well, try to stay up-to-date as possible and rarely erase.
Status: Up and running for 3 days, basic setup as Gateway, static leases, port forwarding, DDNS, WOL 2,4GHz, VAP for IoT, 5Ghz (Vanilla Firmware, Disabled Airtime fairness),
Joined: 16 Mar 2019 Posts: 353 Location: Szczecin, Poland EU
Posted: Sun Jun 26, 2022 10:40 Post subject: New Build - 06/23/2022 - r49326
Router/Version: TP-Link TL-WDR3600 v1.5
File/Kernel: Linux 3.10.108-d11 #111088 Thu Jun 23 05:14:47 +07 2022 mips
Reset: No, only auto reboot after GUI flash and full reboot by button on case and replug power supply
Mode: Internet gateway, WIFI 5GHz AP, dnsmasq server, iptables firewall
Issues: rather weak WAN performance, currently ~300 mbit/s, sometimes download speed value is better
Status: Working
Uptime: -> 64h
Download speed is currently ~300 mbit/s, sometimes speed is higher. I'm attach syslog.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sun Jun 26, 2022 11:45 Post subject:
LizardWizard wrote:
dplettner wrote:
For someone that stays pretty current and often flashes the latest build without performing a "nvram erase && reboot" and configuration, how often is a erase and configuration recommended? Does DD-WRT generally transition a configuration gracefully when flashing over a recent version, or should a user erase and reconfigure after a certain period of time or a certain number of flashes? Generally, I won't erase and configure unless I have waited a long time between flashes, I am having a problem, or I plan to post about a problem and am asking for help.
I'd love to know the answer to this question as this is exactly what I do as well, try to stay up-to-date as possible and rarely erase.
+ 1 for egc's reply of once yearly, rule of thumb.
Personally, like built in help pages say and I pretty much follow that;
- if changing a bunch of settings causes weirdness and cant pin it down to a specific setting.
- If suddenly after an upgrade there is some observed gremlin behavior.
- Once a year, if neither reset as above was done previously within that time period.
However having said that this year already reset 4 times, I do flash test builds anywhere from 2 to 4 times or more a day, depending on level of development.
I do test things thoroughly beyond my use case and while most people dont report weirdness's and notice quite a few issues some critical. there is no need to always report those on build threads, unless corroboration is needed.
Sometimes electrons decide that they want to go next door for a visit or charge is attenuated for some reason, cant measure it always, but it explains the odd gremlins,
I've noticed and seen happen SEU events twice here at my current geographical coordinates, never before see it happen (settings deciding to enable or disable themselves on unrelated pages I dont usually need), perhaps because my current address is not far from a military air base, who knows what else is stored around here underground, no Geiger counter to confirm, but specific radiation does affect these consumer electronics which aren't adequately shielded for such or for cosmic rays, it happens. _________________ Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers DD-WRT Inspired themes for the phpBB Forum DD-WRT Inspired themes for the SVN Trac & FTP site Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Sun Jun 26, 2022 11:51 Post subject:
There are specific cases where you have to do a hard reset or reset to defaults; otherwise, you just have backwards compatibility to older builds with older var names and such. For example, if the variable value is already set and not correct on boot, it will cause issues and the only way to fix that is to reset. Case(s) in point: When swconfig was added to Broadcom builds as well as the whole fun of fixing ethernet port orders in the webUI and when wifi webUI access setting was not only fixed in Broadcom, but added across the board. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Posted: Mon Jun 27, 2022 20:08 Post subject: Re: Build eval MAC Address Clone no set
neosimago wrote:
Linksys EA8500 ...main gateway
Tried to clone the WAN MAC but it won't set.
Cosmetic issue on Status...
Never had a bit of problem with Clone WAN MAC on the EA8500.
been doing it for many years ever since I pulled oldass WRT54GSv2 from my main.
My ISP holds static DHCP IP for me... that's why I use Clone WAN MAC.
Also works fine on the WNDR3700v4 or E2500 whatever I might throw in as main
AND NO, ain't never seen such cosmetic nonsense
---
EDIT--NOTE:
iffin you ever use a nvrambackup you will ALWAYS have to THEN set any 'Clone WAN MAC'
That kinda stuff don't carry over ...and for good reason
Thanks for all the great answers to my question about how often to restore defaults and reenter a configuration. In hindsight, I wish I had started a new thread rather than asking in a build thread.
Upgraded from an ancient 30082 to 49326 with a full reset.
Only issue I faced was a lot of messages of "ath10k_pci 0000:08:00.0: consec fail!!" in the kernel log which went away when I switched the 5ghz firmware to "vanilla" from the default "dd-wrt"
I have spotted "DDR Activity - HIGH" once or twice in the log but doesn't seem to affect operation.