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.
Tickets closed as 'fixed' (Broadcom-related and general):
*6389: "Netgear R6400v2 incorrectly detected as R7000P + proposed fix"
*6435 "tcpdump egress capture issue caused by linux kernel" [k3.18+]
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 Wed Sep 19, 2018 17:08; edited 4 times in total
Posted: Wed Sep 19, 2018 15:35 Post subject: R6400v2 with board xxx30
I have a Netgear R6400v2 with board xxx30. Had issues with many builds and so far Kong's 36820 and 36840 seem to be the only options. All other builds recognize this router (wrongly) as R7000P - and disallow any upgrade to other software (dd-wrt or stock).
Does this build include the changes necessary for the R6400v2 with board xxx30? If yes - I would like to try this out.
Posted: Wed Sep 19, 2018 16:03 Post subject: Re: R6400v2 with board xxx30
@m0eb@ wrote:
I have a Netgear R6400v2 with board xxx30. Had issues with many builds and so far Kong's 36820 and 36840 seem to be the only options. All other builds recognize this router (wrongly) as R7000P - and disallow any upgrade to other software (dd-wrt or stock).
Does this build include the changes necessary for the R6400v2 with board xxx30? If yes - I would like to try this out.
Yes, Kong added it to the main SVN in r36811-36818, 36825, and 36826. And since I'm here, he also added R6700v3 support in r36828-36840. See: https://svn.dd-wrt.com/ticket/6389
I'll add this to the OP. _________________ #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: Netgear R7000
Firmware: DD-WRT v3.0-r36995 std ( 09/19/18 )
Kernel: Linux 4.4.157-rc1 #3874 SMP Tue Sep 18 13:49:25 CEST 2018 armv7l
Previous: r36808M
Mode/Status: Gateway / working
Reset: no (then yes)
Issues/Errors: None so far, but upgrade continues to fail via web UI (web GUI becomes unresponsive, but the router and wireless continue to function, a reboot restores web GUI). After the last failed upgrade, I did a full reset and manual reconfig and hoped it would help this time. It didn't. I've seen other people reporting this issue. Is there a known fix for this? If not, is there a way to confirm the devs are aware and working on a fix?
Uptime: 26 minutes
Temperatures: CPU 67.5 °C / WL0 49.5 °C / WL1 51.0 °C
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r36995 std (09/19/18 )
Kernel: Linux 4.4.157-rc1 #3878 Wed Sep 19 08:32:36 CEST 2018 armv7l
Previous: r36645
Reset: No
Mode/Status: gateway ap/working
Issues/Errors: see below.
Spam in syslog.
Sep 19 18:19:26 router daemon.err httpd[1096]: Request Error Code 404: File favicon.ico not found.
Sep 19 18:29:49 router daemon.err httpd[1096]: Request Error Code 404: File favicon.ico not found.
Sep 19 18:29:58 router daemon.err httpd[1096]: Request Error Code 404: File favicon.ico not found.
Sep 19 18:37:51 router daemon.err httpd[1096]: Request Error Code 404: File favicon.ico not found.
Sep 19 20:56:09 router daemon.info httpd[1096]: httpd : Authentication fail
Sep 19 20:56:09 router daemon.err httpd[1096]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Also noticed when unbound (recursive DNS resolving) is enabled this test https://www.grc.com/dns/dns.htm does not return my WAN address as DNS server anymore. No results whatsoever. I wonder what changes have been made to unbound and is this normal behaviour?
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r36995 std (09/19/18 )
Kernel: Linux 4.4.157-rc1 #3878 Wed Sep 19 08:32:36 CEST 2018 armv7l
Previous: r36645
Reset: No
Mode/Status: gateway ap/working
Issues/Errors: see below.
Spam in syslog.
Sep 19 18:19:26 router daemon.err httpd[1096]: Request Error Code 404: File favicon.ico not found.
Sep 19 18:29:49 router daemon.err httpd[1096]: Request Error Code 404: File favicon.ico not found.
Sep 19 18:29:58 router daemon.err httpd[1096]: Request Error Code 404: File favicon.ico not found.
Sep 19 18:37:51 router daemon.err httpd[1096]: Request Error Code 404: File favicon.ico not found.
Sep 19 20:56:09 router daemon.info httpd[1096]: httpd : Authentication fail
Sep 19 20:56:09 router daemon.err httpd[1096]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Also noticed when unbound (recursive DNS resolving) is enabled this test https://www.grc.com/dns/dns.htm does not return my WAN address as DNS server anymore. No results whatsoever. I wonder what changes have been made to unbound and is this normal behaviour?
do you see any of these Wan issues of 36645 and 36808 (after reboot losing connection need to restart DNS masking to get it back-Transmission stopped working) in this version? or it has been fixed.
do you see any of these Wan issues of 36645 and 36808 (after reboot losing connection need to restart DNS masking to get it back-Transmission stopped working) in this version? or it has been fixed.
My connection has always came back after reboot without any issues. I did not catch your question.
do you see any of these Wan issues of 36645 and 36808 (after reboot losing connection need to restart DNS masking to get it back-Transmission stopped working) in this version? or it has been fixed.
My connection has always came back after reboot without any issues. I did not catch your question.
Mine few times got a connection after reboot, had to restart dns masking (untick, save and apply settings, tick,save and apply settings) to get it back, but after this was impossible to have transmission, i dont know why, but only the few times i got connection without the trick after reboot, transmission worked, most times after rebood had to do the trick, and transmission bugged. my connectios is PPOE, maybe only PPOE connections was bugged.
Joined: 08 May 2018 Posts: 14243 Location: Texas, USA
Posted: Thu Sep 20, 2018 14:28 Post subject: E4200v1
Router/Version: Linksys E4200 v1
Firmware: DD-WRT v3.0-r36995 mega ( 09/19/18 )
Kernel: Linux 3.10.108-d5 #20942 Wed Sep 19 14:41:21 CEST 2018 mips
Previous: DD-WRT v3.0-r36808 mega ( 08/30/18 )
Firmware file used: dd-wrt.v24-36995_NEWD-2_K3.x_mega-e4200.bin
Reset: No
Mode: Gateway/AP
Uptime: ~22:15
Status: OK
Issues/Errors: No new errors, same error messages as last build. I didn't do a reset because I'm pretty sure the new WPA3 implementations are not in the build for this device, there are no options for them in the WebUI. No logs provided, nothing new to see.
Router: Netgear R7000
Firmware: DD-WRT v3.0-r36995 std (09/19/2018)
Kernel Version : Linux 4.4.157-rc1 #3874 SMP Tue Sep 18 13:49:25 CEST 2018 armv7l
Status: Working
Reset: No
Previous: 36840M
Errors: No
Temperatures : CPU 56.9 °C / WL0 48.8 °C / WL1 50.9 °C
Working very well :
Router mode : DHCP
SFE Enable STP Enable
DNSMasq
Encrypt DNS
Cache DNSSEC data
Validate DNS Replies (DNSSEC)
Local DNS
No DNS Rebind
Query DNS in Strict Order
Usb
Nas, Samba, JFFS2, MiniDLNA
wl0, wl1
Vpn (OpenVPN Client) library versions: OpenSSL 1.1.1 11 Sep 2018
Posted: Thu Sep 20, 2018 14:38 Post subject: Re: R6400v2 with board xxx30
jwh7 wrote:
Yes, Kong added it to the main SVN in r36811-36818, 36825, and 36826. And since I'm here, he also added R6700v3 support in r36828-36840. See: https://svn.dd-wrt.com/ticket/6389
I'll add this to the OP.
Thanks.
Router/Version: R6400v2 with board xxx30
Recognized as: Netgear R6400 v2
Loading Method: Direct upgrade from 36840 via web-interface without reset
File Used: netgear-r6400v2-webflash.bin
Firmware Version: DD-WRT v3.0-r36995 std (09/19/18 )
Kernel: Linux 4.4.157-rc1 #3874 SMP Tue Sep 18 13:49:25 CEST 2018 armv7l
Mode: Gateway (my only router for home use)
Status: OK
Other Comments:
1. VPN continues to function normally on 5GHz channel
2. OpenDNS continues to work on 2.4 GHz channel
3. Policy-based VPN works as normal
4. Every firewall check gives an error sh: eval: line 1: syntax error: unexpected "("
... please pardon my daftness with scripting. (I never tested my copy/paste firewall with any build earlier)
4. 5GHz and 2.4GHz signals show up on WiFi Analyzer with usual strengths. (to be checked over time and any difficulties edited below. Rock steady for past 1 hour)
At first impression, I see no difference in functioning as compared to earlier build. Let me know if I should check anything specific for reporting.
(This is the first build with WiFi SpeedChecker that works for R6400v2)
ADDED LATER: Please immediately correct the official page for recommended builds for the R6400v2. It still shows several incompatible builds - the only plus point of which has been to make me somewhat of an expert in unbricking the R6400v2. Many users come here out of trust - and I believe trust is an important factor for all dd-wrt well-wishers ... it's unfair to breach their faith and cause their routers not to work
