Joined: 24 Oct 2008 Posts: 1079 Location: Latin America
Posted: Tue Apr 28, 2020 15:40 Post subject: Poll: which build do you recommend for Broadcom?
We've seen a lot of buildings during the last couple of years. Some might have worked good for your needs and your router(s), while others may not. So, in order to help the community I wonder whether we could compose a table like the following, i.e. with the most popular builds for different hardware and scenarios.
Notes:
1)If your device is rather old and/or have limited resources (basically corerev of your SOC and ammount of flash and RAM), and you are not so-concerned about security and patches, IMHO it probably will have a better performance/stability with a not-so-recent build. On the contrary, if you have a recent and powerful device, and looking for feeling safer, I would recommend to upgrade to a good recent build or try the newest ones being developed, and share your findings for keeping this going.
2)Maybe different people would recommend different builds for the same device. No problem, add it next to the other, and let the people test and decide, or you can add a "[+]" or something, like counts, like votes.
So I will start recommending what's on the Notes 3 and 4 of the Peacock thread (14929, 15962, 17990, 27560, 27858, etc.)
Now, the table I'm thinking about:
For general usage:
Code:
Broadcom devices with K2.4:
WRT54GL 14929std, WL-520GU 14929mini-usb-ftp, F5D7231-4P 15962mini-usb-ftp, [your router and build recommendation here], ...
Broadcom devices with K2.6:
F7D3301/F7D7301/F7D3302/F7D7302 15962big, [your router and build recommendation here], ...
Broadcom devices with K3.x:
[your router and build recommendation here], ...
Broadcom devices with K4.x:
[your router and build recommendation here], ...
For gtaming
Code:
Broadcom devices with K2.4:
[your router and build recommendation here], ...
Broadcom devices with K2.6:
[your router and build recommendation here], ...
Broadcom devices with K3.x:
[your router and build recommendation here], ...
Broadcom devices with K4.x:
[your router and build recommendation here], ...
For VPN:
Code:
Broadcom devices with K2.4:
[your router and build recommendation here], ...
Broadcom devices with K2.6:
[your router and build recommendation here], ...
Broadcom devices with K3.x:
[your router and build recommendation here], ...
Broadcom devices with K4.x:
[your router and build recommendation here], ...
Other scenarios:
Code:
Broadcom devices with K2.4:
[your router and build recommendation here], ...
Broadcom devices with K2.6:
E1000v2 16785voip-small, [your router and build recommendation here], ...
Broadcom devices with K3.x:
[your router and build recommendation here], ...
Broadcom devices with K4.x:
[your router and build recommendation here], ...
So maybe we could gather a list like this both for MIPS and ARM SOCs.
Your feedback is welcome, and please rather than ellaborating too much on why a particular build is good or not, please focus on which one you would recommend for a device/family and scenario(s), and if you want to reinforce this with a few words, that's OK.
Let's see how this goes... _________________ If you want support, please read first the announcements and forum rules.
Si usted desea ayuda, por favor lea primero los anuncios y las reglas del foro.
Last edited by feliciano on Sat Apr 17, 2021 2:46; edited 5 times in total
You left out Broadcom ARM that runs k4.4, and btw, as of today's 43012 build (which has broken BCM ARM wifi), BCM MIPS is also on k4.4 (at least until BS gets 4.9 working for it "soon" ). r43007 alpha is working great on my WNDR4500v2 (MIPS NAND).
All I can say is not to use any build older than 41664, to have SFE NAT (for k3.2+ builds), KRACK (k24+), PBR+SFE, CAKE / FQ_CODEL_FAST, and GTK Rekey wireless timer fixes. For Wireguard, one should use at least 42872.
The latest builds are generally recommended, after one researches the build threads to avoid bad ones. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Last edited by jwh7 on Wed Jul 22, 2020 2:27; edited 1 time in total
Joined: 24 Oct 2008 Posts: 1079 Location: Latin America
Posted: Tue Apr 28, 2020 21:27 Post subject:
Notes taken.
So I think it would be good to have separate lists for MIPSr1, MIPSr2, and ARM, for the major branches of kernels we have worked on, or are working with. _________________ If you want support, please read first the announcements and forum rules.
Si usted desea ayuda, por favor lea primero los anuncios y las reglas del foro.
I do think there needs to be something like this. So well done for having the idea of doing it or - for you want to start collecting data already, yes? - for actually doing about.
Router: Asus RT-AC66U
Build I find best: DD-WRT v3.0-r42278 giga (02/05/20)
Running VPN software (e.g. OpenVPN, Wireguard) directly on the router? No
Operating systems on devices that use the router: Linux, Android and Windows) _________________ My router: Asus RT-AC66U
Operating systems on devices that I use with that router: GNU-Linux; Windows 10; Android 13
You left out Broadcom ARM that runs k4.4, and btw, and of today's 43012 build (which has broken BCM ARM wifi), BCM MIPS is also on k4.4 (at least until BS gets 4.9 working for it "soon" ). r43007 alpha is working great on my WNDR4500v2 (MIPS NAND).
All I can say is not to use any build older than 41664, to have SFE NAT (for k3.2+ builds), KRACK (k24+), PBR+SFE, CAKE / FQ_CODEL_FAST, and GTK Rekey wireless timer fixes. For Wireguard, one should use at least 42872.
The latest builds are generally recommended, after one researches the build threads to avoid bad ones.
I need a recommended build for wrt54g v.4 router thats protected from all the above. Or a suggestion for a new router, thats well supported. I grabbed the wrt54gv4 off ebay thinking it would be well supported but I'm 99% sure I just bricked two of them trying to put something other than 14929 on it. i.e. I tried to put 43217 on it. The only thing I need this router for is a wifi access point, to extend my wifi (i.e. repeater bridge), thats as secure as possible using standard stuff. I need like 5 of them, so the older, cheaper, more supported the better.
Is there even any builds that are supposed to work on this router that have these bugs/CVEs patched ?
note: I do not care about fixing the bricked routers, they were $10 a pop.
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Sun May 24, 2020 1:45 Post subject:
This thread is not to ask these questions. This thread is to give recommendations based on experiences, etc.
But since I'm feeling nice, I will say that you need 43192 or later for your WRT54* series device (look in the build threads like you're s'posed to do). _________________ "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
This is a great thread. I am not sure why more people are not using it. _________________ [MAIN GATEWAY] Netgear R7000 – DD-WRT v3.0-r43324 std (06/02/20)
[AP1-wired] Asus RT-AC68U - D-WRT v3.0-r44467 std (09/24/20)
[AP2-wired] Asus RT-AC68R – D-WRT v3.0-r44467 std (09/24/20)
(switch) 1 AP WRT160N v3 - DD-WRT v3.0-r30731 mini (10/06/16)
==
YOU CAN'T STOP THE COLETRAIN BABY!
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Fri Aug 07, 2020 2:06 Post subject:
All K2.6 builds after 43136 are broken. I received another E4200v1 recently that had been flashed with 43192 and was bricked, so I back-tracked from that build to 43136, checked all the way through 44086 and all have the same problem and will not boot.
EDIT: Should be fixed in releases after 44092, along with pptpd.
I'm running this build on D-Link DIR 890 (similar to R8000) and it don't let me down. No reboots, no staggering for weeks. In later builds there are visible changes in UI and some functions may not start by itself. This build has everything, maybe a little outdated versions. The only thing - processor throttling doesn't seem to work, can't set lower than 1Ghz. It has ARM 1Ghz processor and 3 bands (2x5G, 1x2G).
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Tue Mar 16, 2021 17:14 Post subject:
For K2.4 (WRT54* series and clones): 45955+ due to kernel and webUI patches.
For K2.6 45955+ due to kernel and webUI patches.
For K3.x/K4.x 45955+ due to webUI patches.
Linksys WRT54GS v1.1 = r46640 (May 13th 2021) (i.e. dd-wrt.v24_mini_generic.bin ) ; it works fine for a general use router so far (12 days 5 hrs uptime currently (as of May 30th 2021)). I upgraded from my previous build from about a month ago due to Fragattack fixes included in this May 13th 2021 build.
I upgrade like usual from... 'Administration > Firmware Upgrade'.
here is some general advice when flashing firmware. if someone wants to play it extra safe when upgrading firmware on these WRT54* variations here is a pretty good guideline to follow (which should minimize risk)...
1)Reset router to defaults (i.e. hold reset button for 30 seconds) and once router is responding again...
2)Unplug router for 1 minute and plug it back in.
3)Go to routers configuration page (i.e. 192.168.1.1) and proceed to flash firmware under the 'Administration > Firmware Upgrade' section in DD-WRT. IMPORTANT NOTE: as soon as you start firmware flashing process make sure to wait a FULL 5 minutes as this should keep the risk of bricking ones router at a bare minimum.
4)Reset router to defaults (another 30 second reset using reset button) and reconfigure to your liking.
NOTE: avoid overclocking the WRT54GS v1.1 router (and probably the general WRT54* series and clones to) as, in short, while r45735 (Feb 11th 2021) was fine running at 240Mhz on my WRT54GS v1.1, r46239 (Apr 1st 2021) does not like it as you will have problems (routers configuration page is not accessible/no internet etc) if you try it! ; but what I particularly did to bring mine back to life when I was having problems due to the overclock was... unplug router, wait a little, hold reset button, and while still holding reset button plug the routers power back in and count 30 seconds, release reset button. you should now have a working WRT54GS v1.1 router once again (at least in my case this worked).
p.s. with all of that said, while the steps I provided above are optimal (i.e. safer) for going about the firmware upgrade process, I just typically use my router like usual and when I need to upgrade with new firmware I go to "Administration > Firmware Upgrade" and then upgrade (leaving the "After flashing, reset to: Don't reset" section as is), wait 5 minutes (although the router seems to become responsive in another browser tab around 3 minutes), then just hold reset button on back of router for 30 seconds (or as a potential/quicker alternative to that last reset button option, which may not be as thorough but is probably good enough... through telnet issue, 'nvram erase && reboot' (without the ')) and then reconfigure the router to my liking. _________________ Primary Router: Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r46640 May 13th 2021) ; new Panasonic capacitors Feb 11th 2020 | Backup Router: Linksys WRT54GS v6 /w dd-wrt.v24_micro_generic (r46640 May 13th 2021)
Last edited by ThaCrip on Sun May 30, 2021 11:40; edited 5 times in total
General use:
Broadcom devices with K3.x: DD-WRT v3.0-r41321 mega (10/14/19) [Linksys E1200v2]
I've tried several newer builds up to 44538 and every one of them causes the router to bog down and need a reboot after a few weeks of uptime. It acts as though the memory gets full or something. With 41321 it just keeps running and I can just forget about it. I plan to try 45955 or newer as recommended by kernel-panic69 though, when I have a few spare hours.
I've attempted a few newer builds up to 44538, and they all cause the router to slow down and need a reboot after a few weeks of use. It's as if the memory is getting full or something.