this is more correct but your version will work too
difference is the & symbol
& symbol creates separate process for the write command, so it will be done even if the telnet/ssh connection is lost... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
killing services in order to clear ram yes.. but this unit, has a plenty of ram...anyway..however its recommended to stop USB or ect..(i never do it)
flashing trough GUI, will stop few services in order to flash...CLI flash it not always safe, but works...there are few other ways to CLI flash or serial or TFTP so many of those... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Router: R7000
Firmware: DD-WRT v3.0
File: R52869
Kernel: Linux 4.4.302-st40
Previous: R52720
Reset: Before and After Upgrade via Web GUI
Mode: Gateway, AP, Router behind ISP Router
Status: Operational with Wireguard, uptime 2hrs
Can you please review if this is the correct commands for Netgear R7000.
Yes webflash is the correct file and write netgear-r7000-webflash.bin linux is correct and anything extra is overkill.
Never lost terminal, also never suddenly wanted to exit or log out. Stopped counting somewhere over 200 flashes.
If you are really concerned about it just rename to firmware.bin, and then wait for some automated dd-wrt magic.
Code:
mv netgear-r7000-webflash.bin firmware.bin
If you want to download directly to save the file as firmware.bin, use the lower case -o option or -output with curl.
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Mon Jun 05, 2023 20:04 Post subject:
Both the manual cli write process and webUI process have been patched to fix certain issues with upgrades. I have not experienced any disconnections over wired, but have not completely tested over wi-fi. The thing with using the ampersand (&) at the end of `write filename linux` is that you have no output to let you know when it is finished. Keep in mind, @frater's script is what contributed to certain things regarding patches to write, internal auto-upgrade, and webUI upgrade processes, if I am not mistaken. Plenty of enhancements over the years since 2009.
Joined: 16 Nov 2015 Posts: 6436 Location: UK, London, just across the river..
Posted: Mon Jun 05, 2023 20:33 Post subject:
Yep now you can see the picture...lots of different ways for flash procedure...and there is wiki too..
at the end of the day, all those will serve the purpose...
lots of other details, as the other GURU's explained...suggested...announced...too
Off the record, i had a couple flashes via SSh over WAN, that something went wrong and i lost connection with the unit...ever since i use &, in my case...it saved the day...
I still do have 3 units that i administer or flash over WAN ..
yes in the past flashing with & used to end the flash procedure with no report and you had to hit return to get the report..on the new builds, its fixed now..
Just to add if your device doesn't have enough free ram...CLI flash is not recommended..
you can always check while in cli mode with top command...even if you have a mounted USB and you have your file there, instead of /tmp directory you still must to have enough free ram in order to successfully flash.. _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
nohup write netgear-r7000-webflash.bin linux & tail -f nohup.out
Would make life a little more easier. Regarding flashing over WAN, that is probably something to consider, since there is always a possibility that WAN (possibly) does get sent down during the write process. Only one way to find out in current releases <wink> _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Sorry for hijacking the firmware update log for my off-topic question about CLI flash methodology. I didn't expect there would be that many answers. If you think the CLI flash method should be moved to a separate post, please let me know.
For now still a question
blkt wrote:
If you are really concerned about it just rename to firmware.bin, and then wait for some automated dd-wrt magic.
Code:
mv netgear-r7000-webflash.bin firmware.bin
I assume that when DD-WRT sees a file /tmp/firmware.bin, it will trigger itself a flash? If so, when would that occur? (within a minute?) Would there be any progression output in the SSH terminal?
Other members didn't discuss too much about the rename to firmware.bin. Is it b/c this practice is less popular or has some inconveniences?
Last edited by Tectonic Plates on Tue Jun 06, 2023 2:57; edited 1 time in total
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Mon Jun 05, 2023 22:41 Post subject:
DD-WRT checks for presence of "firmware.bin" in /tmp and automatically runs a firmware update process for you, and you have to `tail -f /var/log/messages` as alluded to already. _________________ "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
People use the convenience of the automatic process all the time. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Joined: 26 Mar 2013 Posts: 1856 Location: Hung Hom, Hong Kong
Posted: Tue Jun 06, 2023 4:38 Post subject:
kernel-panic69 wrote:
DD-WRT checks for presence of "firmware.bin" in /tmp and automatically runs a firmware update process for you, and you have to `tail -f /var/log/messages` as alluded to already.
When would it happen? During startup? Anytime? _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
It (constantly) checks for the presence of the file every minute, 24/7 essentially. Why are we remediating on a years and years old feature of this firmware?
Joined: 26 Mar 2013 Posts: 1856 Location: Hung Hom, Hong Kong
Posted: Tue Jun 06, 2023 8:30 Post subject:
dale_gribble39 wrote:
It (constantly) checks for the presence of the file every minute, 24/7 essentially. Why are we remediating on a years and years old feature of this firmware?
Isn't it a bit dangerous? Imagine someone doing 'ln -s /dev/random /tmp/firmware.bin'!!! This hidden, automatic process MUST be managed. _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!