Joined: 08 May 2018 Posts: 14247 Location: Texas, USA
Posted: Sat Feb 22, 2020 23:40 Post subject:
It's too bad that you can't set up a development environment with the public svn repo since you need what is in the driver_repository repo to make a successful image. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I see a couple of things here at play. The jump from r37012 to r42366/r42410 put you right in the middle of a restructuring process for channel selection. The next build after r42460 should fix 5 Ghz reliably starting at boot. The last build before major changes was r42335.
Since you had similar 2.4 Ghz issues on r37012 this leads me to believe there's a problem between at least one of your client devices and the Marvell radio chipset.
If you don't want to hunt down devices, try WENED's workaround by setting 2.4 Ghz Wireless Network Mode to G-Only and/or disabling WMM. Save and then reboot.
Check syslog for spam auth request and deauthenticated due to inactivity. Hopefully all of that should disappear.
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sun Feb 23, 2020 16:19 Post subject:
Have done a lot of research and testing over the past few days.
WMM protocol is a QOS and Client Powersave protocol.
To function correctly both ends must be in sync.
Android 7, 8, 8.1 all have noted some problems with this. Can be corrected/minimized by configuration in the client device.( Don't ask, I don't have details). My two Zenphones are identical but one which I configured extensively to reduce battery use rarely has problems with my routers, the other is constantly re-connecting. This on mwlwifi which is a mess anyway. Setting to G only and disabling wmm does solve the constant disconnects.
For devices which do not support the wmm protocol (most cheap smart devices) switching to G only and disabling wmm is the only way to get decent connections.
Of course this only seems apparent with mwlwifi but I began thinking that if mwlwifi has so much trouble dealing with the protocol, it only comes to reason that other router chip sets would also be heavily taxed trying to handle this protocol. I have since disabled wmm and set my 1900 to G only to see how this might affect performance.
In the case of my 1900 I would get periodic reboots for no known reason. I have long suspected that it is due to the smart devices connected, as I know they are not wmm compatible and require constant internet connection. I have yet to see if this action stops the reboots. It is my belief at this time that if devices are not wmm compatible or incorrectly setup to accomodate it they over tax the router stack and eventually cause lockups or reboots. This is only conjecture at this point.
Blkt, you are correct in that device isolation is required to determine which devices are causing the lockups. In my case simply going to G only and disabling wmm is a simple solution as The increase in speed is negligible for any of my devices. Besides once wmm is active there is some speed loss anyway so being able to jump apparently 20% with wmm it is likely negated anyway. If I had devices that were capable of 300/600 on 2.4 I would obviously setup a separate VAP accordingly.
In conclusion, although wmm doesn't appear to cause any serious problem on non-mwlwifi I do believe it has an impact and should be considered as a source of strange problems. It may take a few days to determine if this is the cause of my reboots, but so far 36 hours and no reboot. _________________ 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
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Mon Feb 24, 2020 1:09 Post subject:
Additional testing netted the following results;
On my 3200 remote I restored wmm and N only operation.
Had to remove one old camera as it couldn't seem to decide if it was going to run on G or N , kept switching so I moved it to my other 3200 which I use for Sonoff devices.
Also by playing with the settings on my erratic Zenfone specifically turning off Wi-Fi search, I pretty much eliminated all strange entries in the syslog.
On the 1900 I tried using a VAP to isolate my cams from the Sonoff devices but still kept getting a lot of syslog entries. If I restored N/G and wmm I here too had devices that couldn't seem to decide on which band to run, so I went back to the G only.
Also to reduce the re-syncing I set the "Key Renewal Interval" to 86400 so it only occurs once a day rather than the default of every hour. _________________ 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
Additional testing netted the following results;
On my 3200 remote I restored wmm and N only operation.
Had to remove one old camera as it couldn't seem to decide if it was going to run on G or N , kept switching so I moved it to my other 3200 which I use for Sonoff devices.
Also by playing with the settings on my erratic Zenfone specifically turning off Wi-Fi search, I pretty much eliminated all strange entries in the syslog.
On the 1900 I tried using a VAP to isolate my cams from the Sonoff devices but still kept getting a lot of syslog entries. If I restored N/G and wmm I here too had devices that couldn't seem to decide on which band to run, so I went back to the G only.
Also to reduce the re-syncing I set the "Key Renewal Interval" to 86400 so it only occurs once a day rather than the default of every hour.
Disabling just wmm has given me the best 2.4ghz stability.
No issues so far in over 48 hours and that's not been known that I can remember.
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Mon Feb 24, 2020 23:35 Post subject:
Neil1454 wrote:
WENED wrote:
Additional testing netted the following results;
On my 3200 remote I restored wmm and N only operation.
Had to remove one old camera as it couldn't seem to decide if it was going to run on G or N , kept switching so I moved it to my other 3200 which I use for Sonoff devices.
Also by playing with the settings on my erratic Zenfone specifically turning off Wi-Fi search, I pretty much eliminated all strange entries in the syslog.
On the 1900 I tried using a VAP to isolate my cams from the Sonoff devices but still kept getting a lot of syslog entries. If I restored N/G and wmm I here too had devices that couldn't seem to decide on which band to run, so I went back to the G only.
Also to reduce the re-syncing I set the "Key Renewal Interval" to 86400 so it only occurs once a day rather than the default of every hour.
Disabling just wmm has given me the best 2.4ghz stability.
No issues so far in over 48 hours and that's not been known that I can remember.
Will report more the more tests i do.
I am glad to see you are making progress and operating much better. Don't delve too deep as mentioned in this and other posts BS is redeveloping the Wi-Fi. Do post if you discover anything new and like myself watch for new builds as they will likely be quite different for the wireless operation. _________________ 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
To use isolation to capture suspected devices causing the issues. What is the best way to do this ?
Via virtual wifi ?
Would enabling wmm on virtual wifi work or will that cause the lock up on the non virtual 2.4ghz radio as well ?
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Tue Feb 25, 2020 0:10 Post subject:
Neil1454 wrote:
To use isolation to capture suspected devices causing the issues. What is the best way to do this ?
Via virtual wifi ?
Would enabling wmm on virtual wifi work or will that cause the lock up on the non virtual 2.4ghz radio as well ?
The easiest way is as suggested. Disconnect devices (power off) one by one and monitor the results.
Setting up a VAP is also an option but I am not sure it is a viable solution. You must keep in mind that VAP gets a lot of it's settings from the AP and it is using the same radio so you may create a whole new set of problems. You can disable wmm on the VAP or AP separately but as I said not sure how effective this would be. Also by running a VAP remember that because it is still the same radio it will only communicate half the time on either.
I have the luxury of multiple routers where I can usually switch devices to a different configuration on another router. I also have a spare 1900 for use when diagnosing my remote 1900 in the barn.
Since you are currently running with wmm off on your AP you could create a VAP with wmm enabled, but be cautious of the results. Also to do proper testing and because the VAP inherits settings from the AP, you will need to set your AP mode to "Mixed" or at least "N/G mixed" as ther is not an option for this in a VAP.
Good luck and enjoy the indulgence. _________________ 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