[kernel-panic69]

[WARNING]: This thread is for reporting feedback for the benefit of the developers and the community. Please state your hardware model & version, mode(s), and specific firmware image used (e.g. dd-wrt.v24-00000_NEWD-2_K2.6_mega-nv60k.bin). Please avoid discussions or asking questions, this thread is not meant for support: Please open a new thread if you have questions or need help resolving issues. Failure to follow these simple rules may result in your posts being moved or deleted. DO NOT flash this beta release if you do not understand the risks and know your specific device recovery methods.

Downloads: (if a link does not work, try another) DD-WRT website HTTPS & FTP

CLI Flash: 'cd /tmp' then 'wget {file URL}' (or 'curl -k {file URL} -o {file}') with http (not https) or ftp. Then 'write {file} linux'.

Changelogs: SVN changelog since last build: r42914
*Github mirror: https://github.com/mirror/dd-wrt/

Important: BEFORE reporting any issues, reset and manually setup (no nvram backup).
Provide applicable info (GUI syslog, `dmesg`, `cat /var/log/messages`, etc.) including "iptables" info for firewall issues (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file). Search SVN tickets prior to opening a new one.

Notes:

1. Use build 41664 or newer to incorporate: SFE accelerated NAT (k3.2+), KRACK (k24+), PBR+SFE, CAKE & FQ_CODEL_FAST (reset first!), GTK Rekey (radio timer) fixes
   
2. Reset button was broken in 40571; fixed in build 40750.
   
3. CVE-2019-14899 VPN fix from December, and GUI toggle: Since then various revisions including recently 7040. Ref: tickets 6920, 6928, 6931, and 6932
   
4. In-kernel Samba has been implemented this year and default min/max versions have changed, with WSD support.
   
5. VAP issue is fixed! For any Wireless Mode, create a VAP and both ath0/ath1 should now function properly.
   
6. WireGuard! New GUI Tunnel options have appeared since r42872, script no longer required!
   

Issues, observations, and/or workarounds reported:

1. DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use (without entware): 6246
   
2. There are remaining issues for Samba (for example NTFS), with frequent updates.

Template example to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):

[kodtaku]

Router/Version: Linksys WRT3200ACM
File: DD-WRT v3.0-r42926 std (04/18/20)
Previous: DD-WRT v3.0-r42910 std (04/15/20)
Reset: No
Kernel: Linux 4.9.219 #1750 SMP Sat Apr 18 11:31:55 +03 2020 armv7l
Mode: gateway
Status: Running as expected

5GHz wpa2
2.5GHz wpa2
NAS using usb samba

Only weird thing on 42926 5GHz didn't come up. Went back to 42910 still didn't come up so gave 42926 another try - at this point the 5GHz did come up.

[scar1943]

WRT3200ACM V1 r42926 Firefox 75.0 (64-bit) webflash

OpenVPN CLIENT seems fine (nordvpn server)
5GHz wpa2 CCMP-128 (AES) Seems fine 40MHz N
2.4GHz wpa2 CCMP-128 (AES) Seems fine 20MHz N
NAS via USB Samba Conditional

The old bug of asking for credentials when they don't exist still happening.

[WENED]

WRT3200acm r42910 -> r42926 (actual Build on GUI)

Same as previous builds if Ath2 is enabled it disappears from the Wireless Setup and stops working. Otherwise watching for any other hiccups.

[NBA Jam]

Unbound seems to be broken in this build. I tried 42910 and found the same issue. I reverted back to 42335 and Unbound is working again.

Router/Version: WRT1900ACv1
File: ddwrt-linksys-wrt1900ac-webflash.bin
Previous: 42335
Reset: No
Kernel: 4.9.213 #1594 SMP Mon Feb 10 03:31:06 +03 2020 armv7l
Mode: Gateway
Status: Unstable with Unbound. All other functions working as expected.
Issues / Errors: Unbound will not start

I'v got a little script to reload unbound and it returns a PID when unbound loads successfully. 42910 and this build both do not return PIDs. DNS will not work until recursive DNS is disabled in the GUI.

[BrainSlayer]

unbound is not broken. but you are using a custom config. so take care that its still compatible with latest unbound version

[PIZZEDMEOFF]

I flashed this when it was posted and then left, So this build is doing good no wireless mishaps or nothing for me so far, I still have not attempted no more VAPS while bridged since my alternet method has been working just fine ( old wrt54gs-v5 for 2.4ghz access )

[WENED]

WRT3200acm r42910 -> r42926 upgraded well but WDS on 5Ghz would not connect even with VAP off on the remote. Master 3200 still running r42926 without problem.
Went in on 2.4Ghz and switched parts to go back to r42910.All is working again.

[BrainSlayer]

[NBA Jam]

[WENED]

[SurprisedItWorks]

I finally updated my WRT1900ACSv2 client-mode travel router from 41954 to 42926 (filed under 42925 at the download sites) using the command-line approach. The key write SomeFilename linux command that does the flashing initially returned this:

usage: write [path] [device]
Command exited with non-zero status 234
time to flash: 0.00 seconds

No idea why. Repeating the command worked fine:

