[blkt]

[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and device specific recovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.

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

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'.

Repository: Trac SVN changelog since last build r46836 (GitHub mirror)

Notes:
• OpenVPN 2.5.2: Guides, Server, PBR, Reverse PBR, Client (see second post), Kill Switch, update tips, scripts and more.
• WireGuard 1.0.20210219/Tools: Guides, Client, Server, Advanced, PBR, KS, update tips, scripts & more. Thanks BS & egc!
• CVE-2019-14899 VPN fix (applicability depends on VPN setup) and GUI toggle since r41813.
• SmartDNS • MiniDLNA • Unbound 1.13.1 • CoovaChilli 1.6 • Tor 0.4.5.8 • OpenSSL 1.1.1k • Dnsmasq 2.85 • Privoxy 3.0.32
• In-kernel Samba (ksmbd 3.3.9+): default min/max versions changed. • WSD update • ANTFS/NTFS3 kernel mode driver++.
• CVE-2020-26147, CVE-2020-24586, CVE-2020-24587 & CVE-2020-24588 (Fragattack) fixed.
• "Assign WAN port to Switch" feature removed to be reworked in future release: 46782

Issues:
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!

Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.

Example Template:

[Monza]

Upgraded WRT1200AC v1's from r46836 to r46854 using Brave 1.10.97 (64-bit) running on Linux Mint 20.1 OS hardwired via Cat6.

Successful update and reboot. No reset, nothing disabled prior to update, uptime approx 4+ hrs, wired/wireless connected, vpn up immediately (Expressvpn). I do not use NAS. SFE, QoS and IPv6 are always disabled. OpenVPN client/DNSMasq and radios always enabled. I do not have any Apple devices.

Kernel Version Linux 4.9.269 #2640 SMP Thu Jun 3 00:54:03 +07 2021 armv7l

No issues with a routine update session.

Two reds in syslog that I have not seen in a while but with no apparent affect on funtions :
Jun 3 15:11:10 router daemon.err openvpn[1730]: FRAG TTL expired i=19
Jun 3 15:11:36 router daemon.err openvpn[1730]: FRAG TTL expired i=9

[pbphoto]

Flashed my 1900ACSv1 via CLI from 44048. I did not reset to factory defaults this time. No issues with the upgrade.

Linksys WRT1900ACS
wlan0 - AC/N mixed, channel 149 upper, 40mhz, WPA2-personal AES.
wlan1 - NG mixed, channel 11, 20mhz, WPA2-personal AES

Primary clients used for testing:
iPhone SE 2020 - IOS 14.6
Macbook Pro 2018 - macos 11.4
Other Apple and non-apple devices

I tried the changes recommended by justanotherbrokenrouter in build 46816:
5GHz 40MHz Mixed channel 100 Upper (WPA2 CCMP-128 (AES) Only) <-- I did ac/n mixed, not mixed, but it doesn't seem to fucking matter
U-APSD (Automatic Power Save) Disabled
Single User Beamforming Disabled
Multi User Beamforming Disabled

I also put the ng-mixed fix in for basic rates on the 2.4ghz in the wifi security custom config box:
basic_rates=60 120 240
supported_rates=60 90 120 180 240 360 480 540

Problem #1: This build ran for about 40 minutes before my Macbook wifi hung up while I was doing my real job. recycling the wifi on the mac temporarily fixes it but it happened several more times. This problem started happening 10 months ago with 44085. Wifi remains connected but traffic stops flowing. The first time it happened was at 15:54 in the logs and dmesg attached.

Problem #2 - Several process dumps - same signature as with build 46750 and after. This time it dumped 3 times - some even before my wifi hung up. Wifi functionality seemed normal afterwards, with the exception of problem #1

Problem #3: GUI is slow to respond - even with firefox. Then it will be snappy for a minute or two, then hang up again. Makes it tough to troubleshoot #1 and #2.

Went back to 44048 which is the last good marvell release if you have Apple devices (and possibly others) in your environment. Something broke starting with 44085. After reloading 44048 and restoring the 1900acsv1 from backup, it runs flawlessly. A couple hours later, a Netgear r7800 from ebay arrived and it replaced my 1900acsv1 in my network. There seems to be no appetite to fix these issues on the marvell platform - or even look at the logs and dmesgs I've been uploading for months. I've got two r7800s in my environment running 46854. I need to figure out what to do with my 3200ACM running 44048 and wireguard-it's cpu's can do 650-750 down and 550 up as a wireguard client - the r7800s don't come close.

Linksys WRT1900ACSv1: r44048 router operating mode, hardwired ethernet lan to a WRT3200ACM. WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel 11, WPA2-CCMP-128. 5ghz: AC/N mixed, 80mhz channel width, channel 149+upper, WPA2-CCMP-128.

Clients: Apple MACOS x 4, IOS x 4, Apple TV, Chromecast Audio x 2, Eufy doorbells, Lutron Caseta, Axis Camera, Samsung TV, Nest thermostat, EtekCity outlets (Espressif)..

[WENED]

All routers r46836 -> r46854 IE11 no reset

It appears that after I did the upgrade from the old builds r31924 on 1900's and r44048 on the 3200's to r46722 by doing a hard reset on both partitions and upgrading both first, that these current builds work great.
Obviously it is imperative that periodically a full reset is required to remove residuals. Not my favorite thing trying to re-enter all parameters manually, but the end result is worth all the pain.
I had tried reset before but never did both partitions which is what seems to be required, or at least that was my experience in getting these builds to function.
Conclusion; To facilitate these newer builds r44048+ a total reset is required on both partitions and upgrade on both to one of the more recent. I used to keep an older build on one partition for fallback but since I have copies of all builds I try and backups of each I can always fall back anyway. It appears that both partitions must be of similar build structure to avoid conflict.

[SurprisedItWorks]

Just a reminder: Our WRT routers have two firmware partitions but a shared nvram configuration partition. The hard reset resets the latter to defaults for the build in the firmware partition currently in use. So you can't really "reset them both" unless both firmware partitions contain the same build. Even then, you are resetting just one configuration partition. The question is what you are resetting it to.

[WENED]

SurpisedItWorks,

That's what I've always thought as you indicated. However because I have had so much trouble with trying to get new builds working, especially with my 1900V1's I probably overkilled. But the bottom line is it worked and the new builds are performing admirably.
As for reset, what I did was upgrade from current build to one of the newer builds with reset. Upon reboot into the new build (default status) I hit the red reset to ensure a full reset, once back into the newer build I upgraded again to load the other partition with reset and did the same red button reset after reboot. I then would enter all my parameters, a real pain in the butt for my master, following which I would do another upgrade this time without reset to load up the other partition.
As I said, overkill but dam it is the first time in years that I have been able to upgrade any of my 1900 V1's and have them work correctly.

[Justanotherbrokenrouter]

[jifffy]

This is my Linksys 3200acm with linux version Linux 4.9.269 #2640 SMP Thu Jun 3 00:54:03 +07 2021 armv7l, Firmware version DD-WRT v3.0-r46854 std (06/03/21). The update process went ok, using my Linux machine, Firefox. I can no longer administer the 3200acm using my Macbook, ever since that Macbook firmware release, in fact my Macbook is very iffy meaning pages take forever to load, sometimes I have to reload them a few times to take. I keep hoping that Apple will release a fix to this issue but I fear my plead goes on deaf ears. Everything else works good, on my Windows machine, no issues. I have pihole installed which works good too.

[Justanotherbrokenrouter]

[pbphoto]

Router: Linksys 3200ACM r46854

Kernel: Linux router1 4.9.269 #2640 SMP Thu Jun 3 00:54:03 +07 2021 armv7l DD-WRT

I've got some good news. After unsuccessfully trying to get my 1900ACS to work with any build since 44048 (see problems above), I removed it from service and replaced it with another r7800 which is working great with 46854. However, I still had my main gateway 3200ACM running 44048 (and 44970 on partition-2) to deal with. I hadn't tried to upgrade this since 44970 - it was running great on 44048.

Following justanotherbrokenrouter's advice with my 3200ACM, I reset the shit out of this thing - multiple resets on both partitions (using GUI, CLI, and reset button), multiple power-cycles, then I loaded 46854 on both partitions and reset the shit out of it again many times. Finally, after about 90 minutes of giving this thing a lobotomy, I manually typed my configuration back in from scratch. 32 hours of uptime later, and it is running without any hiccups.

I also made some updates to my wifi settings when retyping everything in, but nothing I haven't tried before for months on my 1900ACS. Hell I even went back to stock linksys firmware on my 1900ACS and it didn't help. But maybe all the resets and getting both partitions up to the same code level and reseting again did the trick this time on my 3200ACM. I was also wearing my lucky shirt. Wifi settings attached for anybody who is interested.

The only two issues are:
1) GUI can be painfully slow at times. Opening a telnet also freezes when GUI is acting up - no prompt.
2) These are the only messages being repeated in dmesg. I haven't seen these in a while so maybe it's a sign this build is actually working well with mobile clients.
[107832.782641] ieee80211 phy0: staid 4 deleted
[109301.455457] ieee80211 phy0: staid 2 deleted
[115772.690914] ieee80211 phy0: staid 1 deleted
[116329.870036] ieee80211 phy0: staid 2 deleted
[116333.953205] ieee80211 phy0: staid 6 deleted
[117246.492578] ieee80211 phy0: staid 4 deleted

Linksys WRT3200ACM: gateway mode, DNSMasq for DNS and DHCP, Wireguard client (Mullvad), Firewall enabled, QoS enabled HTB-CAKE, PBR enabled (SFE disabled). WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel 1, WPA2-CCMP-128. 5ghz: AC/N mixed, 80mhz channel width, channel 36+upper, WPA2-CCMP-128.

Linksys WRT1900ACSv1: TEMPORARILY REMOVED FROM SERVICE - router mode, hardwired ethernet lan to WRT3200ACM above. WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel 11, WPA2-CCMP-128. 5ghz: AC/N mixed, 80mhz channel width, channel 149+upper, WPA2-CCMP-128.

Two Netgear r7800s - one replaced the 1900ACS listed above, and the other is an additional WAP on my network configured identically to the 1900ACS, just different wifi channels.

Clients: Apple MACOS x 4, IOS x 4, Apple TV, Chromecast Audio x 2, Eufy doorbells, Lutron Caseta, Axis Camera, Samsung TV, Nest thermostat, EtekCity outlets (Espressif), BlueSound/BlueOS devices...

UPDATE: After running for a week, I have had a couple of wifi-freezes on a couple different iPhones (IOS 14.6), and today I had the first wifi-freeze on my macbook (11.4) about an hour into a Zoom call with my laptop sitting two feet from the 3200ACM. Wifi remained connected but traffic stopped flowing. Recycling wifi on my macbook fixed the problem. Still, I consider this a major improvement over the releases after 44048 where I had iphones and macbooks constantly hanging- not sure if there was some sort of fix in the code (doubtful) or reseting the crap out of the router did the trick? I'm at the same code level on two Netgear r7800 AP's in my environment and they don't appear to have this problem. I'm willing to live with it on my 3200ACM because it is my gateway and I can get 750mbit down and 550mbit up with Wireguard. Maybe someday I'll reset the crap out of my 1900ACS and see if I can put it back into the environment.

[WENED]

I have noted this a few times already, but overkill on resets and having both partitions with similar builds seems to be the key to getting around the problems associated with builds after R44048 or in my case getting my 1900 V1's to run on anything else other than r31924.
It has been a couple of weeks now since I did the massive resetting and configuration and have upgraded a couple of times without incident.
Interestingly though one thing I did notice was that even though I did multiple resets (red button) and GUI resets my WDS configurations (WDS Links) remained in memory. I can only assume that I should be Telnet into the routers I want to reset and clear NVRAM as the resets do not completely clear everything.
This however did not cause any problems was actually a blessing since I didn't have to re-enter all the MAC addresses again.
I do suspect that clearing ram is not the issue, but possibly having incompatible builds on alternate partitions. Something for the master GURU's to work out as for upgrade procedures.

[Justanotherbrokenrouter]

[WENED]

Justanotherbrokenroute,

Just upped all routers to r46885 from 46854 using IE11, no reset. All came up well including VPN. The massive overkill I did at r46750 seems to have eliminated any problems with these new builds.