seth_space wrote: > just installed the wlanpoke script.. it works but intermittent Drop out > of approx 40/45sec before reconect after some time.[ed] > I can see logs in /var/log and i activated the webserver -W slow > ... Link Quality:55/94 Signal level:-40 dBm Noise level:-96 dBm > ... > Ping 2s-1q6f Events, Fails[0..7] 3084s : Qr:0 Fr:8 Wr:0 Wc:0 [ 417 > 0 0 0 0 0 8 0 ] > Step 0:0, limit:results: [ 12:0,0,0,0,0,0,0,0, 18: 26: 37: 53: ] Wlan: > Rate=54 Quality:54/94 level:-41 retries:0 > Gaps:8 @1618416002 -Gap+OK secs: > +291,-47+375,-47+296,-45+323,-44+224,-41+393,-43+264,-44+258,-48+301, > Resets:8 @1618416002 -Gap+OK secs: > +290,-48+375,-47+296,-45+323,-44+224,-41+393,-43+264,-44+258,-48+301, Well, you certainly are getting hammered. Eight full resets in 51 minutes, we might say typical for heavy interference. Your signal levels are excellent. No single ping losses.
After some experimenting with wifi-6 here, using a 2.5 gHz wifi-6 client copying 15 GB, more or less completely disrupted 2 of the 7 radios here during the copy time, which wasn't particularly quick, not much if at all better than 802.11ac or n. (However, on the 5 gHz band, wifi-6 was awesome.) A full report of these tests will be made as time allows, but it seems that the wifi-6 is the culprit, and wifi-6 traffic makes it much, much worse. Some suggestions: disable wifi-6 on the 2.5 gHz band. Ask your neighbors to do the same. This may be a problem if their router won't let them disable wifi-6 on 2.5 gHz without doing so on 5 gHz. It might be helpful to scan your environment to identify wifi-6 routers and clients on 2.5 gHz. You can get routers from a windows notebook with a ($20 Intel AX200 implementation) wifi-6 adapter running netsh wlan show networks mode=bssid. Scanning for clients requires a promiscuous (monitor) mode wifi-6 adapter plus software. The AX200 driver does not supported this in Windows, but Linux might. You may benefit from enabling the quick reset function with the -Q 3 option to try the quick reset after the 3rd failed ping. The quick reset has been helpful here, although under some circumstances, the relief given is short lived, and multiple quick resets occur in succession only to be followed by a full reset. If it doesn't work at all, there is no harm done because the full reset comes along at its usual time anyway. If the quick reset is not working for you, because your signal is so strong, you could try to speed up the full reset to reduce the outage. You could advance its activation to work after the 2nd failed ping (aggressive) instead of the 6th, for example. With the default 6 trial, the script waits for 6*2.7=16 seconds or so before resetting. You might cut that down to 6. All of this points to the need for progress at the system driver level. ------------------------------------------------------------------------ POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
