Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.2 and newer 2. 'KRACK' vulnerability fixes were completed in r33678 for Broadcom, including k26 (33655) & k24 (33656); use 33772 or later.
3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issues below).
4. PBR/UDP with SFE working again since r40513 (see 6729)
5. CAKE scheduler changes "completed" with r41057 (see 5796) & FQ_CODEL_FAST with r41027 (reset first!)
6. Reset button was broken in 40571; fixed in build 40750.
Issues, observations, and/or workarounds reported: 1.Trendnet 81*DRU models are missing factory-to-flash 2.DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:6246 3.WDS does not work on Broadcom ARM devices (only MIPS<->MIPS) 4.K2.6 builds are broken since 38253(?) (GUI issues):6538 5.VAPs not working at boot; workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
This appears fixed (only for unbridged VAPs?) with r40564:40566...
Important: if reporting any issues, provide applicable info (GUI syslog, `dmesg`, `cat /var/log/messages`, etc.)
Or put into SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).
Template to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):
WARNING:This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Please avoid discussions and create a new thread to discuss specific problems or questions, as this thread is for reporting, not support. Posts may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build.
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r41379 std (10/24/19)
Kernel: Linux 4.4.197 #156 SMP Thu Oct 24 11:35:58 +04 2019 armv7l
Previous: r41375
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working well so far.
Uptime: 8min
Temperatures: CPU 65.8 °C / WL0 47.0 °C / WL1 52.7 °C
Joined: 14 Sep 2019 Posts: 301 Location: Maine, USA
Posted: Thu Oct 24, 2019 22:09 Post subject:
Router/Version: Asus RT-N66U
File: dd-wrt.v24-41379_NEWD-2_K3.x_mega_RT-N66U.trx
Kernel: Linux 3.10.108-d8 #42 Thu Oct 24 17:40:44 +04 2019 mips
Mode: AP w/USB
Previous: r41328
Reset?: N
Status: Working
Router/Version: Asus RT-N12D
File: dd-wrt.v24-41379_NEWD-2_K3.x_mega.bin
Kernel: Linux 3.10.108-d8 #42 Thu Oct 24 17:40:44 +04 2019 mips
Mode: Router/OpenVPN client
Previous: r41328
Reset?: N
Status: Working
Flashed from gui. Syslogs clean. Up 30 minutes. Wait to see if timer/rekey issue reappears as in previous versions.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Thu Oct 24, 2019 22:11 Post subject: Cisco Linksys E4200 v1
Router Model / Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-41379_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r41379 mega (10/24/19)
Kernel: Linux 3.10.108-d8 #42 Thu Oct 24 17:40:44 +04 2019 mips
Previous: DD-WRT v3.0-r41358 mega (10/20/19)
Reset: No
Mode: Gateway / AP - QoS (HFSC+FQ_CODEL_FAST)
Uptime: ~ 5:25
Status: OK
Issues / Errors: Nothing new to report. Funny how I flash this as alpha, report that it's good to go for MIPS, and here we are lol
Posted: Fri Oct 25, 2019 3:08 Post subject: broadcom_K3X_mipsel32r1
was wondering when would someone use broadcom_K3X_mipsel32r1 vs using broadcom_K3X also i got a WNDR4000, been using K3X would the mipsel32r1 build be better?(notice the K3X is about a 32kb larger than mipsel32r1 build)
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Fri Oct 25, 2019 4:28 Post subject: Re: broadcom_K3X_mipsel32r1
mali843 wrote:
was wondering when would someone use broadcom_K3X_mipsel32r1 vs using broadcom_K3X also i got a WNDR4000, been using K3X would the mipsel32r1 build be better?(notice the K3X is about a 32kb larger than mipsel32r1 build)
I have no details on what those experimental builds are for, but your router is a MIPSR2, so using that build may not be a good idea.
Router: Netgear R7000P
Kernel: Linux 4.4.197 #161 SMP Thu Oct 24 12:15:07 +04 2019 armv7l
Mode: Gateway / AP / Unbound
Reset: No
Uptime: 9hrs
Status: all seems well
Posted: Fri Oct 25, 2019 14:54 Post subject: Re: broadcom_K3X_mipsel32r1
kernel-panic69 wrote:
mali843 wrote:
was wondering when would someone use broadcom_K3X_mipsel32r1 vs using broadcom_K3X also i got a WNDR4000, been using K3X would the mipsel32r1 build be better?(notice the K3X is about a 32kb larger than mipsel32r1 build)
I have no details on what those experimental builds are for, but your router is a MIPSR2, so using that build may not be a good idea.
Ya, I would advise against trying the k3.10 r1 driver build on an r2 device.
The mips32r1 build is for k2.x devices; of course so far it only fits 8MB+ devices, which are limited. BS is running it on a wrt600n v1.1, and is working on a smaller version but having cpu/kernel issues.
BS wrote:
in theory wrt300n should work too and some others like the wrt610nv1. in theory the version should even work on a wrt54gs but i was unable to test it yet. however, the mips32r1 wireless driver is currently just tuned for the wrt600n and i did not include wifi chipset support for all devices yet
I don't have any 8+MB k2.x devices. Anyone got a GSv1-3 to test (sacrifice)? _________________ #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
Posted: Fri Oct 25, 2019 17:05 Post subject: Re: broadcom_K3X_mipsel32r1
kernel-panic69 wrote:
mali843 wrote:
was wondering when would someone use broadcom_K3X_mipsel32r1 vs using broadcom_K3X also i got a WNDR4000, been using K3X would the mipsel32r1 build be better?(notice the K3X is about a 32kb larger than mipsel32r1 build)
I have no details on what those experimental builds are for, but your router is a MIPSR2, so using that build may not be a good idea.
Router/Version: Cisco-Linksys EA2700
File: dd-wrt-41379-ea2700.trx
Firmware: DD-WRT v3.0-r41379 giga (10/24/19)
Kernel: Linux 3.10.108-d8 #30 Thu Oct 24 17:26:48 +04 2019 mips
CPU: Broadcom BCM5357 chip rev 2 (BCM47186)
CPU Features: MIPS32r1 MIPS32r2 MIPS16 DSP DSP2
CPU Frequency: 480 MHz (some said 500MHz)
Mode: Gateway/AP
TCP Congestion Control: Westwood
Status: transport layer (UDP/TCP) hangs or disconnections in wireless LAN
I can't find "HONG KONG" in Regulatory Domain of Wireless setting page in webGUI anymore. So what should I choose now? Wifi standard in Hong Kong is different from the mainland China after all...
And the problem of the "Apply Settings" button is still existed. Pressing "Apply Settings" button in the Wireless Security page with any random configs or even just keeping default "no security", does always brick my router until unplugging power and re-plug the power again (hard power restart). Sometimes just pressing "Reboot Router" button does brick my router as well, until unplugging power and re-plug the power again, too. This bug should be fixed as soon as possible. The ticket for this bug was created before already: https://svn.dd-wrt.com/ticket/6721
Several recent builds are much better than the ancient builds already, less TCP/UDP hangs and shorter hang/recovery time. Great job!
Seems like improving things like nl80211, mac80211, cfg80211 or ndpi-netfilter has improved wifi so much. Good job and keep on!
But nothing helps anymore whatever even use WPA2 only and AES only, Group Key Renewal Interval set to 0 and default English WebGUI language, nothing improved and nothing different with all above.
use WPA2 only and AES only? nothing different.
Group Key Renewal Interval set to 0? nothing different.
Keep default English WebGUI language? nothing different as well.
Beside, I use these scripts as startup scripts, seem to make my router much smoother and further less hangs:
You see they just loosen the max. memory size limitations of TCP/UDP/socket connections. But any scripts modifying any queue sizes (e.g. netdev_max_backlog, tcp_max_syn_backlog) only make things worse.
67108864 = 64MB = Total physical RAM size of EA2700. Thought that might eat up much more memory than before, but finally overall not much difference than before, and only a few MB more junping up and down sometimes.
16384 pages mean 64MB Total physical RAM size as well, 4096 page size supposed.
IP filter maximum ports 65536 / 8 = 8192 hash size, which is a standard way.
Now I'm quite sure those TCP/UDP hangs in Wifi are related to the congestion control or something related around. There should be something conflicted or crashed/deadlocks inside somewhere of the congestion control working place or something related around.
Hangs usually happen when:
1. Suddenly huge amount of connections created at the same moment, whatever TCP or UDP or mixed, whatever how less amount of data each connection is actually transferring.
2. Any wifi devices newly connected (in link layer) to the AP or disconnected from the AP or shutdown.
3. Any wifi devices are woken up from a long-time sleep mode (e.g. turning on the screen of a phone) or wifi link speed changed (slower or faster than before, default auto Transmission Fixed Rate in DD-WRT)
4. Multiple wifi devices streaming videos or downloading large files at the same time.
I've tested about this for several weeks already, repeatedly proved that.
Usually images, video and audio connections hang much more than text or command connections.
Router CPU suddenly full of workload for at least half a minute or more. Nearly 100% loads, I have no ideas what was the Broadcom CPU busy for.
Wifi reactions become longer latency, longer response time after devices repeatedly connect and disconnect from the AP for many times. But much less hangs when longer latency, longer response time.
And I can only see some TX errors counted in Wifi AP, but always no any RX errors. Strange!
Conclusion: when the wifi link speed changes or busy transportations which trigger the congestion control take places, transport layer (TCP/UDP) hangs occur in wifi.
Hope this problem would be fixed completely soon.
P.S. 5GHz wifi radio device inside EA2700 is Broadcom BCM43236
Last edited by parco on Sat Oct 26, 2019 17:58; edited 2 times in total
Posted: Fri Oct 25, 2019 17:06 Post subject: Re: broadcom_K3X_mipsel32r1
WRT54GS v2 previous:
DD-WRT v3.0-r36841 mega [09/05/18]
Linux 2.4.37 #50496 Mi 5. Sep 07:00:10 CEST 2018 mips
GUI install: 'dd-wrt.v24_mega_generic.bin'
Linksys WRT54G/GL/GS
DD-WRT v3.0-r41379 mega (10/24/19)
Linux 2.4.37 #56723 Thu Oct 24 09:54:03 +04 2019 mips
all seems good
jwh7 wrote:
Anyone got a GSv1-3 to test (sacrifice)?
reset
attempt to install the mipsel32r1
rejects (reboots it) in 'bout 2 seconds however the unit comes back alive in couple minutes
webif good with r41379 same previous firmware
I thought it might be a size problem but NO, this unit should be good for 7,995,392 bytes
Don't know how far this goes back, but all of the colored themes are the same color in this build. Other themes work correctly though. (I did not do a reset)
Posted: Fri Oct 25, 2019 21:31 Post subject: E1200v2
Router/Version: E1200v2
File: DD-WRT v3.0-r41379 mega (10/24/19)
Kernel: Linux 3.10.108-d8 #42 Thu Oct 24 17:40:44 +04 2019 mips
Mode: Router with QOS enabled
Status: Working so far
Uptime: 1hr 25min
Temps: 48.3 °C
Overclock: 400Mhz (300Mhz stock)
Not sure if it was the new build or the overclock (will check) but the CPU usage has dropped using QOS. QOS is applied to the WAN interface with HFSC PIE (cake was highest CPU usage) with a 15Mbps limit.
Posted: Sat Oct 26, 2019 18:33 Post subject: WRT54G2 v1
I just flashed my WRT54G2 v1 from 10/1/19 build to this version 10/24/19.
So far this build has been working fine without issues. _________________ WRT54GL v1.1 - Flashed
Linksys WRT54G2 v1 - Flashed
EA6350 v2 - Flashed