Posted: Mon Jul 10, 2017 1:45 Post subject: How do you install a "stable" release?
I'm a bit confused about the firmware downloads from the FTP server. I recently downloaded and installed a version of DD-WRT onto my TP-Link C7 Archer with a build date of 2015. I imagine there are at least some security patches since then but when I look up new firmware builds for my router I only find them in the "betas" section. Looking in the "stable" section on the server only shows very old images from 2008. Is the stable folder even used anymore, and if so how should I go about patching my device?
I have not upgraded to the latest 2, I am still on 31899 on most of my routers because of a problem with the 5GHz network on the Archer C7 v2 in particular. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
Posted: Mon Jul 10, 2017 4:27 Post subject: Stable release?
The concept of state release has no well-defined meaning in DDWRT. A given release may be anything from rock solid to too large to even download, depending on the target hardware. Some areas, such as WiFi and VLANs, are subject to the underlying hardware of each target device. Other area, like to GUI and VPN, oscillate based on updates to underlying base packages outside of the DDWRT developers' control.
In the past there have be proposals to systematically measure the most commonly used release/hardware combinations, monitor mean uptimes as a proxy for stablity, or curate lists of known working release, hardware, and used feature sets. None have come to pass due to the effort involved, privacy issues, and the broad spectrum of application of DDWRT across hardware types, feature sets, etc.
For the past 4 years it has been my practice to determine frequent contributors to these forums who operate the same hardware I use and follow them at a safe distance (six months to a year lag) on releases they find stable.
While I value DDWRT for the broad and generally consistent feature set across a wide variety of hardware platforms of differing vintages, I realize it is a volunteer effort with resulting trade-offs.
