-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 20H2 Appears to Break SoapySDRServer --bind #288
Comments
The discovery operates over a multi-cast protocol SSDP: https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol On the client side, if you set the environment variable SOAPY_SDR_LOG_LEVEL to DEBUG, you should see prints about discovered servers. It may also be worth watching wireshark with the filter for SSDP to see if its being blocked in or maybe out. Both the client side of SoapyRemote should be requesting network servers to send, and on the server side, the server should be regularly sending out discovery info as well as replying to those requests. |
tl;dr;
In my setup after upgrading to Windows 10 20H2
SoapySDRServer.exe --bind
no longer appears to work (some firewall corner case is filtering this). I am working around this by explicitly declaring the interface to bind to like so:SoapySDRServer.exe --bind="0.0.0.0"
The Long
After experiencing a switch outage, I power cycled all my equipment, sadly this means I took the Windows 10 20H2 update on the Windows box I am using to host several Nooelec NESDR SMArt v4 devices. After the machine came back on I was no longer able to use CubicSDR to "see" the devices hosted on the Windows Machine.
After several hours of debugging and updating packages (I am now on the latest Windows
PothosSDR-2020.12.28-vc14-x64
) I believe that there is an issue with Windows and the way thatSoapySDRServer.exe --bind
behave.Here is a truncated version that gets to the jist of this:
SoapySDRServer.exe --bind
nmap 10.1.0.10 -Pn -p 55132
which returned the following:filtered
- This would seem to indicate some type of Firewall Issue, but the Firewall should have already been configured from before the Windows update to allow SoapySDRServer through.nmap 10.1.0.10 -Pn -p 55132
on the RPiclosed
? This makes zero sense!SoapySDRServer.exe --bind="10.1.0.10"
nmap 10.1.0.10 -Pn -p 55132
on the RPinmap 10.1.0.10 -Pn -p 55132
SoapySDRServer.exe --bind="0.0.0.0"
nmap 10.1.0.10 -Pn -p 55132
on the RPiSoapySDRServer.exe --bind
nmap 10.1.0.10 -Pn -p 55132
on the RPi--bind="0.0.0.0"
work around.nmap 10.1.0.10 -Pn -p 55132
on the RPiI stopped digging after this, but if it would help to dig more let me know and I am willing to help to have someone else avoid this headache.
Thank you
The text was updated successfully, but these errors were encountered: