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.
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.
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r40048 std (06/16/19)
Kernel: Linux 4.4.181 #257 SMP PREEMPT Sun Jun 16 09:09:54 CEST 2019 armv7l
Previous: r40009
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working so far.
Uptime: 42min
Temperatures: CPU 66.9 °C / WL0 47.8 °C / WL1 54.0 °C
Router/Version: Linksys EA6300 v1/EA6400
Firmware: DD-WRT v3.0-r40048 std (06/16/19)
Kernel: Linux 4.4.181 #257 SMP PREEMPT Sun Jun 16 09:09:54 CEST 2019 armv7l
Previous: DD-WRT v3.0-r39927 std (06/03/19)
Mode/Status: Gateway / working
Reset: no
Issues/Errors: VAP cann't work in this release, but VAP is work well in r39927
Posted: Mon Jun 17, 2019 14:05 Post subject: Netgear WNDR4000
Router/Version: Netgear WNDR4000
File: dd-wrt.v24-40048_NEWD-2_K3.x_mega-nv64k.bin
Kernel: Linux 3.10.108-d8 #24933 Sun Jun 16 16:27:47 CEST 2019 mips
Firmware: DD-WRT v3.0-r40048 mega (06/16/19)
Previous: DD-WRT v24-sp2 (06/07/14) vpnkong - build 22000M
Reset: No
Mode: Gateway/AP with VAPs
Status: Great !!
Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Mon Jun 17, 2019 15:35 Post subject:
b]Router Model:[/b] Netgear R6400v1
Firmware Version: DD-WRT v3.0-r40048 std (06/16/19)
Kernel Version: Linux 4.4.181 #257 SMP PREEMPT Sun Jun 16 09:09:54 CEST 2019 armv7
Upgraded: from DD-WRT v3.0-r38580M Kong, via GUI
Reset: No, which I would normally do because i am changing from Kong to BS, But I was asked to test SFE and UDP forwarding so just did a dirty upgrade
Status: Up and running 4 hours, basic setup as Gateway, static leases, Advanced routing, Port Forwarding, IPv4, DynDNS, 2.4 GHz and 5 GHz
Errors: No, I upgraded to this version to test UDP forwarding with SFE which was broken on the latest builds.
From limited testing UDP forwarding seems to work with SFE!
DNSCrypt v2 is backwards compatible to 1.95
its still working on my R7800 very well...
Now, are you saying you installed dnscrypt-proxy version 2.x via Entware /off-topic
I thought Alozaros meant that v1.95 on his R7800 is able to work with v2 servers. Some clarification would help though. _________________ #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
Router/Version: ASUS RT-AC3200 File: asus_rt-ac3200-firmware.trx Kernel: Linux 4.4.181 #262 SMP PREEMPT Sun Jun 16 09:41:57 CEST 2019 armv7l Mode: Gateway Status: Losing my download speed.
Didn't change anything other then flash 40009 to 40048.
Internet speed is 100Mbits down without QoS enabled. With QoS enabled it down to 30-33Mbits used to be fine at around 92-96Mbits. Turn off QoS run fines. Not sure why I am losing so much speed with this build.
Also note - while running speed test and monitoring sirq in ssh, it is hitting 79-89%
Disabling SFE make no difference _________________ ASUS RT-AC3200 - Deployed Client's site
ASUS RT-AC5200 - Merlin
ASUS RT-AX88U - Merlin
...upgraded to this version to test UDP forwarding with SFE which was broken on the latest builds.
From limited testing UDP forwarding seems to work with SFE!
Big Thanks to the devs
Hmm, I wonder if this is why connecting to Xbox party chat has been problematic for me since late April after installing r39572 [SFE + PBR fix].
Issue has been: when first connecting, Xbox part chat cycles though the following statuses until things finally connect after about 30 seconds...
DNSCrypt v2 is backwards compatible to 1.95
its still working on my R7800 very well...
Now, are you saying you installed dnscrypt-proxy version 2.x via Entware /off-topic
I thought Alozaros meant that v1.95 on his R7800 is able to work with v2 servers. Some clarification would help though.
Bingo.
I believe what he said & what he meant are one & the same...
I also still happily use DNSCrypt...
Most servers I use bark in the log that the server is using version 2.0 of the DNsCrypt protocol every hour when it documents the server certificate re-vallidation.....but all "appears" to be working without issue ¯\_(ツ)_/¯ _________________ Location 1
R7800- DD-WRT v3.0-r53562 (10/03/23) Gateway
WNDR3400v1 DD-WRT v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R7800- DD-WRT v3.0-r51855 (02/25/23) Gateway
R6300v2- DD-WRT v3.0-r50671 (10-26-22) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
RBWAPG-5HACT2HND-BE RouterOS-v6.46.4 (2/21/20) Outdoor Access Point
2x RBSXTG-5HPACD RouterOS-v6.46.4 (2/21/20) PTP Bridge 866.6Mbps-1GbpsLAN
Location 3
2x R7000- DD-WRT v3.0-r50671 (10/26/22) Access Points
2x RBWAPG-60AD RouterOS-v6.45.9 (04/30/20) PTP Bridge 2.3Gbps-1GbpsLAN
2x RBSXTsqG-5acD RouterOS-v6.49.7 (10/14/22) PTP Bridge 866.6Mbps-1GbpsLAN Thank You BrainSlayer for ALL that you do & have done, also to "most" everyone here that shares their knowledge
...upgraded to this version to test UDP forwarding with SFE which was broken on the latest builds.
From limited testing UDP forwarding seems to work with SFE!
Big Thanks to the devs
Hmm, I wonder if this is why connecting to Xbox party chat has been problematic for me since late April after installing r39572 [SFE + PBR fix].
Issue has been: when first connecting, Xbox part chat cycles though the following statuses until things finally connect after about 30 seconds...
Gamertag1 - connected
Gamertag2 - connected
Gamertag1 - connected
Gamertag2 - connecting
Gamertag1 - connecting
Gamertag2 - connecting
Gamertag1 - connected
Gamertag2 - connected
similar to my case but connecting from my phone instead of xbox
Posted: Tue Jun 18, 2019 23:05 Post subject: DHCP Issues
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r40048 std (06/16/19)
Kernel: Linux 4.4.181 #257 SMP PREEMPT Sun Jun 16 09:09:54 CEST 2019 armv7l
Previous: unknown (fairly recent build, this year)
FOUND IT, 38840
Mode/Status: Gateway / working
Reset: nvram erase
Issues/Errors: When I set a static DHCP lease inside/outside the pool and reboot, the DHCP server no longer assigns IPs to clients. I can access everything fine setting a static on clients.
I've done some crazy troubleshooting. Hours worth. Tried the latest Kong build too.
Going to start working backwards until it hopefully works.