Home of the Squeezebox™ & Transporter® network music players.
Page 25 of 28 FirstFirst ... 152324252627 ... LastLast
Results 241 to 250 of 273
  1. #241
    Quote Originally Posted by seth_space View Post
    Both neighbors are using it in a mesh system with only one SSID. During Corona they are heavy users with online schools and team meetings.
    So not an option i guess. I will try the settings according to your advice.
    Btw, a Inssider scan found 16 wifi different SSIDs (<-80dBm) and some "invisible" the curse of the city ;(
    so i tried the agressive way..
    /etc/wlanpoke/wlanpoke.sh -W slow -Wp 80 -Q 3 -F 2 -S 1 &
    ...
    Ping 1s3q2f Events, Fails[0..3] 499s : Qr:0 Fr:1 Wr:0 Wc:0 [ 132 4 1 0 ]
    Step 1:0, limit:results: [ 2:0, 4: 7: 11: 16: 23: 33: 47: ] Wlan: Rate=54 Quality:55/94 level:-40 retries:0
    Gaps:5 @1618423770 -Gap+OK secs: +97,-5+7,-31+21,-4+40,-6+244,-5+39,
    Resets:1 @1618423770 -Gap+OK secs: +109,-31+359,
    Your -F 2 full reset is coming before the -Q 3 quick reset. You might try using the quick reset first, leaving the full reset where it was. If you cannot use quick reset, then disable it. Quick reset > full reset has never been tested, although it doesn't look like quick reset was triggered.

    It looks like the -F 2 is saving about 10-14 seconds or so. Still, 31 seconds 9 times/hour seems like a lot. Can you time the music interruptions? What service? Can you increase the buffering by the interruption time? Does that keep the music un-interrupted?

    Looking into the neighbors, the free Nirsoft utility WiFiInfoView for Windows will show you your neighbor's access points and protocols, even without a wifi-6 adapter. They may be agreeable to disabling wifi-6 on the 2.4 gHz band and going back to -n or wifi-4 (wifi-5 or -ac doesn't work on the 2.4 gHz band). They may even be suffering themselves. See this FAQ for one manufacturer's instructions. They recommend disabling wifi-6 on the 2.4 gHz band, and other settings. To locate the hidden network, walk around with a smart phone WiFi analyzer and look for increasing signal strengths.

  2. #242
    Junior Member
    Join Date
    Sep 2017
    Posts
    16
    I have just updated wlanpoke from v0.6.3 to v0.8.4. I will see if quick reset will help in my case.
    If I understand correctly, I should not see any effect in the number of connectivity losses per day but these reconnections should take less time (and maybe not create music interruptions).

    I don't follow completely your explanation under Log File Analysis. I have to re-read when kids won't be around.

    Here is my output for one radio:
    Code:
    Wireless LAN Statistics
    
    Squeezebox Cuisine wlanpoke.sh 0.8.4.1 4/6/2021 launched 2021-04-15_14:28:40 1618489720 Options: -W slow logging to /var/log/
    Thu Apr 15 16:44:41 CEST 2021 ( 16:44:41 up 2 days, 20:36, load average: 1.14, 0.98, 0.98 )
    
    eth1      AR6000 802.11g  ESSID:"MUSIC"  
              Mode:Managed  Frequency:2.412 GHz  Access Point: 28:C6:8E:B3:D4:BD   
              Bit Rate=54 Mb/s   Tx-Power=15 dBm   Sensitivity=0/3  
              Retry:on   
              Encryption key:off
              Link Quality:41/94  Signal level:-54 dBm  Noise level:-96 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:3  Invalid misc:0   Missed beacon:0
    
    Ping: settings, events, and failed pings [0..n]; Step: full reset results, status; Gaps, Resets: # and recents
    
    Ping 2s-1q6f Events, Fails[0..7] 8154s :    Qr:0 Fr:27   Wr:0 Wc:0  [ 2299 10 0 0 0 0 27 0 ]
    Step 0:0, limit:results: [ 12:0,0,0,0,0,0,0,0,0,0,0,0 18: 26: 37: 53: ]   Wlan: Rate=54 Quality:41/94 level:-54 retries:2
    Gaps:37 @1618497874 -Gap+OK secs: +175,-4+31,-42+145,-4+38,-41+289,-42+134,-42+122,-41+48,-3+241,-42+183,-41+192,-3+200,-42+6,-4+113,-41+126,-41+218,-41+183,-42+183,
    Resets:27 @1618497874 -Gap+OK secs: +210,-42+187,-41+289,-42+134,-42+122,-41+292,-42+183,-41+395,-42+123,-41+126,-41+218,-41+183,-42+183,-42+187,-42+122,-41+397,-41+184,
    
    recent AP scan results
    
    Selected interface 'eth1'
    bssid / frequency / signal level / flags / ssid
    28:c6:8e:b3:d4:bd	2412	-51	[WPA2-PSK-CCMP][ESS]	MUSIC
    24:4b:fe:f5:05:b0	2432	-53	[WPA2-PSK-CCMP][WPS][ESS]	faidherbe
    24:4b:fe:f4:c3:21	2432	-70	[WPA2-PSK-CCMP][WPS][ESS]	faidherbe
    Thank you very much @POMdev, you're doing a great job in helping us.
    Are you confident we could get an actual solution packaged in community firmware fixing all our disconnection issues?

  3. #243
    I succeeded in changing the other wifi networks to use only B/G/N on the 2,4Ghz band.
    That resulted in two total freezes of the community build. A normal on/off resulted in an extremely slow system. After a few reboots the radio worked again. Never experienced this before.
    But the result is nice.

    At the moment the radio is stable for 24hours. One problem, the wlanpoke script stopped working, at least the webpage is unavailable.
    Is it possible the script crashed?

    The last var/log fping.txt

    Ping 2s3q2f Events, Fails[0..23] 38819s : Qr:19 Fr:13 Wr:0 Wc:0 [ 12680 13 1 3 5:2 6:15 12:2 13:1 23:1 ]
    Step 3:4, limit:results: [ 4:0, 7:6,0,0,0,6, 11:10,0, 16:8,10,8,16, 23:8, 33: 47: ] Wlan: Rate=48 Quality:25/94 level:-70 retries:15
    Gaps:38 @1618601255 -Gap+OK secs: +1212,-3+2170,-4+7410,-3+2718,-3+820,-3+2357,-4+201,-62+17,-21+20,-22+5,-21+14,-21+3288,-64+57,-21+8,-21+20,-19+11,-21+15,-21+14,
    Resets:9 @1618601255 -Gap+OK secs: +16908,-62+3429,-64+1766,-64+2089,-160+2465,-31+3468,-33+1854,-30+2114,-59+1500,-28+2696,


    for now i restarted the script (without the Q parameter) and will post the results later.
    Last edited by seth_space; 2021-04-16 at 12:39.

  4. #244
    Quote Originally Posted by seth_space View Post
    I succeeded in changing the other wifi networks to use only B/G/N on the 2,4Ghz band. ...
    At the moment the radio is stable for 24hours. One problem, the wlanpoke script stopped working, at least the webpage is unavailable.
    Is it possible the script crashed?

    Ping 2s3q2f Events, Fails[0..23] 38819s : Qr:19 Fr:13 Wr:0 Wc:0 [ 12680 13 1 3 5:2 6:15 12:2 13:1 23:1 ]
    Step 3:4, limit:results: [ 4:0, 7:6,0,0,0,6, 11:10,0, 16:8,10,8,16, 23:8, 33: 47: ] Wlan: Rate=48 Quality:25/94 level:-70 retries:15
    Gaps:38 @1618601255 -Gap+OK secs: +1212,-3+2170,-4+7410,-3+2718,-3+820,-3+2357,-4+201,-62+17,-21+20,-22+5,-21+14,-21+3288,-64+57,-21+8,-21+20,-19+11,-21+15,-21+14,
    Resets:9 @1618601255 -Gap+OK secs: +16908,-62+3429,-64+1766,-64+2089,-160+2465,-31+3468,-33+1854,-30+2114,-59+1500,-28+2696,

    for now i restarted the script (without the Q parameter) and will post the results later.
    To test the quick reset, use just the -Q 3 and no -F option.

    In two instances in the last few weeks over 7 radios subjected to various tortures, the 'slow' web page was not available. The server just stops if there is a script error. The ahttpd.sh server is launched by but completely separate from wlanpoke. You can get the report without the server from ssh cd /etc/wlanpoke ; ./awstats.sh.

    Running B/G/N on 2,4Ghz is a start. Did you change the neighbor's, too? You reported 13 full resets in ~11 hours, much better than 9 / hour, and none in the last 4.6 hours. That's pretty good for a very low signal level of -70 dBm. Improving this to the -50 dBm range should help in several ways.

    My new wifi-6 AP has been on 2.5 GHz mixed ax for several days now, and when transferring 13GB of data, it caused 2 radios to go offline for extended periods of time. Using ssh to add the BSSID of the new AP to the "badAP" list caused them to calm down. (/lib/atheros/wmiconfig --badAP xx:xx:xx:xx:xx:xx --num=0). Too bad there are only two slots 0 and 1 for that to work, otherwise I could add the 10-11 other wifi-6 BSSIDs that are detectable around here (although at low levels). Six of these is from a single ax mesh household.
    Last edited by POMdev; 2021-04-16 at 19:31.

  5. #245
    Quote Originally Posted by castor_fou View Post
    ... any effect in the number of connectivity losses per day...
    I don't follow completely your explanation under Log File Analysis. ...
    Ping 2s-1q6f Events, Fails[0..7] 8154s : Qr:0 Fr:27 Wr:0 Wc:0 [ 2299 10 0 0 0 0 27 0 ]
    ...Are you confident we could get an actual solution packaged in community firmware fixing all our disconnection issues?
    The number of connectivity losses may go up if the quick reset effects don't last very long, but 'hopefully', those brief outages they will not result in music interruptions. You are experiencing 12 resets per hour, that's high, especially considering your very good signal level of -54 dBm.

    Too bad the script is so complicated as it is. The modest mitigation portion is just detection, a full "brute force" reset, one of many possible 'quick' resets, and making sure that the os software stack is running (e.g. 'wpa_cli' occasionally disappears, and we relaunch it). Most of the script is data capture, which takes a lot of processing time. Some of the data is for validating the script, but most of it is for evaluating the environment and the radio's response to the outages. It is not practical to do other than the most basic analysis on the radio using a script. So we have to do it ourselves, perhaps by processing the captured data with some (e.g., your) desktop analysis code.

    Explaining the data in an understandable and concise manner is not easy, and there are so many different cases to explain, especially as the software evolves into new areas of investigation. For example, we are not logging actual music interruptions for correlation to outages, but the most important measure is music interruptions, and is critical to evaluating different mitigation methods.

    "Confident" would be going too far. The attitude is "Hopeful." The real solution would be for Qualcomm/Atheros to investigate and patch their (by necessity closed) chip firmware, if not to prevent loss of receiver sensitivity then at least to monitor it and offer some much quicker method for resetting or adjusting the systems on the chip so that they do not repeatedly fail to respond to packets. What we can do is build on the expressly open yet unavailable source os driver stack to implement detection and mitigation that can work far more quickly and efficiently than the current mitigation script, so that the usual buffering would make very brief degradations or interruptions unnoticeable. Whether the latter mitigation can be adequately justified, tested, and validated and thus be fit for inclusion into an official software release is for others to decide.

  6. #246
    webserver keeps crashing so only a short view:
    Squeezebox RadioBAD wlanpoke.sh 0.8.4.1 4/6/2021 launched 2021-04-17_16:41:38 1618670498 Options: -W slow -Wp 80 -Q 3 logging to /var/log/
    Sat Apr 17 17:15:50 CEST 2021 ( 17:15:50 up 12:27, load average: 0.94, 1.06, 1.09 )

    eth1 AR6000 802.11g ESSID:"HAX3_Wi-Fi5"
    Mode:Managed Frequency:2.437 GHz Access Point: 5C:78:xxxxxx
    Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3
    Retryn
    Encryption keyff
    Link Quality:27/94 Signal level:-68 dBm Noise level:-96 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    Ping: settings, events, and failed pings [0..n]; Step: full reset results, status; Gaps, Resets: # and recents
    Ping 2s3q6f Events, Fails[0..7] 2028s : Qr:1 Fr:1 Wr:0 Wc:0 [ 675 0 0 0 0 0 1 0 ]
    Step 0:0, limit:results: [ 12:0, 18: 26: 37: 53: ] Wlan: Rate=54 Quality:27/94 level:-68 retries:0
    Gaps:1 @1618672526 -Gap+OK secs: +81,-41+1906,
    Resets:1 @1618672526 -Gap+OK secs: +81,-41+1906,

  7. #247
    Quote Originally Posted by seth_space View Post
    webserver keeps crashing so only a short view:
    Squeezebox RadioBAD wlanpoke.sh 0.8.4.1 4/6/2021 launched 2021-04-17_16:41:38 1618670498 Options: -W slow -Wp 80 -Q 3 logging to /var/log/
    ...
    Ping 2s3q6f Events, Fails[0..7] 2028s : Qr:1 Fr:1 Wr:0 Wc:0 [ 675 0 0 0 0 0 1 0 ]
    Step 0:0, limit:results: [ 12:0, 18: 26: 37: 53: ] Wlan: Rate=54 Quality:27/94 level:-68 retries:0
    Gaps:1 @1618672526 -Gap+OK secs: +81,-41+1906,
    Resets:1 @1618672526 -Gap+OK secs: +81,-41+1906,
    I launched the script via ssh on the hardest-hit (54268s: Qr:67 Fr:12) machine here: /etc/wlanpoke/wlanpoke.sh -W slow -Wp 80 -Q 3 &, then "pounded" on it from a Firefox browser window, including odd URLs, but it kept working, even through seven quick resets followed by a full reset. (Firefox is pretty aggressive retrying unresponsive sites.) You frequently experience the server not working, and might be in a good position to fix this issue. Adding some logging would give a clue, e.g., adding several echo `date` "got (here)" > /var/log/w.log or something, then looking at the log to see where it stopped. If you want to debug this, the GitHub issues tab would be a good place to correspond. If not, there is always ssh cd /etc/wlanpoke ; ./awstats.sh to get the current report.

    BTW, your "Resets" entry does not show the quick reset despite Qr:1 Fr:1. That's odd. What is expected is Resets:1 @1618672526 -Gap+OK secs: +81,-41+-15,-15+1906,, where the 15s are the time taken by the quick reset. Another mystery. Thanks for testing all this.

  8. #248
    This is the recent fping.txt

    Ping 2s3q6f Events, Fails[0..12] 108461s : Qr:62 Fr:44 Wr:0 Wc:0 [ 34178 33 0 1 0 12 39 1 8:1 9:2 10:1 11:1 12:4 ]
    Step 0:0, limit:results: [ 12:0,8,0,12,0,0,0,0,0,0,0,0 18:0,0,0,0,0,0, 26: 37: 53: ] Wlan: Rate=48 Quality:23/94 level:-72 retries:2
    Gaps:95 @1618778959 -Gap+OK secs: +570,-44+223,-3+1753,-52+5,-21+9,-18+8,-23+17,-10+5,-19+8,-22+52,-26+14,-22+65,-22+92,-21+49,-21+28,-21+1002,-3+1347,-59+2201,
    Resets:40 @1618778959 -Gap+OK secs: +570,-44+1978,-53+2950,-59+2201,-41+2120,-85+2864,-44+1738,-42+1804,-49+2396,-42+2188,-42+4750,-43+2017,-43+1862,-47+3626,-42+1436,

  9. #249
    Quote Originally Posted by seth_space View Post
    This is the recent fping.txt

    Ping 2s3q6f Events, Fails[0..12] 108461s : Qr:62 Fr:44 Wr:0 Wc:0 [ 34178 33 0 1 0 12 39 1 8:1 9:2 10:1 11:1 12:4 ]
    Step 0:0, limit:results: [ 12:0,8,0,12,0,0,0,0,0,0,0,0 18:0,0,0,0,0,0, 26: 37: 53: ] Wlan: Rate=48 Quality:23/94 level:-72 retries:2
    Gaps:95 @1618778959 -Gap+OK secs: +570,-44+223,-3+1753,-52+5,-21+9,-18+8,-23+17,-10+5,-19+8,-22+52,-26+14,-22+65,-22+92,-21+49,-21+28,-21+1002,-3+1347,-59+2201,
    Resets:40 @1618778959 -Gap+OK secs: +570,-44+1978,-53+2950,-59+2201,-41+2120,-85+2864,-44+1738,-42+1804,-49+2396,-42+2188,-42+4750,-43+2017,-43+1862,-47+3626,-42+1436,
    You can see some quick resets in the Gaps report, although at 21-26 seconds, they don't look that "quick" (resulting in a music gap?), and they don't last very long before the next gap. Not being so quick might have something to do with your very low signal level of -72 dBm, long lasting seems to be independent of signal level. The quick reset might be more effective only with higher signal levels. Sill, even with the low signal lever, 44 (or 40) resets in 30 hours is not so bad, considering that others have experienced 8-12 per hour.

    The 0.8.4.1 version from the main branch and release doesn't display the combined quick and full resets clearly. You can try the 0.8.4.2 or now 0.8.5.5 versions in the development branch for a better understanding.

  10. #250
    For now it works for >95% and that is a lot more then i had. So thanks for that already.
    The webserver keeps crashing after one or two hours.
    You suggested some lines added to a script.
    Please explain a bit more in detail (pref a example) to find the cause.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •