The command I know of is nvram erase. That command was changed a while back, if memory serves. I don't know why I didn't pick up on that in the ticket: https://svn.dd-wrt.com/ticket/6695 ... also, I don't recall any status return issuing either command via shell, anyway.
Thanks for the fast support at this time. I'll give telnet a go in the next build.
Any thoughts about what changed the CPU load even though it doesn't look to effect CPU temperatures?
Hard reset I feel is a bad idea in most cases, but others may need it at some point.
Update: Almost 3-days of uptime. This release is working very well for me. Performance and reliability are excellent so far in my environment. None of my work-from-home family members have bitched at me either.
Upgraded to 43471 3 days ago after running 43306 for the last few weeks without issues. All upgrades were done via GUI over Safari. General browsing feels snappier with this release, and wireguard client upload performance is better too.
Issues: The usual red http authorization/authentication errors in syslog which I've been seeing for at least a year now. Also,I was having lots of disconnects and DHCP chatter in syslog from some of my IOT devices and one of my chromecast audio devices. Giving them static leases in DNSMASQ and going back to 5ghz channel 100 (a DFS channel that the chromecasts do not like) have settled things down.
Wireguard client: Using Mullvad client config following parts of Hellakenut's "idiots guide for commercial clients" and egc's updated guide to eliminate the startup script. I'm getting about 10% improved Wireguard upload speed with this release. I haven't dug into why - I suppose it could have been an upgrade with the Wireguard server I'm attached to. I've noticed some bufferbloat on the upload side however, so I'll keep playing around with it.
Kernel: Linux 4.9.227 #1858 SMP Fri Jun 19 03:18:32 +03 2020 armv7l
Sorry kernel just a quick question in some of the builds the GUI design changes, but returns with a soft reboot,or a URL refresh. Is this more of a web browser issue?
-->
According to Kong the commmand to go for nowadays is nvram erase
No luck in finding it currently, but if my memory serves right a few months after this post there were additional changes, further limiting the use of "erase nvram"
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Fri Jun 26, 2020 3:57 Post subject:
The nvram erase without a reboot won't work. Because of the static nvram variables stored in the filesystem. All it takes is a "save" and there ya go. At least that is my best understanding of it
P.S. I have MLandi's old 3200 running 19.07.3 OpenWRT and handling the office at present. I had to figure out the right voodoo to get the 2.4 radio useable for my mobile phone to connect to. Most everything is wired, and I'm not using either 5GHz radio. _________________ "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
Wired I never have issues, and 5, and 2.4GHz is fine to. This is not a bad router. Just have to really play with radio settings sometime to make all devices happy, and the Linksys
Router Model Linksys WRT3200ACM
Firmware Version DD-WRT v3.0-r41380 std (10/24/19)
Kernel Version Linux 4.9.197 #1368 SMP Thu Oct 24 07:06:09 CEST 2019 armv7l
OpenVPN Client (NordVPN Server) OK
5GHz 40MHz Mixed WPA2 AES OK
2.4GHz 20MHz Mixed WPA2 AES OK
Load Average 0.07, 0.06, 0.01 4%
Temperatures CPU 54.1 °C / WL0 30.9 °C / WL1 31.9 °C
Clients 2 PS3s, 2 PS4s, 2 Firesticks, 1 Firebox, 3 Android phones, 2 laptops, 1 desktop.
Update: Over 32 days of uptime on both devices. This release is working very well for me. Performance and reliability are excellent so far in my environment. None of my work-from-home family members have bitched at me either.
Upgraded to 43471 after running 43306 for the last few weeks without issues. All upgrades were done via GUI over Safari. General browsing feels snappier with this release, and wireguard client upload performance is better too.
Issues: IOT devices (chromecast audio, eufy homebase2, axis camera) can be finicky with wifi. Sometimes, it simply a matter of repositioning them an inch and their connection problem is solved. Sometimes, they repeatedly try to connect to a weaker 5ghz channel and you have to force them onto the stronger 2.4ghz channel. Once in a while, when me and my Macbook Pro laptop roam to another room in the house, I'll try to ping an IOT device that I know is on another device and radio, and it takes a few minutes for the ping to work.
Wireguard client: Using Mullvad client config following parts of Hellakenut's "idiots guide for commercial clients" and egc's updated guide to eliminate the startup script. I'm getting about 10% improved Wireguard upload speed with this release..
Kernel: Linux 4.9.227 #1858 SMP Fri Jun 19 03:18:32 +03 2020 armv7l
