Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 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)
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-r39884 std (05/30/19)
Kernel: Linux 4.4.180 #136 SMP PREEMPT Thu May 30 08:42:27 CEST 2019 armv7l
Previous: r39866
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working so far. Fixed - WAN remaining lease time shows a non-zero value again.
Uptime: 1h 2m
Temperatures: CPU 66.4 °C / WL0 47.5 °C / WL1 53.3 °C
Asus RT-N12D1still shows in webif as an Asus RT-N12B
DD-WRT v3.0-r39884 (05/30/19)
Linux 3.10.108-d8 #24659 Thu May 30 15:10:10 CEST 2019 mips
[dd-wrt.v24-39884_NEWD-2_K3.x_mega.bin]
reset and put into 'repeater' mode ... no trouble with its VAP
#
EDIT:
It's been reset to defaults with its WAN pluged into my main network and '../Status_Internet.asp' shows --
Connection Uptime 0:27:18
Remaining Lease Time 0 days 23:33:13
so reckon that's ok
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Fri May 31, 2019 1:45 Post subject:
Yes, WAN DHCP lease time was fixed, as well as I think syslog timestamps, but as usual, the updated SFE patch to the K3X builds isn't included in this build, so, I am sitting this one out. It is really aggravating when a build is run a commit or two short of where it should be.
Router: Buffalo WZR-1750DHP
Firmware: buffalo-wzr-1750dhp-webflash.bin (v3.0-r398864 std)
Kernel: Linux 4.4.180 #136 SMP PREEMPT Thu May 30 08:42:27 CEST 2019 armv7l
Status: Working
Reset: No
Notes on configuration:
FTP server
DNSMasq
DNSSEC
USB v3.0
DHCP reservation
Router/Version: Netgear R7000P
Firmware: DD-WRT v3.0-r39884 std (05/30/19)
Kernel: Linux 4.4.180 #141 SMP PREEMPT Thu May 30 09:14:02 CEST 2019 armv7l
Mode: AP
Status: running well
Issues: no issues but not specific to this build I get this error.
Dec 31 19:00:16 DD-WRT kern.err kernel: bcmsflash: found no supported devices
it has been showing up here and there for a while now. recently it shows every boot. it doesn't seem to effect anything. is this something that just pops up or did i break something?
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Fri May 31, 2019 22:58 Post subject:
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-39884_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-39866_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #24659 Thu May 30 15:10:10 CEST 2019 mips
Mode: Both basic client bridges with everything not required turned off.
Status: Working, however see below
I've used these two E3000 boxes for a long time now with no problem. But sometime in the last few builds (I don't know exactly what one, apologies), when setting the DHCP server to off, as well as dnsmasq to off (both not required for a client bridge), upon reboot, the dnsmasq toggle is enabled and there is a dnsmasq process running with "/tmp/dnsmasq.conf" as the file (which I never set up...). It caused a few issues, which I solved with this in the startup script:
Code:
# Disable dnsmasq as it seems to be starting on boot <-- Unwanted!
nvram set dnsmasq_enable=0
rm /tmp/dnsmasq.conf
killall dnsmasq
After adding that, the computers/devices get correct assignments from the AP router really quick. Before adding that, it was a hit or miss with how fast they got their assigned IP (normally took awhile).
I figured this out as I was doing a total rebuild of all my networks, so I think it's not supposed to happen? And if it is, mind informing me why and what it does? Like I said, I got much better performance when disabling and killing the "rouge" dnsmasq server on my client bridges.
Router/Version: Asus RT-N66U
File: dd-wrt.v24-39884_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r39884 big (05/30/19)
Kernel: Linux 3.10.108-d8 #24655 Thu May 30 15:06:08 CEST 2019 mips
Mode: Gateway, Wifi disabled
Reset: No
Status: syslog shows correct time :), maybe this fixed the reboot issue (have to test), ~24h up.
Issues: no issues but not specific to this build I get this error.
Dec 31 19:00:16 DD-WRT kern.err kernel: bcmsflash: found no supported devices
it has been showing up here and there for a while now. recently it shows every boot. it doesn't seem to effect anything. is this something that just pops up or did i break something?
It should've been there ever since you started using that router.....& paid attention...
Don't take my word.....As who am I? ¯\(°_o)/¯
<Kong> wrote:
Only the 8/16MB units have sflash. The others have nand
So...That is not an issue nor an error...but rather a statement ¯\_(ツ)_/¯ _________________ 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
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Sat Jun 01, 2019 2:01 Post subject:
SinCalChewy wrote:
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-39884_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-39866_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #24659 Thu May 30 15:10:10 CEST 2019 mips
Mode: Both basic client bridges with everything not required turned off.
Status: Working, however see below
I've used these two E3000 boxes for a long time now with no problem. But sometime in the last few builds (I don't know exactly what one, apologies), when setting the DHCP server to off, as well as dnsmasq to off (both not required for a client bridge), upon reboot, the dnsmasq toggle is enabled and there is a dnsmasq process running with "/tmp/dnsmasq.conf" as the file (which I never set up...). It caused a few issues, which I solved with this in the startup script:
Code:
# Disable dnsmasq as it seems to be starting on boot <-- Unwanted!
nvram set dnsmasq_enable=0
rm /tmp/dnsmasq.conf
killall dnsmasq
After adding that, the computers/devices get correct assignments from the AP router really quick. Before adding that, it was a hit or miss with how fast they got their assigned IP (normally took awhile).
I figured this out as I was doing a total rebuild of all my networks, so I think it's not supposed to happen? And if it is, mind informing me why and what it does? Like I said, I got much better performance when disabling and killing the "rouge" dnsmasq server on my client bridges.
Good day.
Did you set all dnsmasq related settings to disabled on services tab and un-check all dhcp-related settings on basic setup tab? There's some sort of magic voodoo to make it work, usually, but then again, the 'fix' to remove udhcpd was 'incomplete'... perhaps.
i have since enabled USB and it went away. now I get a different one. looks like it's just tied to me enabling different things. thanks for the replies.
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Sat Jun 01, 2019 9:35 Post subject:
kernel-panic69 wrote:
SinCalChewy wrote:
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-39884_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-39866_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #24659 Thu May 30 15:10:10 CEST 2019 mips
Mode: Both basic client bridges with everything not required turned off.
Status: Working, however see below
I've used these two E3000 boxes for a long time now with no problem. But sometime in the last few builds (I don't know exactly what one, apologies), when setting the DHCP server to off, as well as dnsmasq to off (both not required for a client bridge), upon reboot, the dnsmasq toggle is enabled and there is a dnsmasq process running with "/tmp/dnsmasq.conf" as the file (which I never set up...). It caused a few issues, which I solved with this in the startup script:
Code:
# Disable dnsmasq as it seems to be starting on boot <-- Unwanted!
nvram set dnsmasq_enable=0
rm /tmp/dnsmasq.conf
killall dnsmasq
After adding that, the computers/devices get correct assignments from the AP router really quick. Before adding that, it was a hit or miss with how fast they got their assigned IP (normally took awhile).
I figured this out as I was doing a total rebuild of all my networks, so I think it's not supposed to happen? And if it is, mind informing me why and what it does? Like I said, I got much better performance when disabling and killing the "rouge" dnsmasq server on my client bridges.
Good day.
Did you set all dnsmasq related settings to disabled on services tab and un-check all dhcp-related settings on basic setup tab? There's some sort of magic voodoo to make it work, usually, but then again, the 'fix' to remove udhcpd was 'incomplete'... perhaps.
I spent a good two or so hours trying to disable it via the GUI. I disabled everything dhcp and dnsmasq, and still, every reboot dnsmasq would "re-enable" itself. For now the "fix" I posted works (speeds much faster), but I will definitely be checking into doing it in a less "hack-y" way. _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Joined: 18 Mar 2014 Posts: 12836 Location: Netherlands
Posted: Sat Jun 01, 2019 16:18 Post subject:
Router Model: Linksys E2000 (converted N320)
Firmware Version: DD-WRT v3.0-r39884 mega (05/30/19)
Kernel Version: Linux 3.10.108-d8 #24659 Thu May 30 15:10:10 CEST 2019 mips
Upgraded: from DD-WRT v3.0-r39866 mega (05/27/19) with IE, Firefox seems flaky when updating
Reset: No, not this time
Status: Up and running for 18 hours, basic setup as Gateway, static leases, OpenVPN client (tun) (on PIA) up and running, VPN download speed 5-6 Mb/s, Wifi 2,4GHz working.
OpenVPN server tested and working
I have tested the new unidirectional firewall (Inbound Firewall on TUN) for OVPN client and can see that the necessary firewall rules are in place, good job!
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Sat Jun 01, 2019 16:36 Post subject:
SinCalChewy wrote:
kernel-panic69 wrote:
SinCalChewy wrote:
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-39884_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-39866_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #24659 Thu May 30 15:10:10 CEST 2019 mips
Mode: Both basic client bridges with everything not required turned off.
Status: Working, however see below
I've used these two E3000 boxes for a long time now with no problem. But sometime in the last few builds (I don't know exactly what one, apologies), when setting the DHCP server to off, as well as dnsmasq to off (both not required for a client bridge), upon reboot, the dnsmasq toggle is enabled and there is a dnsmasq process running with "/tmp/dnsmasq.conf" as the file (which I never set up...). It caused a few issues, which I solved with this in the startup script:
Code:
# Disable dnsmasq as it seems to be starting on boot <-- Unwanted!
nvram set dnsmasq_enable=0
rm /tmp/dnsmasq.conf
killall dnsmasq
After adding that, the computers/devices get correct assignments from the AP router really quick. Before adding that, it was a hit or miss with how fast they got their assigned IP (normally took awhile).
I figured this out as I was doing a total rebuild of all my networks, so I think it's not supposed to happen? And if it is, mind informing me why and what it does? Like I said, I got much better performance when disabling and killing the "rouge" dnsmasq server on my client bridges.
Good day.
Did you set all dnsmasq related settings to disabled on services tab and un-check all dhcp-related settings on basic setup tab? There's some sort of magic voodoo to make it work, usually, but then again, the 'fix' to remove udhcpd was 'incomplete'... perhaps.
I spent a good two or so hours trying to disable it via the GUI. I disabled everything dhcp and dnsmasq, and still, every reboot dnsmasq would "re-enable" itself. For now the "fix" I posted works (speeds much faster), but I will definitely be checking into doing it in a less "hack-y" way.
you can disable DHCP from basic setup page... just set it to disable... you cannot disable whole dnsmasq because it is used for DNS... e.g. ntpclient uses DNS if you enter hostanme as a time server...