Posted: Fri Aug 21, 2020 15:50 Post subject: wrt1900ac v1 has WiFi fixes coming in builds 44215+
Heads up to the group....
Looks like we have some improvements in 2.4Ghz radio code for the wrt1900ac v1. Initial reports show a decent improvement.
The Wifi range, speeds and interoperability improvements coming for the wrt1900ac v1 in 44215 and newer should be interesting to test. _________________ Location (urban) - 1x Linksys EA8500 (AP wlan0 & wlan1 enabled)
1x Asus 68u (Repeater Bridge w/VAP) - wl0 disabled
1x Asus 87u (Client Bridge) - wl1 disabled
So before I change anything with the next new build I'll just say that build 43055 has been rock solid on my wrt1900ac v1. I have the enviroment setup in my signature and I have 30 clients connected.
System
Router Name - wrt1900
Router Model - Linksys WRT1900AC
Firmware Version - DD-WRT v3.0-r43055 std (05/05/20)
Kernel Version - Linux 4.9.221 #1770 SMP Tue May 5 02:39:12 +03 2020 armv7l
Hostname - wrt1900
LAN Domain Name - localhost.local
Current Time - Fri, 21 Aug 2020 11:54:51
Uptime - 40 days, 15:42
CPU
CPU Model - Marvell Armada 370/XP
Load Average - 0% 0.00, 0.00, 0.00
Temperatures - CPU 66.7 °C / WL0 51.1 °C / WL1 53.2 °C
Enable Short Preamble and set a fixed Channel Width e.g. 20 or 40. Set a channel e.g. 1, 6 or 11 instead of Auto.
Thanks. Sure I'll give those a try. I'm not having any issues but I always like to tweak and improve.
I'll make these changes after I have successfully upgraded to the newest build. _________________ Location (urban) - 1x Linksys EA8500 (AP wlan0 & wlan1 enabled)
1x Asus 68u (Repeater Bridge w/VAP) - wl0 disabled
1x Asus 87u (Client Bridge) - wl1 disabled
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Fri Aug 21, 2020 19:33 Post subject:
blkt wrote:
Enable Short Preamble and set a fixed Channel Width e.g. 20 or 40 MHz. Set a channel e.g. 1, 6 or 11 instead of Auto.
Maybe lower ACK Timing to 1350 or 900. Maybe set 2.4 GHz Beacon Interval to a prime number such as 101, 5 GHz 191.
Because I'm out of ideas I am trying your suggestions which are much appreciated.
The only question I have is regarding the ACK Timing. Currently (recent builds) the default has been 500 compared to the 2000 in much older builds. So lowering does not make sense on these new builds or am I missing something?
Will have to wait and see if these minor changes help, but may be anywhere from 1 to 12 hours as the frequency of reboots is not constant. If it does help with the Deauth/remove errors it will be well worth the changes. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55460
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55460 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55460 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Joined: 04 Aug 2018 Posts: 1446 Location: Appalachian mountains, USA
Posted: Fri Aug 21, 2020 20:39 Post subject:
WENED wrote:
The only question I have is regarding the ACK Timing. Currently (recent builds) the default has been 500 compared to the 2000 in much older builds. So lowering does not make sense on these new builds or am I missing something?
I finally experimented a little with ack timing recently. It may have been at issue only during that period when I was experimenting with RTS/CTS for Protection Mode - memory too flaky to say - but it appeared that it set a range limit beyond which wifi would instantly refuse to connect. With the 500m setting I had just enough range to connect from the garage, but out in the driveway I'd instantly get an error popup on my phone when trying, even though there was plenty of signal. I think it's a round-trip range, so moving it up 2m allows you to connect from 1m farther away.
However, in an isolated rural setting, i.e. not significant interference from neighbors, I don't think there's any point to RTS/CTS and an ack range limit.
Perhaps someone with an actual clue will chime in and correct this, because this is very much not really my area. _________________ 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.
If it does help with the Deauth/remove errors it will be well worth the changes.
The only known solution for Marvell 2.4 GHz authenticated deauthenticated loops (aside from playing around with different builds) is to disable WMM Support and/or select G-Only or BG-Mixed, Full 20 MHz Channel Width and simplify Wireless Security i.e. WPA2 Personal, CCMP-128 (AES) only, the defaults. Legacy data rates are key to work around this wifi driver and/or binary blob issue.
Wireless -> Basic Settings should be configured and saved in the order below (reboot when done).
if yall have deauth issues try ack timing 0 that always fixed it for me currently i am trying 500 _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
Each chipset behaves differently; some read 0 as Disabled, to others Auto, or in the case of QCA it uses nearest value up 450.
An example with my EA8500 (QCA) is ACK Timing ignores the current DD-WRT default value of 500 and uses 900 anyway.
So 0 is definitely worth a try. In older builds the default was 2000 though it should be 900, 1350 or 1800 (increments of 450).
As for Beacon Interval, everyone seems to have their own magic values or formula lol. I just choose a prime number between 101 and 199, as I don't use VAP or multiple SSID. I read that a value of 100 is really 102.4ms, so maybe prime numbers just make people feel warm & fuzzy inside (placebo) and really should just choose 100, 200 maybe increments of 50 etc. Mmm... Bacon.
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sat Aug 22, 2020 4:52 Post subject:
I have tried mucking with the settings suggested here and had a look at the Wiki pages to better understand, however nothing helped. Still getting Deauth/Remove errors and periodic reboots for no known reason. I have posted elsewhere some of my logs but they don't show any particular cause of the reboots.
I know I can return to r31924 which always ran without problem but because r44213 always recovers when a reboot occurs and any Deauth's also recover I will continue as is and hope maybe future builds might correct some of the problems.
It is ironic that the reboots only occur on the remote in WDS Station mode or Client Bridged mode. I have never experienced any reboots on my other 1900's except power related. In one case my dead 2.4Ghz 1900 although in WDS Station mode has never rebooted.
My only conclusion is it specific to the 1900V1 running as a client or WDS Station on the 5Ghz and using the 2.4Ghz for an AP. Pretty much running as an extender in Fast Track mode. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55460
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55460 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55460 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Each chipset behaves differently; some read 0 as Disabled, to others Auto, or in the case of QCA it uses nearest value up 450.
An example with my EA8500 (QCA) is ACK Timing ignores the current DD-WRT default value of 500 and uses 900 anyway.
So 0 is definitely worth a try. In older builds the default was 2000 though it should be 900, 1350 or 1800 (increments of 450).
As for Beacon Interval, everyone seems to have their own magic values or formula lol. I just choose a prime number between 101 and 199, as I don't use VAP or multiple SSID. I read that a value of 100 is really 102.4ms, so maybe prime numbers just make people feel warm & fuzzy inside (placebo) and really should just choose 100, 200 maybe increments of 50 etc. Mmm... Bacon.
thats pretty informative, esp the bacon part js
switched to 1350 as 500 was giving me some strange issues at about half signal
Id also like to point out that everytime i turn the wireless radio off that in Fact nothing seems to connect JS _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
r44236 was possibly the worst time I have ever encountered. That story on the build post.
However blkt I have been following many other posts where you have commented and started wondering about r44048 since I had not tried that one.
Well to my amazement I have been running 48 hrs without a reboot on famous remote 1900V1 and overall very few entries for deauth/remove most of which were normal as I shut down some Android devices overnight.
Overall I am surprisingly impressed with this build as it is the only newer build in the past two years that has been this stable on my remote 1900V1 other than r31924.
So, thank you blkt for your continued advice. Incidentally I put r44048 onto all the routers (except master) by IE11 Reset and used predominantly all default settings except where otherwise noted in my profile. Even though I did not reset on the Master 3200, it also is performing well. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55460
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55460 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55460 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use