Posted: Sun May 30, 2021 12:04 Post subject: New Build - 05/30/2021 - r46816
[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.
Upgraded WRT1200AC v1's from r46788 to r46816 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 1 hr, 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 #2632 SMP Sun May 30 05:32:04 +07 2021 armv7l
No issues with a routine update session. No red error messages in syslog. No GUI issues with the build seeming to have quicker response times.
46788 ran for days without crashes. I think for my issue, that problem was eliminated from build 46772.
I have tested for the issue I was describing under 46788 and 46772 about the Spoof messages from a Pi4 being connected both to ether (Static address) and wifi.
They also appear in this build.
Something is still funny with my Samsung S9+ connected to wifi. The speed is far to slow now (21 mbits/s), but at least no full stop so far.
Edit: Indeed full stop. Wifi restart on the phone to get back online with it...
Edit2:
Major problems with the phone on this build. Tried to assign it a static IP to it. Upon configuration and enabling, dnsmasq service crashed. Nameserver not available. Ping 8.8.8.8 responds, while ping google.com gives an error. Rebooted router - same story, until the Samsung was deleted from static leases. Setting it back to DHCP it quickly loses connection. 5 ghz radio: Phone debug info "No Internet - SL SL SL <Frequency><Router mac> rssi=27, score 60, speed=VERY FAST, tx=9.3,0.0,0.0 rx=2,1 STAs:N/A (2).
Edit3The lock-up of the router was due to me using "+"-sign in the name. Calling it just "S9" solved that issue.
Last edited by Fonzi on Mon May 31, 2021 17:05; edited 2 times in total
Upgraded using IE11.
First upgrade on all routers, reset both partitions to default and then entered all parameters from a default condition.
Subsequent upgrades all done without reset and those on remote WDS Stations were upgraded via WiFi without incident.
Tried to upgrade my 1200 V1, but because I used the wrong flash file on both partitions, it is now a boat anchor.
By doing a total reset on the routers, especially the 1900's this was first time that they have been running correctly without an archaic build (r31924).
Upgrades have been performed over the past few days without incident and functioning as they should. I also added VPN prior to doing all these upgrades and so far all is well. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Edit3The lock-up of the router was due to me using "+"-sign in the name. Calling it just "S9" solved that issue.
Just wanted to check in with you and make sure you're not experiencing the same issue. I am about to flash my first DDWRT with this build as a baseline for my WRT1900ACV2.
I have a note 10+ I just renamed it to S10 plus so hopefully shouldn't see that happen for me.
Edit3The lock-up of the router was due to me using "+"-sign in the name. Calling it just "S9" solved that issue.
Chargain wrote:
Just wanted to check in with you and make sure you're not experiencing the same issue. I am about to flash my first DDWRT with this build as a baseline for my WRT1900ACV2.
I have a note 10+ I just renamed it to S10 plus so hopefully shouldn't see that happen for me.
The lock-up was obviously due to the "+"-sign. After renaming the router is stable. However, contrary to many reports here - Our Apple devices are working OK on this build - but the S9+ just don't want to play with this setup. It starts out with fast wifi, slows down, and its just a matter of time, before it stays Wifi-connected with "No internet". Would be interesting to see if you with 10+ experience the same. I believe you have Android 11 - while the 9+ is at Android 10. Anyway - without another Access Point in the setup - the S9+ problem would probably prevent me, from keeping this setup. Incidentally, the AP is a Netgear R6700V3 - running the same build. And no such Wifi issues there.
Just to prevent advises about things I already tried:
- The MAC randomization on the S9+ is turned off
- Wifi Scan throttling, in dev options is turned off
Status: Reset previous build r44048 with router red button, power cycled to other partition with Linksys firmware, and flashed with factory-to-ddwrt.
This build has been working well with my Samsung note 9 for a little over 2 days without a single Wi-Fi issue. I have S10's in the household but haven't been able to test them due to needing to keep the peace 🙃 Note 9 hasn't played well with all of the newer builds. I guess I held my breath long enough this time flashing this build. Note 9 is on Android 10
Only changes from r44048 to r46816
5GHz 40MHz Mixed channel 100 Upper (WPA2 CCMP-128 (AES) Only)
U-APSD (Automatic Power Save) Disabled
Single User Beamforming Disabled
Multi User Beamforming Disabled
These I normally have to enable with r44048 to keep wireless from being flaky.
Update: Note 9 is still connected well without issues.
Only difference is 40MHz has less wifi distance on build r46816 than with r44048. My wife joined the network last night with S10 Android 11 without problems, but was only connected about 3 hours.
Info
Received (RX)
2962061 OK, no error
Transmitted (TX)
4391310 OK, no error
r44048 would have errors by now.
Update: r46816 is still stable. Tried gaming on VPN, and experienced lag, but that is to be expected.
Time: 21:07:03 up 3 days, 22:30, load average: 0.00, 0.00, 0.00
Last edited by Justanotherbrokenrouter on Wed Jun 16, 2021 0:24; edited 1 time in total
Joined: 04 Aug 2018 Posts: 1447 Location: Appalachian mountains, USA
Posted: Tue Jun 15, 2021 22:10 Post subject:
Updated one WRT1900ACSv2 from 46069 (still in the other partition) to 46816 via ssh over wifi and configured from scratch after nvram erase.
I've done several reboots along the way as I've tweaked things, but I've been up continuously for the past 24h or so.
Seven Apple devices, of all types and ages, have been connected on and off, and I've had no issues. Update: I've now had two iOS freezeups in the 48h since last booting, both in the second day up. Inter-boot sessions before that were all less than a day in length and had no freezes.
In fact things are flawless AFAIK except that sending SIGHUP to the OpenVPN client, in my case after having a script edit openvpn.conf to change servers, kills PBR. I've let resident OpenVPN guru @egc know.
The CHACHA20-POLY1305 data cipher for the OpenVPN client is awesome, btw. I'm maxing out my 200/10 ISP service to an AirVPN server a kilomile or so away.
_________________ 2x Netgear XR500 and 3x Linksys WRT1900ACSv2 on 53544: VLANs, VAPs, NAS, station mode, OpenVPN client (AirVPN), wireguard server (AirVPN port forward) and clients (AzireVPN, AirVPN, private), 3 DNSCrypt providers via VPN.
Updated one WRT1900ACSv2 from 46069 (still in the other partition) to 46816 via ssh over wifi and configured from scratch after nvram erase.
I've done several reboots along the way as I've tweaked things, but I've been up continuously for the past 24h or so.
In my opinion probably the best build at the moment for the WRT3200ACM. I have ran this build for several days without issues.
Updated one WRT1900ACSv2 from 46069 (still in the other partition) to 46816 via ssh over wifi and configured from scratch after nvram erase.
I've done several reboots along the way as I've tweaked things, but I've been up continuously for the past 24h or so.
In my opinion probably the best build at the moment for the WRT3200ACM. I have ran this build for several days without issues.
Are you able to access the router GUI using your Apple devices and this build?
Maybe it’s time to jump from r44048? _________________ Linksys WRT3200ACM
VersionDD-WRT v3.0-r50500 std (10/13/22)
Kernel VersionLinux 4.9.330 #3466 SMP Thu Oct 13 02:01:23 +07 2022 armv7l
Linksys RE9000 Extender (WiFi attached)
OpenVPN with PBR: ExpressVPN
Devices: Sonos, Apple, QNAP, Laserjet other
Joined: 04 Aug 2018 Posts: 1447 Location: Appalachian mountains, USA
Posted: Tue Jul 20, 2021 22:17 Post subject:
This replaces my earlier, preliminary post above. The routers discussed here have been used for several days running the new build. One, my primary (local) router, has been used with it for a couple of weeks. I do overnight reboots on all, however, so don't get too excited. All routers were configured from scratch but heavily using scripts developed originally for 46069 by examining diffs of nvram show outputs from before and after individual GUI changes. These scripts write the nvram commands that I sourced in the procedures below.
Updated four WRT1900ACSv2 routers to 46816, one from 42926, two from 44048, and one from 46069. Methods differed for the two local and the two (very) remote routers. This list of steps is approximate, but you get the idea: do as little by hand as possible, so as to be consistent across all routers:
Local routers were done mostly over ssh, using the GUI in one step only.
scp the firmware build file and files of nvram commands to router.
write buildFileName linux
nvram erase
Source files containing "nvram set" commands for basic setup, wlan0 and wlan1 setup, OpenVPN setup, nvram variables sshd_authorized_keys, dnsmasq_options, rc_startup, and rc_firewall.
reboot to bring up the new build for the first time. It comes up ssh capable with a running OpenVPN client, the latter because I actually considered doing this messy procedure for the remote routers. See below though for the better way those remote routers were actually handled.
In GUI add VAPs, wireguard client tunnels, and bridges in GUI without parameters.
scp and source nvram commands to set up details for VAPs, wireguard client tunnels, bridges, and DHCP servers.
reboot
In GUI set up DDNS and USB/NAS and add wireguard server tunnels without parameters.
scp and source nvram commands to set up wireguard server tunnels.
Remote routers were upgraded by building the config on a local spare router as above, backing up the config, then using the config to do the remote update using scp and ssh connected via VPN port forwarding with appropriate firewall rules at the other end.
scp buildFile and backupFile to router.
write buildFile linux
nvram erase && nvram restore backupFile && reboot
The only syslog issues were with the one (local) router that included USB/NAS/Samba with a 128GB flash drive. There were 93 lines of this sort:
Dec 31 19:00:25 TheRouter user.err wsdd2[1551]: error: wsdd-mcast-v4: wsd_send_soap_msg: send: Network unreachable
There were also several lines like
Dec 31 19:00:34 TheRouter local5.err ksmbd: [ksmbd-manager/3643]: ERROR: Failed to create lock file: File exists
followed by
Dec 31 19:00:33 TheRouter user.err wsdd2[1551]: Terminated received.
and three lines of the form
Jun 25 12:40:49 TheRouter user.err wsdd2[3631]: error: llmnr-tcp-v4: open_ep: SO_BINDTODEVICE: No such device
I don't use Windows discovery, so I didn't pursue this.
To work around the iOS-client freeze-up issue, I cut wlan0's bandwidth from 80 MHz to 40 MHz (AC/N-Mixed) to provide 3 dB more SNR on the uplink, which is where the problem appeared to be. Seems to have completely taken care of it on my primary local router, which is where the serious testing is taking place. In most of the house this did NOT cause loss of speed, because it turned out that 3 dB less noise bought more speed than dropping bandwidth to 40 MHz cost. One of the remote routers is still having freeze-ups, but it looks like it may be a signal-strength issue, so changes in router placement will be forthcoming there.
Other than that, things are flawless AFAIK except that sending SIGHUP to the OpenVPN client, in my case after having a script edit openvpn.conf to change servers, kills PBR. My workaround was adding ip rule... commands in route-up.sh to rebuild the PBR internals. The material added was minimal, but the details of making this work are messy. My recommendation is to not do the SIGHUP thing with this build. I've let resident OpenVPN guru @egc know about this PBR business.
The CHACHA20-POLY1305 data cipher for the OpenVPN client is awesome. I've seen a ton of comments that these WRT1900blah routers have OpenVPN clients limited to 70-90 Mbps. Nope. Not anymore. On my 200/10 ISP service to an AirVPN server over 2000 miles away:
237.5/10.5 Mbps _________________ 2x Netgear XR500 and 3x Linksys WRT1900ACSv2 on 53544: VLANs, VAPs, NAS, station mode, OpenVPN client (AirVPN), wireguard server (AirVPN port forward) and clients (AzireVPN, AirVPN, private), 3 DNSCrypt providers via VPN.
