Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 and newer 2. krack fixes for Broadcom were completed in r33678, 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 Issue #4 below).
4.R6400v2 support added in r36811-36818, 36825, and 36826. R6700v3 support added in r36828-36840.
Issues, observations, and/or workarounds reported: 1. (egc) Policy-Based Routing broken if SFE enabled: 5900 quarkysg's PBR+SFE fix: 5986 2.Trendnet 81*DRU models are missing factory-to-flash 3.DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:6246 4.WDS does not work on ARM devices (only MIPS<->MIPS) 5.VAPs not working at boot (k3.10?); workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
6.K2.6 builds are broken since 38253(?); GUI issues:6538
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-r38581 std (02/06/19)
Kernel: Linux 4.4.173-rc1 #4633 SMP Wed Feb 6 06:44:52 CET 2019 armv7l
Previous: r38570
Mode/Status: Gateway / working
Reset: no
Issues/Errors: No issues so far.
Uptime: 26m
Temperatures: CPU 66.4 °C / WL0 49.3 °C / WL1 53.0 °C
Router/Version: Asus RT-N66U
File: dd-wrt.v24-38581_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r38581M big (02/06/19)
Kernel: Linux 3.10.108-d8 #22821 Wed Feb 6 14:21:26 CET 2019 mips
Mode: Gateway, Wifi disabled
Reset: No
Status: working as intended, uptime 4h
Router/Version: Asus RT-N12D1
File: dd-wrt.v24-38581_NEWD-2_K3.x_mega_RT-N12B1.trx (D1 revision uses same HW as B1)
Firmware: DD-WRT v3.0-r38581M mega (02/06/19)
Kernel: Linux 3.10.108-d8 #22825 Wed Feb 6 14:27:21 CET 2019 mips
Mode: Gateway/AP, connected via WAN to N66U
Reset: No
Status: working as intended, uptime 4h
Router/Version: E3000
File:ftp://ftp.dd-wrt.com/betas/2019/02-06-2019-r38581/broadcom_K3X/dd-wrt.v24-38581_NEWD-2_K3.x_mega-e3000.bin Firmware: DD-WRT v3.0-r38581M big (02/06/19)
Kernel: Linux 3.10.108-d8 #22825 Wed Feb 6 14:27:21 CET 2019 mips
Mode: Gateway, Wifi enabled
Reset: Yes
Status: working, ill revise time here in a bit, so far 10 mins. Careful on upgrading to this when I was upgrading from jan build it didn't reboot by itself after taking the update file.
Update: Been running for a few hours did have a hiccup when I had samba going and transferring some files to a flash drive.. it caused the Webui to crash. However reboot and havent had any problems since. A lot more stable than the jan build I was running.
Joined: 29 Nov 2013 Posts: 36 Location: Düsseldorf, Germany
Posted: Wed Feb 27, 2019 21:41 Post subject: ASUS RT-N66U
Router/Version: ASUS RT N66U
File: dd-wrt.v24-38581_NEWD-2_K3.x-big-RT-N66U.trx
Kernel: Linux 3.10.108-d8 #22821 Wed Feb 6 14:21:26 CET 2019 mips
Mode: Gateway
Status: Errors
Since i updated from 33555, i flashed with reset.
I do not use anything special except Privoxy in transparent mode and Tor.
After 6 days, i saw that httpd was running amok, causing an average load of 2. I just killed it, but it is restarted automatically, and soon after accessing the web page, it uses 100% CPU again (probably related to changeset/38938).
In the dmesg protocol, there are messages complaining about "br0: received packet on eth1 with own address as source address".