flash : boot partiton is 2
flash : flash to partition linux
flash : Flash is NAND
flash : freeram=[404905984] bufferram=[6569984]
flash : The free memory is enough, writing image once.
flash : linux: CRC OK (0x446AA7B5)
flash : Writing image to flash, waiting a moment...
flash : Flash is NAND
flash : erase[41943040]
flash : write block [37486592] at [0x023C0000]
done [37617664]

The only syslog surprises:

Dec 31 19:00:17 user.info wsdd2[1431]: starting.
Dec 31 19:00:17 user.info : smbd : samba started
Dec 31 19:00:17 user.err wsdd2[1431]: cannot read netbios name from testparm
Dec 31 19:00:17 user.err wsdd2[1431]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Dec 31 19:00:17 user.err wsdd2[1431]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Dec 31 19:00:17 user.err wsdd2[1431]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
...
Apr 24 12:15:13 user.info : wsdd2 : windows service discovery daemon successfully stopped
Apr 24 12:15:13 user.err wsdd2[1431]: Terminated received.
Apr 24 12:15:13 user.info wsdd2[1431]: terminating.
Apr 24 12:15:13 user.info : ksmbd.mountd : samba daemon successfully stopped
Apr 24 12:15:13 kern.info kernel: [ 56.646664] ksmbd: shutting down ksmbd
Apr 24 12:15:13 user.info wsdd2[2202]: starting.
Apr 24 12:15:13 user.info : smbd : samba started
Apr 24 12:15:13 user.err wsdd2[2202]: cannot read netbios name from testparm

I have no idea what any of that means. (I'm not a Windows person.)

Samba seems fine in my application (mounting/using a share from a linux machine). Restarting samba in Startup appears no longer necessary.

The OpenVPN client (OpenVPN 2.4.9 with OpenSSL 1.1.1e) connects fine but with a couple of mysteries in the vpn log. This log line

ip: command line is not complete, try "help"

near the end turns out to be from a harmless bug in route-up.sh and is in the queue to get fixed. There were also a few lines about shell variable $route_netmask_1 not existing. This turns out to be due to an error in iptables commands in route-up.sh and route-down.sh, which I hacked a patch to fix by creating a script up.sh to edit those route-*.sh scripts to replace $route_netmask_1 with $ifconfig_netmask and adding an "up" command to the VPN additional config to point to the script. Without some sort of fix, the iptables -t raw -I PREROUTING ... command fails to install the intended rule. This is the rule that drops packets from other interfaces (i.e. not tun1) to tunnel addresses. Most people will never notice that it's missing, and my understanding is that it has already been fixed in later builds.

If Apply is used from the OpenVPN GUI page, the vpn log mysteriously gains a variable number of lines like ip: RTNETLINK answers: File exists just before the irrelevant (because I use keys instead of a user/pass) WARNING: this configuration may cache passwords in memory... and the very relevant Initialization Sequence Completed. The number of copies of this RNETLINK message varies. I've seen between six and eight. If Apply is tried a second time, the openvpn process dies. If Apply is tried a third time, things work again but again with the RNETLINK lines. Again and it dies. So a loop. If when the process dies I just run openvpn --daemon --config /tmp/openvpncl/openvpn.conf by hand, I again get the RNETLINK version of things in the log. So I'm considering OpenVPN Apply to be broken (it was broken all through fall of 2019 as well) and will reboot after changing anything. This whole problem could be unique to my config, or not. I tried to sort that out but ran out of energy and failed.

Update June 6, 2020: I now have 42926 running on four WRT1900ACSv2 routers, one in Client Mode and three in Gateway mode, the latter including one that has run fine for over a week and that now is supporting 18 clients. All were updated from the command line: write blahblah linux.

The overabundance of hostapd deauthentications of builds from a few months ago is gone. DHCP seems (mostly... see below) clean. DNS using two DNSCrypt providers appears flawless. The two or three VAPs (different routers) run smoothly. Wifi speeds (NG-Mixed HT40SGI on 2.4G, AC/N-Mixed VHT80SGI on 5G) are great. VLANs (swconfig) are fine. The OpenVPN client (AirVPN) is doing its job. The one router using USB/SMB has no trouble with it. No SFE, QoS, IPv6, or port forwarding is used.

Two problems have appeared, ones that may have been present for awhile (maybe a long while) without me noticing:

• The trivial one: The GUI styles named for colors do not work.
  
• The nontrivial one: some wifi clients connect so quickly after boot that DHCP leases them IP addresses before NTP time is up. When NTP does get the time, dd-wrt thinks the leases are long expired and forgets about them. The clients believe they still have valid leases, so GUI Status shows their wifi connections with no corresponding DHCP leases. I have not caught dnsmasq in the act of creating an IP-address conflict by reassigning the forgotten IPs, but how could it not happen now and then? Workaround: use a short DHCP lease time so that following an overnight boot, new leases are assigned before users are awake and apt to notice trouble. Longer term though, would it perhaps be a good idea to hold off on starting DHCP services until time is set? (This is way beyond my competence.)

[simo955]

Updated and the speed on 2.4G is up to 15mbps ( from 500+)
Wireless Network Mode: mixed
Channel Width: full 20
WPA2 Personal; CCMP-128 (AES)
I have reset the router after updating to be sure that the setting are ok.
The problem is only on 2.4G