search

pothosware / SoapySDR

Vendor and platform neutral SDR support library.
https://github.com/pothosware/SoapySDR/wiki
Boost Software License 1.0
1.1k stars 176 forks source link

Unable to find devices on SoapyRemote on WSL2 #345

Closed FenixC4 closed 2 years ago

FenixC4 commented 2 years ago

I have configured my Windows 11 system to have a SoapySDRServer setup on Windows system and SoapySDR with SoapyRemoteModule built on WSL2. When I start the Server I am able to connect to it from Windows system itself and other deviecs in the network, however I am unable to connect to it from WSL2

image

image

image

What should I do to make it work ?

zuckschwerdt commented 2 years ago

Does SoapySDRUtil --info on WSL show the driver? (since you are using ./SoapySDRUtil it looks like things aren't installed?)

FenixC4 commented 2 years ago

I'm using ./SoapySDRUtil . because I have it installed in custom directory, I have done the same on my Ubuntu Laptop and it works just fine.

image

And as you can see it shows the driver

zuckschwerdt commented 2 years ago

Would have been too easy, right ;) Next guess: with WSL2 the subsystem is a VM, the network interface is mapped to the host (Windows), but since it's external to the host it might need to pass through the firewall? If you want to cut the remote client out, try socat. On WSL a socat - tcp:192.168.1.109:1234 should connect and the SoapySDRServer should show that connection.

FenixC4 commented 2 years ago

Ok, so I went down the rabbit hole and resolved the issue. It was all down to Windows's firewall. First I found out that by default Windows doesn't allow WSL to connect to it in any way, so that event pings won't reach Windows system.

By using this command New-NetFirewallRule -DisplayName "WSL" -Direction Inbound -InterfaceAlias "vEthernet (WSL)" -Action Allow you allow connections to be made from WSL to Windows machine. Since it only uses the HyperV adapter it is safe and closed from outside connections.

Next I had to add rules both Inbound and Outbound for the SoapyRemote itself since by default it got somehow blocked. After adding these rules everything works just fine.