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. _________________ #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
Asus RT-N12D1
DD-WRT v3.0-r40260 mega (07/09/19)
Linux 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips
[dd-wrt.v24-40260_NEWD-2_K3.x_mega.bin]
Just a WAP, No VAP -- tis all worky good
##
Linksys E2500
DD-WRT v3.0-r40260 mega (07/09/19)
Linux 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips
[dd-wrt.v24-40260_NEWD-2_K3.x_mega.bin]
'Repeater' mode setup to test
#
Linksys E1200 v2
Firmware Version
DD-WRT v3.0-r40260 mega (07/09/19)
Kernel Version
Linux 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips
[dd-wrt.v24-40260_NEWD-2_K3.x_mega-nv64k.bin]
'Repeater' mode setup to test
spare Asus RT-N12D1 with r40260
'Repeater' mode setup to test
All three of the units --- same ol broadcom buggy VAP crap been there long time now.
VAP (all its functions) not fully start after an install or reboot.
Just some minor testing --- wired clients to 'Repeater' mode router is fine but wireless clients CANNOT connect to its VAP
until you 'Apply Settings' at ../Wireless_Basic.asp ...even though the VAP does broadcast after reboot.
and yea I know there is various startup commands you can use to make it work besides having to go into the webif but that ain't the point ---
This should be fixed
Joined: 08 May 2018 Posts: 14208 Location: Texas, USA
Posted: Wed Jul 10, 2019 15:26 Post subject:
mrjcd wrote:
All three of the units --- same ol broadcom buggy VAP crap been there long time now.
VAP (all its functions) not fully start after an install or reboot.
Just some minor testing --- wired clients to 'Repeater' mode router is fine but wireless clients CANNOT connect to its VAP
until you 'Apply Settings' at ../Wireless_Basic.asp ...even though the VAP does broadcast after reboot.
and yea I know there is various startup commands you can use to make it work besides having to go into the webif but that ain't the point ---
This should be fixed
This is also tied to the damn channel and mode selection, etc. issues that are STILL PRESENT. It is really annoying, I have noticed even after the router is up and running, doesn't matter, you go to the basic page, and something randomly goes askew and while it MAY NOT AFFECT the actual settings in use, it is definitely an issue. That all being said, I saw no specific commits since 40189 except for the user access blocklist feature that are of any interest for Broadcom, if it's even being implemented for Broadcom builds
All three of the units --- same ol broadcom buggy VAP crap been there long time now.
VAP (all its functions) not fully start after an install or reboot.
Just some minor testing --- wired clients to 'Repeater' mode router is fine but wireless clients CANNOT connect to its VAP
until you 'Apply Settings' at ../Wireless_Basic.asp ...even though the VAP does broadcast after reboot.
and yea I know there is various startup commands you can use to make it work besides having to go into the webif but that ain't the point ---
This should be fixed
This is also tied to the damn channel and mode selection, etc. issues that are STILL PRESENT. It is really annoying, I have noticed even after the router is up and running, doesn't matter, you go to the basic page, and something randomly goes askew and while it MAY NOT AFFECT the actual settings in use, it is definitely an issue. That all being said, I saw no specific commits since 40189 except for the user access blocklist feature that are of any interest for Broadcom, if it's even being implemented for Broadcom builds
It seems like the developers just focus on the new optional functions rather than really thoroughly debug the essential core functions like SFE, VAP and any other malfunctions of the basic route server core..... When the SFE fails to function, VAP fails to function, unstable connections, hang connections, even stops routing, stops connections, stops functions, what more is the damn definition of "a router"? Maybe I'm too old to comprehend..... I'm too out of date...... Can't understand the new definition of "a router" defined by the new and next generations.....
Joined: 08 May 2018 Posts: 14208 Location: Texas, USA
Posted: Wed Jul 10, 2019 17:56 Post subject:
parco wrote:
It seems like the developers just focus on the new optional functions rather than really thoroughly debug the essential core functions like SFE, VAP and any other malfunctions of the basic route server core..... When the SFE fails to function, VAP fails to function, unstable connections, hang connections, even stops routing, stops connections, stops functions, what more is the damn definition of "a router"? Maybe I'm too old to comprehend..... I'm too out of date...... Can't understand the new definition of "a router" defined by the new and next generations.....
Atheros/IPQ seems to be the priority lately. Marvell is even ahead of Broadcom on the list of focus, it seems. It is really painstaking to focus just on the Broadcom-specific code in the DD-WRT base. It gives me headaches. I have my ideas on where the problems are, but I have no *glue*.
It seems like the developers just focus on the new optional functions rather than really thoroughly debug the essential core functions like SFE, VAP and any other malfunctions of the basic route server core..... When the SFE fails to function, VAP fails to function, unstable connections, hang connections, even stops routing, stops connections, stops functions, what more is the damn definition of "a router"? Maybe I'm too old to comprehend..... I'm too out of date...... Can't understand the new definition of "a router" defined by the new and next generations.....
Atheros/IPQ seems to be the priority lately. Marvell is even ahead of Broadcom on the list of focus, it seems. It is really painstaking to focus just on the Broadcom-specific code in the DD-WRT base. It gives me headaches. I have my ideas on where the problems are, but I have no *glue*.
I've just updated your SFE ticket, and someone seemed to update my TX queue length ticket, please check.
It seems like the developers just focus on the new optional functions rather than really thoroughly debug the essential core functions like SFE, VAP and any other malfunctions of the basic route server core..... When the SFE fails to function, VAP fails to function, unstable connections, hang connections, even stops routing, stops connections, stops functions, what more is the damn definition of "a router"? Maybe I'm too old to comprehend..... I'm too out of date...... Can't understand the new definition of "a router" defined by the new and next generations.....
Atheros/IPQ seems to be the priority lately. Marvell is even ahead of Broadcom on the list of focus, it seems. It is really painstaking to focus just on the Broadcom-specific code in the DD-WRT base. It gives me headaches. I have my ideas on where the problems are, but I have no *glue*.
And this is how the Broadcom hardware router users feel like to be treated now:
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r40260 std (07/09/19)
Kernel: Linux 4.4.184 #410 PREEMPT Tue Jul 9 08:22:25 CEST 2019 armv7l
Mode: Gateway
Previous: 38155
Reset: No
Status: OK (dhcp, static leases, unbound, smb, wireless all working so far). Webif seems to load slower than previously though.
Joined: 08 May 2018 Posts: 14208 Location: Texas, USA
Posted: Thu Jul 11, 2019 10:58 Post subject:
rnix wrote:
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r40260 std (07/09/19)
Kernel: Linux 4.4.184 #410 PREEMPT Tue Jul 9 08:22:25 CEST 2019 armv7l
Mode: Gateway
Previous: 38155
Reset: No
Status: OK (dhcp, static leases, unbound, smb, wireless all working so far). Webif seems to load slower than previously though.
Most likely because of this change which limits the total number of threads in httpd: https://svn.dd-wrt.com/changeset/40029. It seems to slow down the webUI. I forgot to mention that in the thread for 40065.
EDIT: I may flash this build to see if the user access blocking feature slowed it down any further.
Last edited by kernel-panic69 on Thu Jul 11, 2019 18:59; edited 1 time in total
Joined: 26 Mar 2013 Posts: 1856 Location: Hung Hom, Hong Kong
Posted: Thu Jul 11, 2019 15:44 Post subject:
mrjcd wrote:
All three of the units --- same ol broadcom buggy VAP crap been there long time now.
VAP (all its functions) not fully start after an install or reboot.
Just some minor testing --- wired clients to 'Repeater' mode router is fine but wireless clients CANNOT connect to its VAP
until you 'Apply Settings' at ../Wireless_Basic.asp ...even though the VAP does broadcast after reboot.
and yea I know there is various startup commands you can use to make it work besides having to go into the webif but that ain't the point ---
This should be fixed
Someone in the Kong's new build said (again?) VAP was fixed, no work-around needed... is there a bridge to port it over? Meow...
Joined: 08 May 2018 Posts: 14208 Location: Texas, USA
Posted: Thu Jul 11, 2019 18:41 Post subject:
mwchang wrote:
mrjcd wrote:
All three of the units --- same ol broadcom buggy VAP crap been there long time now.
VAP (all its functions) not fully start after an install or reboot.
Just some minor testing --- wired clients to 'Repeater' mode router is fine but wireless clients CANNOT connect to its VAP
until you 'Apply Settings' at ../Wireless_Basic.asp ...even though the VAP does broadcast after reboot.
and yea I know there is various startup commands you can use to make it work besides having to go into the webif but that ain't the point ---
This should be fixed
Someone in the Kong's new build said (again?) VAP was fixed, no work-around needed... is there a bridge to port it over? Meow...
For some devices it works fine, others, not so much. As they say, YMMV. I think if the bridge modes (client, repeater) were removed, and a few other things done, it would help, but my eyes get cross-eyed staring at thousands of lines of code trying to find the problems.
