If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
Simplified instructions for Squeezebox Radio Wi-Fi fix (wlanpoke)
I want to thank the OP for his excellent instructions.
I was having a problem with my SB Radio WIFI networking dropping and gave this a try. It looks like it worked.
Too bad I went on ebay and bought another $250 SB Radio new. Oh Well.
I want to thank the OP for his excellent instructions.
I was having a problem with my SB Radio WIFI networking dropping and gave this a try. It looks like it worked.
Too bad I went on ebay and bought another $250 SB Radio new. Oh Well.
Unfortunately, this did not fix my problem.
I think this fixed my problem:
If that doesn’t fix it, then it’s interference from a neighbor’s WiFi and the only reliable way is to bypass the SB radio’s WiFi with an Ethernet connection (direct or with a WiFi to Ethernet dongle, I.e. Vonets)
So for my router, I switched the mode under 2.4 from 600 to 289 and that fixed my problem....so far
ok so that guy disabled his AX mode which is Wi-Fi 6.
I am trying to understand what you did :-) What does this mean > I switched the mode under 2.4 from 600 to 289
I guess your router/AP shows channel bondings as speed?
ok I am not sure if it is wlanpoke or something else..........but the one radio I installed wlanpoke, its network icon is still white. However it did stop playing after some time. But I switched to another preset and then the radio started playing. So I am not 100% sure if wlanpoke is the solution (if the playback stops).
I can say it is better than nothing :-) Thank you!
The other SB radio's turned red. I will install wlanpoke on that one too.
From all the research and troubleshooting I have done into this, it seems to me that the device itself disconnects from the wifi AP (access point/router). It is not the fault of wifi 6 or some other setting on the AP.
ok I can today confirm that my 2 SB radios have managed to stay connected overnight after wlanpoke was installed on both
THANK YOU for making this script.
And thanks for posting these instructions.
One minor thing, it is mentioned to change directory to \etc. (probably just a typo) That will not work because in Linux we do a forward slash /
So change directory to /etc.
PS: I am very curious exactly what wlanpoke does, gotta look into the script when I get a minute :-)
Late to the party on this one. Wish I'd seen this thread last year!!
Many thanks rojikewl for putting those instructions together and thank you to the creator of WANpoke - PomDev2.
30 mins after the instal without a drop so it looks like I am now finally able to switch on 2.4 WiFi 6 on my ASUS mesh
HB
1 x Duet, 3 x Yamaha Restio, 3 x Radio, 2 x Touch with iPeng 9 served by Synology DS2419+, Docker and LMS 8.2.0
I was blissfully unaware of this whole issue until about a week ago. Then the new neighbour (I'm assuming him, but could be another neighbour - but everything points to him) started up their new shiny Wifi 6 router and I could not understand what had hit my 3 radios.
Luckily came across the wlanpoke threads reasonably quickly and installed on my 3 radios. Much better. But occasionally I have seen the dreaded red symbol, and even when that does not happen I reckon I get 3 dropouts an hour from a radio in use (will measure more scientifically when back home in 10 days).
Before I go any further, many many thanks to the dev Pomdev and to the creators of this thread and the macOS thread for their efforts. Made getting my radios back to mostly usable very easy.
Lastly from what I understand there is no long term solution to this - only a firmware patch for the wifi radio will do it, and that must come from the manufacturer, and that is highly unlikely. Is this correct?
Therefore workarounds/mitigation options are:
wlanpoke
get neighbour to deactivate wifi 6
aluminium foil around the radio (pseudo faraday cage to shield from the neighbour's wifi)
use Ethernet instead of wifi (real shame - do not always have a socket nearby, and for at least one radio I use the portability a lot)
Vonet or similar, with a battery to make it portable
And then the final thing is to replace the radio (I can repurpose 2 of my 3, but need a portable/wifi solution too) - but with what? I cannot see myself moving away from squeezebox for now (this forum, and the dedicated things some members do and provide is a major reason), I have not seen anything better (for my needs) and have invested a bit in it (1x SBC, 1x SBT, 3x Radios).
I was blissfully unaware of this whole issue until about a week ago. Then the new neighbour (I'm assuming him, but could be another neighbour - but everything points to him) started up their new shiny Wifi 6 router and I could not understand what had hit my 3 radios.
Luckily came across the wlanpoke threads reasonably quickly and installed on my 3 radios. Much better. But occasionally I have seen the dreaded red symbol, and even when that does not happen I reckon I get 3 dropouts an hour from a radio in use (will measure more scientifically when back home in 10 days).
Before I go any further, many many thanks to the dev Pomdev and to the creators of this thread and the macOS thread for their efforts. Made getting my radios back to mostly usable very easy.
Lastly from what I understand there is no long term solution to this - only a firmware patch for the wifi radio will do it, and that must come from the manufacturer, and that is highly unlikely. Is this correct?
Therefore workarounds/mitigation options are:
wlanpoke
get neighbour to deactivate wifi 6
aluminium foil around the radio (pseudo faraday cage to shield from the neighbour's wifi)
use Ethernet instead of wifi (real shame - do not always have a socket nearby, and for at least one radio I use the portability a lot)
Vonet or similar, with a battery to make it portable
And then the final thing is to replace the radio (I can repurpose 2 of my 3, but need a portable/wifi solution too) - but with what? I cannot see myself moving away from squeezebox for now (this forum, and the dedicated things some members do and provide is a major reason), I have not seen anything better (for my needs) and have invested a bit in it (1x SBC, 1x SBT, 3x Radios).
you did a great job of reading the various threads and summarizing
My 2 cents (or p) - but not I do not have a wifi 6 router and don't have nearby neighbors, so I don't have the problem. But, I love my radios. I have many. I would not be inclined to give up on them. I'm still buying ones I don't need on ebay at the right price because there is a whole lot of value for $USD50.
If it is your neighbor, it all comes down to increasing your wifi strength, or attenuating theirs. Or, as in the vonnets or ethernet, eliminating the vulnerable wifi of the radio. I think there is a vonnet that can be powered and in turn power the radio (another thread somewhere). But the portability thing isn't addressed. Wifi access points/repeaters near the radios have also been discussed, basically saturating/maxing your wifi signal that the radio sees. I have played around a bit with foil, and never had any luck, but others have, and since I am not affected, I didn't give it much effort. One thing to test, I think that Pomdev suggested it, is, if you have a basement, play your radio on wifi in your basement. Ground/soil is an excellent attenuator of 2.4GHz.
An idea (and this just something I was dreaming I'd like to try to tackle) would be to extract the electronics of a vonnets or similar, modify it's power to accept the radio adaptor or battery power (add some buck or boost), and create a form factor that would stick in that crevice in the back of the radio, plugging into ethernet and power. Maybe use the headphone jack (pass through or just physical attachment of module to radio). Ideally in the given space, but maybe sticking out a bit (like a pod).
But I have allot of ideas that just sit there
Also, if you haven't, use something like wifi analyzer (android) to see what your radio is seeing in terms of your and neighbor's signal. I might even tell you what neighbor is the problem (by walking toward/away and watching the signal change)
After months of no problems with the Radio, I started having major problems last week. It never stays connected for more than 10 minutes. When it is on the network, signal strength in LMS shows only 73-78%, where it used to always be at least 86%.
I installed wlanpoke and it's no better, still drops off after a few minutes. Is there some means of checking to see that wlanpoke is actually running? I tried the Windows batch file provided, but that just times out.
... I installed wlanpoke and it's no better, still drops off after a few minutes. Is there some means of checking to see that wlanpoke is actually running?
Open a browser to the optional wlanpoke web server:
http://<Squeezebox IP address>:8080/
to display an assortment of status information. Scroll to the "important processes" section at the bottom and observe an entry resembling:
If that line is not there, wlanpoke is not running.
If the web page does not display, the optional web server is not running. Enable it by using SSH to edit the /etc/init.d.rcS.local file to include the "-W slow" option, e.g.:
/etc/wlanpoke/wlanpoke.sh -W slow &
You can also run a(n) ncat listener on your pc to listen to wlanpoke's reports. If you are not running the listener, you should disable reporting using the "-x" option.
I tried the Windows batch file provided, but that just times out.
The "gs.bat" batch file requires the optional web server running, "curl" installed, and the batch file edited to use the Radio's IP address.
See "manual.txt" for more information.
It sounds like the script is not being launched or failing. You can test the installation step by step using the instructions in the manual. For example, launching the script directly from the SSH shell (e,g,m using the command in rcS.local above) will display various messages including a final error message if the script is somehow failing. Good Luck!
It sounds like the script is not being launched or failing.
Yeah, I failed to read the manual about how to enable the HTTP server, but did so this morning. With the HTTP server running on port 80, now I get the following:
Code:
C:\>curl -v http://192.168.9.111/RawFails
* Trying 192.168.9.111:80...
* Connected to 192.168.9.111 (192.168.9.111) port 80 (#0)
> GET /RawFails HTTP/1.1
> Host: 192.168.9.111
> User-Agent: curl/7.79.0
> Accept: */*
>
* Received HTTP/0.9 when not allowed
* Closing connection 0
curl: (1) Received HTTP/0.9 when not allowed
Never had this problem before, but it has now surfaced on my bedside Radio this week, which is running community firmware.
WiFi icon will turn blue, then if I try to reconnect to WiFi, sometimes it will, but still can't see the server.
Other times it just goes red, and no amount of futzing will get it back online. Only a reboot will recover the connection.
After a reboot, if left alone, the Radio will stay connected for only ~5 minutes.
If I am playing anything, the connection appears to stays up indefinitely.
Radio WiFi IP was set static via SSH years ago.
Have an older Asus router with no WiFi 6. Possibly a neighbor recently upgraded theirs.
I saw another thread about a patch for the Radio, and potentially having to rollback LMS to apply it, but I have no idea how to verify if the patch is applied.
Installed wlanpoke as per instructions here. No change.
I don't need the radio to be portable, but don't have a nearby wired network drop, so I ordered an IO Gear Etherent > WiFi adapter (read they were slightly better than Vonets, but I like the idea of passing power through the Vonet to the Radio, so we'll see).
However, I'm now reading that there have been issues with wired as well...???
I'm deep in the Squeezebox ecosystem for close to 20 years, and am not about bail now.
Will the patch mentioned above help? I can't find the info about it again to save my life atm.
***EDIT*** Found the info about the patch I was referring to. Seems it was for Radios not connecting to LMS after updating to community fw, so don't think it applies here.
...
* Received HTTP/0.9 when not allowed
* Closing connection 0
curl: (1) Received HTTP/0.9 when not allowed
Time marches on. Regrettably, the curl 7.79.0 and later versions have become more particular about what they accept. The /RawFails URL returns just raw WLAN failure data without http headers and formatting (i.e., raw) for quick logging and status display. To receive /RawFails using curl now requires adding the new "--http0.9" option, which evidently is forgiving of header-less responses (from "curl --help http": --http0.9 Allow HTTP 0.9 responses). So the default command for later curl versions should be:
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment