Posted: Wed Mar 31, 2021 10:42 Post subject: New Build - 03/31/2021 - r46220
[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 specificrecovery 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.
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.
Router/Version: Linksys WRT1900ACS v2
File: ddwrt-linksys-wrt1900acsv2-webflash.bin
Firmware: DD-WRT v3.0-r46220 std (03/31/21) (prev. DD-WRT v3.0-46069 std (03/17/2021))
Kernel: Linux 4.9.264 #2521 SMP Wed Mar 31 00:13:03 +07 2021 armv7l
Mode: Gateway, 2.4GHz, 5GHz and guests wifi, OpenVPN, NAS
Status: 15 min, load average 0.00, 0.00, 0.00, Temperatures CPU 76.5 °C / WL0 48.0 °C / WL1 49.8 °C.
I tried all three firmware from 46069 to 46220 (r46130, r46166 and r46177), and all of them something broken resulting in hang down of wireless connection.
Hope this one will be a good one, but I see CPU temperature too high, not good.
Upgraded WRT1200AC v1's from r46177 to r46220 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 3 hrs, wired/wireless connected, vpn up immediately (Expressvpn). I do not use NAS. SFE and IPv6 are always disabled. OpenVPN client/DNSMasq, QoS with PIE always enabled. I do not have any Apple devices.
Kernel Version Linux 4.9.264 #2521 SMP Wed Mar 31 00:13:03 +07 2021 armv7l
OpenVPN 2.5.1 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Mar 31 2021
library versions: OpenSSL 1.1.1k 25 Mar 2021 LZO 2.09
I am not sure what changed from build r44048 to r46220, but WiFi is now functional at this time.
At first I did Experience some hang time with wifi connection browsing the internet with my Note 9, but resolved after a couple of minutes.
Wifi Channel Quality strength is higher.
Have not noticed higher CPU temps.
WiFi speed test are slightly faster.
5GHz 40MHz Mixed 100 + 104 (5500) Upper (WPA2 CCMP-128 (AES) Only)
** Are the only changes from default
Advanced Settings
TX Power 30 dBm
Antenna Gain 0 dBi
**U-APSD (Automatic Power Save) Enabled**
(NEW) Disassoc Low Ack Disabled
Protection Mode None
RTS Threshold Disabled
Short Preamble Disabled
Short GI Enabled
**Single User Beamforming Enabled**
**Multi User Beamforming Enabled**
AP Isolation Disabled
Beacon Interval 100
DTIM Interval 2
WMM Support Enabled
Radar Detection Disabled
ScanList default
Sensitivity Range (ACK Timing) 500 (Default: 500 meters)
Max Associated Clients 256 (Default: 256 Clients)
Minimum Signal for authenticate -128
Minimum Signal for connection -128
Poll Time for signal lookup 10
Amount of allowed low signals 3
Other settings
Allow Channel Overlapping Disable
Router/Version: Linksys WRT1900ACS v2
File: ddwrt-linksys-wrt1900acsv2-webflash.bin
Firmware: DD-WRT v3.0-r46220 std (03/31/21) (prev. DD-WRT v3.0-r46177 std (03/26/21))
Kernel: Linux 4.9.264 #2521 SMP Wed Mar 31 00:13:03 +07 2021 armv7l
Mode: Gateway, 2.4G and 5G wifi, Wireguard for external access, WAN to 4G, Keep Alive reboot 6:02 in the morning
Reset: No
Status: Testing since yesterday, ok. load average 0.00, 0.00, 0.00, Temperatures CPU 71.7 °C / WL0 45.1 °C / WL1 46.8 °C.
So far everything is working solidly, including DNSSEC.
Will update if there's any issues. _________________ Router: Linksys WRT3200ACM WLAN0 and 1 have same SSID
88W8964 802.11ac WLAN0 Mode AP VHT80 80MHz Mixed Mode Channel and Extension Channel Auto Extension LL-6
88W8964 802.11ac WLAN1 Mode AP 20 MHz Mixed Mode Channel Auto
SD8887 802.11ac disabled but visible on GUI and CLI
TX Power 18 dBm
Antenna Gain 0 dBi
U-APSD (Automatic Power Save)Enabled
Protection Mode None
RTS Threshold Disabled
Short Preamble Disabled
Short GI Enabled
Single User Beamforming Enabled
Multi User Beamforming Enabled
AP Isolation Disabled
Beacon Interval 100
DTIM Interval 2
WMM Support Enabled
Radar Detection Disabled
ScanList default
Sensitivity Range (ACK Timing) 500 (Default: 500 meters)
Max Associated Clients 256 (Default: 256 Clients)
Minimum Signal for authenticate -128
Minimum Signal for connection -128
Poll Time for signal lookup 10
Amount of allowed low signals 3
Wireless security is WPA2 Personal CCMP-128 only
QAM256 is on
I am not sure what changed from build r44048 to r46220, but WiFi is now functional at this time.
At first I did Experience some hang time with wifi connection browsing the internet with my Note 9, but resolved after a couple of minutes.
Wifi Channel Quality strength is higher.
Have not noticed higher CPU temps.
WiFi speed test are slightly faster.
(...)
From my observations with previous builds (haven't tried this one yet), that "hang" always returns after disconnecting all devices for quite some time/idling long enough. I do agree everything else works better, but I just can't stand that "hang" (it absolutely destroys my workflow). I am effectively stuck in build r44048 ever since something changed in the wifi and I had to rollback, always reading these threads looking for that magical build that solves the issue. The Marvell driver development is dead, so I am not holding my breath. It's not like BS can just rollback whatever changed either, because some users will require at least part of the new changes to solve compatibility issues with ESP boards (IoT devices and such).
Keeping an older build r44048 is always a step-gap solution. We started the year with the public disclosure of new DNSmasq vulnerabilities, that range from "just" DNS poisoning to the potential of having full-blown RCE in our router. Build r44048 is now unpatched and ready to exploit (the possible mitigations are only partial and impact performance), so I am now pondering my next move. I'll likely try OpenWRT first just for kicks, I've had great success with that the last time DD-WRT gave me troubles.
I have been stuck with r44048 since it was released Due to my Galaxy Note 9 behaving poorly with the newer builds WiFi.
I would experience hang ups, and connection drops with every new build I tried. I would always have to revert back to r44048 as soon as any connection problems developed because it's the best known build for WiFi needs. Also my connection just idled for over 2 hours, just picked up right where I left off without a connection hang up, and I didn't have to reconnect my device to wifi before browsing to this site either. The hang up with internet browsing I mentioned in my first comment was due to me connecting my device to WiFi before the router had the chance to fully boot from a reboot after configuration changes. Disconnecting, and reconnecting WiFi is also without failure for now.
I usually do not make a comment on a build until I see significant improvements from the r44048 build. I'm not saying this build is better than r44048 by no means hell in 2 more hours it could become one of the worst builds ever. Before you go criticizing someone comment shouldn't you at least need to try the build first. So you do you.
From my past experience most 3rd party router software comes with some kind of bug no matter the router selected. Good luck with OpenWRT
Last edited by Justanotherbrokenrouter on Thu Apr 01, 2021 9:55; edited 2 times in total
Upgraded per my post above (WRT1200's) yesterday evening. Ran well and streamed with no issues. Zero issues.
This morning, the connection was gone, rebooted, regained connection but was incredibly slow, unusable actually.
Saw the new release and upgraded to that after I got the GUI up. So far it's working great, fast and connected.
I would suggest skipping this release. (r46220) and wait for some feedback concerning r46239. I will post after some uptime with the latest release in the proper thread.
There is a newer build already out. Nevertheless, I must note that SVN commit 46184 does have relevant driver changes (changelog states twice the disabling of TurboQAM for 2.4Ghz due to instability). It's far too early to tell how it behaves in the long run, but I'm seeing remarkable improvements even in my 5Ghz use-case.
