Joined: 24 Oct 2008 Posts: 983 Location: Latin America
Posted: Tue Apr 28, 2020 15:40 Post subject: Poll: which build do you recommend for Broadcom?
We have seen a lot of buildings during the last couple of years. Some might have worked good for you, while others don't. In order to help the community I wonder whether we could compose a table like the following, with the most popular builds:
For general usage:
Code:
Broadcom devices with K2.4:
WRT54GL 14929std, WL-520GU 149292mini-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 gaming:
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], ...
And gathering this both for MIPS and ARM SoC's.
Your feedback is welcome, but rather than ellaborating why a particular build is good or not for a given device, please focus on which one you would recommend, and if you want to complement with a few words, that's OK.
Notes:
1)I think if your device is rather old and/or with limited resources (CPU, flash, RAM), it probably will work better with a not-so-recent build. On the contrary, if you have a recent and good device, it would be nice to upgrade to a good recent build and/or try the ones being developed.
2)Maybe different people could recommend different builds for the same device. No problem, add it next to the other, and let the people try and decide, and/or add a "[+]" or something, like counts, like votes.
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 Fri May 08, 2020 2:12; edited 1 time 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#
x64 OPNsense 20.7.6|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 45036: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250|OpenWRT 19.7.5: 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: 983 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 Lollipop
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.
This is a great thread. I am not sure why more people are not using it.[/url] _________________ [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: 8368 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: 8368 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 = r46239 (Apr 1st 20211) (i.e. dd-wrt.v24_mini_generic.bin ) ; it works fine for a general use router so far (I got a bit over 3 days of uptime currently) and I would imagine the other builds from r46239 are fine to but I never directly tested those.
I upgrade like usual from... 'Administration > Firmware Upgrade'.
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 before flashing new firmware (if you want to be extra cautious)...
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.
IMPORTANT NOTE: do not overclock 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! NOTE: 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).
NOTE: but I am not really saying anything all that new as overclocking in general increases risk. but in my case it was never a problem until somewhere between r45735 (Feb 11th 2021) and r46329 (Apr 1st 2021). _________________ Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r46239 Apr 1st 2021) ; new Panasonic capacitors Feb 11th 2020 | ASUS WL-520gU /w dd-wrt.v24_mini_generic (r46239 Apr 1st 2021) | Linksys WRT54GS v6 /w DD-WRT v24-12548_NEWD_micro | Belkin F5D7230-4 v1444 (bricked on Apr 6th 2021)
Last edited by ThaCrip on Fri Apr 09, 2021 18:30; edited 1 time in total