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. _________________ #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
Last edited by jwh7 on Tue May 21, 2019 0:31; edited 1 time in total
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Mon May 20, 2019 21:33 Post subject:
Yep, pretty much moot to flash this one, but folks with 4.4 kernels may wish to, if I remember the commits right. I think Broadcom-ARM are the only devices to benefit flashing this or 39825.
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r39827 std (05/20/19)
Kernel: Linux 4.4.180 #74 SMP PREEMPT Mon May 20 07:32:28 CEST 2019 armv7l
Previous: r39825
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working so far.
Uptime: 19m
Temperatures: CPU 73.0 °C / WL0 50.0 °C / WL1 55.6 °C
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: DD-WRT v3.0-r39827 std (05/20/19 Kernel: Linux 4.4.180 #74 SMP PREEMPT Mon May 20 07:32:28 CEST 2019 armv7l Previous: BSr39572 Mode/Status: Gateway / WIFI = AP / Seems ok CPU overclocked to 1400mhz from default 800mhz via r33006 Reset: Yes Issues/Errors: Seems ok UpTime: 1:14m
What i have noticed:-
1) This message is in yellow:-
May 21 17:01:29 FluCruM kern.warn kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module.
Router/Version: ASUS RT-AC3200 File: asus_rt-ac3200-firmware.trx Kernel:
Linux 4.4.180 #79 SMP PREEMPT Mon May 20 08:02:09 CEST 2019 armv7l Mode: Gateway Status: Firmware would NOT accept previous firmware was r39800. Tried to us CLI to flash also would not accept. Ended up rebooting, but it went to boot loop. Got the router to CFE and flash DD-WRT v3.0-r39827 std (05/20/19)
It's only been 10mins. Will keep an eye out.
VAP seems to be fine now for the AC3200. All my VAP came back up and verified connectable
Also still getting the 'ghost' usage (Load avg is super high, but the system is actually at idle)
killing httpd does stop it though. Need a fix for this! _________________ ASUS RT-AC3200 - Deployed Client's site
ASUS RT-AC5200 - Merlin
ASUS RT-AX88U - Merlin
Last edited by mbze430 on Wed May 22, 2019 17:53; edited 2 times in total
I updated to this firmware because I wanted to use DNSCrypt-Proxy on the router since I literally had to set up a VM to get DNSCrypt-Proxy running.
However I couldn't find a place to enable it in the GUI
So what is up with that? I have seen a post back in 2017 that had it in the DDWRT GUI.
I know the 'dnscrypt-proxy' is in the firmware now.
Code:
root@ddwrt-ac3200:~# dnscrypt-proxy
Wed May 22 09:48:43 2019 [ERROR] Error: no resolver name given, no configuration file either.
Wed May 22 09:48:43 2019 [ERROR] The easiest way to get started is to edit the example configuration file
Wed May 22 09:48:43 2019 [ERROR] and to append the full path to that file to the dnscrypt-proxy command.
Wed May 22 09:48:43 2019 [ERROR] Example: dnscrypt-proxy /usr/local/etc/dnscrypt-proxy.conf
Wed May 22 09:48:43 2019 [ERROR] The local list of public resolvers is loaded from: [/usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv]
Wed May 22 09:48:43 2019 [ERROR] Consult https://dnscrypt.org for more information about dnscrypt-proxy.
_________________ ASUS RT-AC3200 - Deployed Client's site
ASUS RT-AC5200 - Merlin
ASUS RT-AX88U - Merlin
Updated from dd-wrt.v24-39825_NEWD-2_K3.x-big-RT-N66U.trx through the GUI on my ASUS N66U without wiping the settings.
Router ended up semi busted, unable to reach the GUI and rebooting every 10 seconds or so.
Ultimately ended up connecting a cheap CH340 USB/serial adapter and recovering with curl:
The built-in CFE miniserver has saved my bacon quite a few times; but always takes a good 15 minutes or so for the process to finish.
The changelog doesn't seem vastly different, all the recent versions have been working well so perhaps I was just unlucky.
The built-in CFE miniserver has saved my bacon quite a few times; but always takes a good 15 minutes or so for the process to finish.
The changelog doesn't seem vastly different, all the recent versions have been working well so perhaps I was just unlucky.
It's not just you -- the same thing happened to my RT-N66U when I tried to upgrade after an NVRAM reset.