Posted: Wed Jun 24, 2020 19:52 Post subject: How often do you flash DD-WRT?
I'm just curious how often everyone flashes a new build of DD-WRT on there router.
Personally, I think every couple months is good. Overall, it tends to allow me to get any new security fixes and features while I'm not over flashing the chip and I can usually avoid the rare bugs that occasionally pop up.
Joined: 16 Nov 2015 Posts: 3707 Location: UK, London, just across the river..
Posted: Wed Jun 24, 2020 20:49 Post subject:
hmm, it depends if i follow svn line to be aware of the progress, and i know how to unbrick my units...yep i do it quite often...i don't care about warned out flash chip ,as they are good enough to last a long time... _________________ Atheros
TP-Link WR740Nv1 ------DD-WRT 44085 BS AP,NAT
TP-Link WR740Nv4 ------DD-WRT 43028 BS WAP/Switch
TP-Link WR1043NDv2 ----DD-WRT 44085 BS AP,NAT,AP Isolation,Firewall,Local DNS,Forced DNS,DoT,VPN
TP-Link WR1043NDv2 ----DD-WRT 44048 BS AP,NAT,AD Block,Firewall,Local DNS,Forced DNS,DoT,VPN
TP-Link WR1043NDv2 ----Gargoyle OS 1.12.0 AP,NAT,QoS,Quotas
Netgear R7800 -------DD-WRT 44085 BS AP,NAT,AD-Block,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT
Netgear R7000 -------DD-WRT 44085 BS AP,Wi-Fi OFF,NAT,AD-Block,Firewall,Local DNS,Forced DNS,DoT,VPN
Stubby for DNS over TLS I DNSCrypt v2 by mac913
Joined: 16 Mar 2019 Posts: 126 Location: Szczecin, Poland EU
Posted: Fri Jun 26, 2020 17:43 Post subject:
Generally I'm flash version to version. Sometimes I have soft brick on my device. I must back to last stable version. Generally I'm update my device as soon as is possible. Then I can test the newest builds. DD-WRT is advantageous project for me.
Joined: 04 Aug 2018 Posts: 869 Location: Appalachian mountains, USA
Posted: Fri Jun 26, 2020 21:38 Post subject:
Fascinating range of responses developing here.
I upgrade only every six months to a year, because I have to upgrade five routers, three of which have to be upgraded and tested remotely - they are not nearby - without being offline for any extended period. It's all kind of a high-stakes game, and it eats a lot of my time, especially as I feel I have to be fairly thorough with testing. It's the time commitment that keeps me from upgrading more often. _________________ Five Linksys WRT1900ACSv2's on 42926, 43904, 44048:
VLANs, multiple VAPs, NAS, QoS, client-mode travel router, OpenVPN client/PBR (AirVPN), wireguard/PBR (AzireVPN), two DNSCrypt servers (incl Quad9) routed through OpenVPN.
I usually try to understand what is happening in trac / svn.dd-wrt.com.
If I'm bored and driver, kernel or wireguard commits were added --> flash
If my release is older than a month --> flash
Nowadays I registered here in the forum to also add my reports, but am doing this since I bought the WRT54GL in 2009.
Never had a problem with defective flash, but VERY often managed to brick everything due to not understanding / reading / being patient enough
I think it varies from case to case.
For my personal D-Link repeater bridge, I upgrade the firmware everytime there's a new build, because I'm the only user. I can afford to get it soft-bricked without affecting others, and it's fairly easy to recover (compared with my previous Linksys router), and even if I'm unable to recover (or lazy to recover) then I still have internet connection from the main router. I don't think flash wear-out is a big concern because most flash chips have the life-time in the range of 100,000 erase. I also think that upgrading frequently will help the developer(s) iron out any issue in the early stage and speed up the development process: pushing out small changes and confirm before moving on will be more efficient than adding a lot of codes in one go then unable to pinpoint the root cause if there's issue.
But for the other router used at work, I am afraid of upgrading/try not to upgrade, because if something went wrong then many people would be affected. That kind of environment prefers stability over speed/functionality.