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 build 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. Since 39469, udhcpd was removed and replaced with the already present dnsmasq, and PIE qdisc was added for some builds.
5. Policy-Based Routing with SFE enabled was fixed in r39556: 5986 and 5900 6. k2.4 (broadcom/) builds were fixed in 39715 (broken in 39144 through 39654)
7.SFE update (k3.10+ for BCM) was in the 39927 build.
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 to be fixed for some routers (different kernels, modes, and radios) since build 39508. 6.UDP forwarding might not work with SFE Enabled: 6668
Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
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.
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Fri Jul 12, 2019 22:52 Post subject:
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-40274_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-40260_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #25353 Fri Jul 12 15:40:31 CEST 2019 mips
Mode: Client bridges, all settings not required turned off.
Status: So far so good! :)
Router/Version: Linksys E1200v2
Firmware: dd-wrt.v24-40274_NEWD-2_K3.x_mega-e1200v2.bin
Previous: dd-wrt.v24-40260_NEWD-2_K3.x_mega-e1200v2.bin
Kernel: Linux 3.10.108-d8 #25353 Fri Jul 12 15:40:31 CEST 2019 mips
Mode: Client.
Status: Seems to be working, not used much. _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Last edited by SinCalChewy on Fri Jul 12, 2019 23:16; edited 1 time in total
Router/Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-40274_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r40274 mega (07/12/19)
Kernel: Linux 3.10.108-d8 #25353 Fri Jul 12 15:40:31 CEST 2019 mips
Previous: DD-WRT v3.0-r40189 mega (07/04/19)
Reset: No
Mode: Gateway/AP
Uptime: ~2h 50m
Status: OK
Issues/Errors: Nothing new so far. Looks like the Broadcom K3.x builds were two revision numbers prior, which means the only thing missing was the php updates in r40275 & r40276 commits.
EDIT: I have noticed that the webUI is a little smoother after removing the thread number limitation and adding nanosleep.
Last edited by kernel-panic69 on Sat Jul 13, 2019 19:52; edited 1 time in total
Posted: Sat Jul 13, 2019 9:12 Post subject: Re: Cisco Linksys E4200 v1
kernel-panic69 wrote:
Router/Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-40274_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r40274 mega (07/12/19)
Kernel: Linux 3.10.108-d8 #25353 Fri Jul 12 15:40:31 CEST 2019 mips
Previous: DD-WRT v3.0-r40189 mega (07/04/19)
Reset: No
Mode: Gateway/AP
Uptime: ~2h 50m
Status: OK
Issues/Errors: Nothing new so far. Looks like the Broadcom K3.x builds were two revision numbers prior, which means the only thing missing was the php updates in r40275 & r40276 commits.
Finally I have just disabled the shitty buggy Shortcut Forwarding Engine now. I can't take it anymore. I rather keep backing to the traditional netfilter instead now. Thanks god everything is running smooth and well like 2 years ago now. no more connection hangs for wifi now. Network transportation between WAN and LAN seems even much faster than SFE, with same full speed for my 100Mbps ISP, no bandwidth drops. I have even restored back all the txqueuelen (tx queue length) of eth0 eth1 and vlan2 back to their default 1000, with no any speed changes and latency differences in result, a big surprise for me!!
It seems like the queue lengths get no issues for me even if just 2 or 20000, can't notice the differences. But I can 1000000% ensure now, the source of the problems, is ABSOLUTELY the SFE, the Shortcut Forwarding Engine makes all the connection problems of whatever UDP or TCP out for our Broadcom MIPS SoC routers. SFE is our nightmare. So I am going to keep disabling SFE until one day you guys are telling me that the SFE has been really fixed and I can really prove that.
The latest completely stable build of DD-WRT with staying all default config for my Linksys EA2700 was r33555, which no any issues for me. I can't imagine what are the differences after r33555, what codes changed after that
My ISP just simply provides me 100Mbps, with a fiber coming into my house I can see (just single fiber, maybe half-duplex fiber I guess), then a fiber to ethernet converter come from my ISP (not my own), and a simple ethernet into my router WAN port. For my WAN config, just simple ethernet cable DHCP I need, from my ISP, the simple DHCP just like what you config for your own LAN, with auto MTU. I guess because the competition between ISPs in Hong Kong here is too keen here, and ISPs here just wanna catch up the level of Japanese ISPs (I heard Japanese ISPs provide full 100Mbps to resident consumers since 18 years ago already, now maybe 1Gbps or even 10Gbps per house). My ISP ever provided 1Gbps to us before, and that's why we have a fiber here. But we rarely need 100Gbps speed here, usually can't even transport full 100Mbps, so we decided to downgrade to 100Mbps with cheaper fee. In HK we can't order any bandwidth slower than 100Mbps anymore, no ISPs provide slower than 100Mbps broadband services here so we have no choices here. But of course here are still much slower cell phone plans we can choose. Anyway I still don't think our oversea backbone could let us really run our full 100Mbps, should have some kinds of traffic jams. The only benefit of 100Mbps I think is just when you transfer from your building to your neighbouring buildings, or within the same ISP, huh.....
P.S. hey I read that Broadcom hardwares support cut through forwarding, maybe DD-WRT could provide CTF to broadcom users instead of SFE? Seems like the SFE is full og bugs for Broadcom MIPS? or actually still not compatible with Broadcom MIPS especially the Broadcom CTF? ¯\_(ツ)_/¯
Last edited by parco on Sat Jul 13, 2019 10:54; edited 2 times in total
Router Model: TP-Link Archer C9v1 (BCM4709 1GHz & BCM4360)
Firmware: DD-WRT v3.0-r40276 std (07/12/19)
Kernel: Linux 4.4.185 #426 SMP PREEMPT Fri Jul 12 08:52:27 CEST 2019 armv7l
Status: 2.4 and 5 GHz WAPs for Edgerouter X, switch for PC
Reset: No
Issues: Does not support VAPs for both radios on a bridge. VAP's won't startup on boot. _________________ Linksys EA8500
Linksys EA6350v3
Edgerouter X
Last edited by eginnc on Sat Jul 20, 2019 13:28; edited 1 time in total
im on my phone but my Netgear R7000P is running well
noob question
how do you run that log txt?
Activate Syslogd and klogd on Services tab ("System Log" section), then go to Status->Syslog
If you want to see the dropped/rejected/accepted connections in the log, go to Security tab, and configure it in "Log Management" section (bottom of the page).
The last part of that log is using that sentence (cat /proc/cpuinfo) from telnet/ssh
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Sun Jul 14, 2019 3:24 Post subject: Re: Cisco Linksys E4200 v1
kernel-panic69 wrote:
Router/Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-40274_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r40274 mega (07/12/19)
Kernel: Linux 3.10.108-d8 #25353 Fri Jul 12 15:40:31 CEST 2019 mips
Previous: DD-WRT v3.0-r40189 mega (07/04/19)
Reset: No
Mode: Gateway/AP
Uptime: ~2h 50m
Status: OK
Issues/Errors: Nothing new so far. Looks like the Broadcom K3.x builds were two revision numbers prior, which means the only thing missing was the php updates in r40275 & r40276 commits.
EDIT: I have noticed that the webUI is a little smoother after removing the thread number limitation and adding nanosleep.
im on my phone but my Netgear R7000P is running well
noob question
how do you run that log txt?
Activate Syslogd and klogd on Services tab ("System Log" section), then go to Status->Syslog
If you want to see the dropped/rejected/accepted connections in the log, go to Security tab, and configure it in "Log Management" section (bottom of the page).
The last part of that log is using that sentence (cat /proc/cpuinfo) from telnet/ssh
In the Folder for Broadcom KX3 (ftp://ftp.dd-wrt.com/betas/2019/07-12-2019-r40276/broadcom_K3X/) all the names appoint to 40274, is that just a typo and it is really the build 40276, or is the wrong build? _________________