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-r40065 std (06/20/19)
Kernel: Linux 4.4.182 #284 SMP PREEMPT Thu Jun 20 11:19:37 CEST 2019 armv7l
Previous: r40048
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working so far.
Uptime: 4hrs 27min
Temperatures: CPU 67.5 °C / WL0 48.0 °C / WL1 53.8 °C
Asus RT-N12D1
DD-WRT v3.0-r40065 mega (06/20/19)
Linux 3.10.108-d8 #24993 Thu Jun 20 19:19:52 CEST 2019 mips
[dd-wrt.v24-40065_NEWD-2_K3.x_mega.bin]
No reset -- GUI install over r40009
just a WAP and all working ok .... up 2:54
Posted: Fri Jun 21, 2019 15:05 Post subject: Linksys EA6400
Router/Version: Linksys EA6400
File: DD-WRT v3.0-r40065 std (06/20/19)
Kernel: Linux 4.4.182 #284 SMP PREEMPT Thu Jun 20 11:19:37 CEST 2019 armv7l
Mode: Gateway/Router/Port Forwarding
Reset: No
Issues/Errors: Samba Server does not start automatically.
Router/Version: Linksys EA6900
File: DD-WRT v3.0-r40065 std (06/20/19)
Kernel: Linux 4.4.182 #284 SMP PREEMPT Thu Jun 20 11:19:37 CEST 2019 armv7l
Mode: AP
Status: working if no extended powerdown occurs
Issues/Errors:
Not only on this build and maybe is not related to it, but every time I have a long power off period, when booting on the routers doesn't allow access to web gui or shell and also not respond to pings. To fix I have to clear setting by manual reset using buttons and re-enter settings. Also had the same problems with builds from last 2018 quarter and 2019. I haven't found a way to recover detail of errors when locked.
Router/Version: Asus RT-N66U
File: dd-wrt.v24-40065_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r40065 big (06/20/19)
Kernel: Linux 3.10.108-d8 #24989 Thu Jun 20 19:14:04 CEST 2019 mips
Mode: Gateway, Wifi disabled
Reset: No
Status: ~36h up, keep alive (still) does not work. Utilizing the script mentioned in Wiki for restart purposes.
... keep alive (still) does not work. Utilizing the script mentioned in Wiki for restart purposes.
Keep Alive (Schedule Reboot - At a set Time Everyday) wasn't working for my ASUS RT-N66R for quite some time (several months?), then all of a sudden it started working again. I don't recall the exact dates, or which MEGA builds I'd used, but I believe I experienced the issue from about September [?] 2018 to about March [?] 2019. It has been working again since then, and it's still working now for me with the latest MEGA build.
I noticed that when I'd the problem, if I clicked on the 'Apply Settings' then the router would reboot once upon the next scheduled event, and then would stop working for subsequent events. I also suspect that a router settings reset, or Restore Factory Defaults, may be necessary, and the settings need to be reconfigured manually from scratch. However, I never bothered since my setup has numerous static leases and port forwarding requirements making a reset quite an ordeal. If it's not too troublesome with your setup, you might try a reset--if not already.
A time consuming task I'd like to avoid.
Last reset was a few months ago... maybe I should bite the bullet
I fully understand your predicament... You could do what I did during the period when it didn't work for me, just manually hit the 'Apply Settings' every couple of weeks or so. Enabling Keep Alive for me was a carryover from 3 or 4 routers ago, over 7 to 10 years' iterations of DD-WRT, when one of those routers back then would crash and hang over extended periods of operation. The DD-WRT MEGA builds have been quite stable for my ASUS RT-N66R, fulfilling my network requirements, so the Keep Alive function is not as critical for me now.
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r40065 std (06/20/19)
Kernel: Linux 4.4.182 #284 SMP PREEMPT Thu Jun 20 11:19:37 CEST 2019 armv7l
Previous: 39884
Mode: Gateway/AP
Reset: no
Uptime: 2d
Temperatures: CPU 55.2 °C / WL0 45.5 °C
Satus: Working (SFE, QOS, VAP/br1, Privoxy, Samba)
Issues/Workarounds:
Startup command for 2.4 VAP
wlconf eth1 down
wlconf eth1 up
If modem is rebooted (or occasionally loses connection?), no clients can access internet. Pressing apply settings in router lets all devices access internet again.