`SoapySDRUtil --find="remote=a.b.c.d"` instantly throws `No devices found! ` without trying to send a packet. about soapyremote HOT 2 CLOSED

The --find in SoapySDRUtil uses SoapySDR::Device::enumerate() which for SoapyRemote is here:
https://github.com/pothosware/SoapyRemote/blob/master/client/Registration.cpp#L51

Can you increase the verbosity (SOAPY_SDR_LOG_LEVEL=DEBUG SoapySDRUtil ...) to see "SoapyClient querying devices for %s" and possibly "SoapyRemote::find() -- connect(%s) FAIL: %s"?

from soapyremote.

Well that's a ginormous relief! Today the same command is working, successfully enumerating the remote which has the SDR plugged in with SoapySDRServer --bind running from this laptop running a VPN to the remote network and on a different broadcast domain, when the IP is provided. I'm not sure why it's working today and could only potentially point at a recent update on each machine perhaps quietly fixing something. I will keep an eye open for if this happens again.

Trying to use this remote in GQRX seems to 'pause' every second or so either as some kind of underrun or and intolerance to the latency/throughput of funneling raw RF traffic from the remote over Soapy. This is over a low latency, high throughput fibre link though and selecting the lowest SDR sampling rate (240000) doesn't seem to fix the issue. I will look into this on my end as I know this problem does not happen over a 1gbps LAN of sub-1ms-latency.

from soapyremote.