The SDR Server supports one or more SDR radios located at a remote location, the internet is used to connect the SDR Console to the server. Use the Server Manager (below) to configure and start the server (runs as a Windows service). The server also supports up to ten simulateneous connections (one radio per user), so the practical limit is your internet upload bandwidth.

To determine your upload bandwidth use one of the many websites such as which will gives results such as shown below.

The recommended minimum bandwidth is 2 MBps (two megabits), more is better as it allows a higher sample rate between the server and the console.

The server does not require a high-end computer - tests have successfuly concluded on a 32-bit Windows 7 laptop with a 2GHz Core2Duo processor, the CPU load typically less than 2%.

Data Format

The server sends IQ data (In-phase and Quadrature), this is the same data your SDR radio creates so you are effectively running a SDR radio with the internet between. By sending over IQ data you lose none of the features available when the radio is connected to your local computer.


Transmit support using the V3 server is not currently planned.






In the console you connect to a server in the same way you connect to a SDR radio only you search for a radio of type V3 Server (at the bottom of the search list).



Optionally add your server to the On-Air list of servers at if you allow public access to the server.


Server Manager

Use the Server manager to configure and diagnose the server. Start the Server Manager from either the Windows Start menu or the Tools pane of the Console's ribbon bar.



Public or Private?

To ensure your server is private (cannot be accessed from the internet):

  • Do not open the server port in your router,
  • Add a firewall entry in your router (if supported) to explicitly block access to the server port (the server uses TCP),
  • Do not enable the On-Air option (below).

To allow public access:

  • Configure your router to forward TCP on the server's port to the computer where the server is running,
  • Check firewalls (including Windows Defender Firewall) allow access on the server's port,
  • Enable On-Air (below) if you want an entry on

Firewalls and Routers

Configuring a server requires knowledge of:

  • Firewalls such as Windows Defender Firewall, and
  • Routers.


You will be required to follow these steps:

  1. Add an inbound rule in your firewall to allow incoming TCP connections on the port assigned to the server (usually port 50101).
  2. If using an ethernet-based radio (see below), add an inbound rule to allow UDP data from the radio to the server computer.


If accessing the server from the internet (a WAN connection) you will add a port forwarding entry for TCP on the server port (usually 50101) with the local IP of the computer where the server is installed. (It is recommended that the IP address of the server is fixed.)

Corporate & Hotel Problems

Sadly some companies and hotels don't like employees and guests accessing dubious servers, it is quite common for access to your server to be blocked while you are at work or on holiday. 

Ethernet Radios & Firewall

If you are using a radio with an Ethernet connection such as:

  • NetSDR,
  • CloudIQ,
  • Afredi

and do not see any data in the console's waterfall then the UDP data from the radio is probably blocked by a firewall, for example Windows Defender. To enable UDP data from the radio you must add an inbound firewall rule to allow UDP on the Radio's port to SDRServerService.exe from either the radio's address or any address on the local LAN .



Public/WAN IP

Normally your ISP will assign you a public IP address, you see this in your router settings; an example from an ASUS RT-AC3200 is shown below. To avoid the address changing you should have a static IP address. Most ISPs allow you to purchase a static IP address (keeping the same IP address) for a small fee, for example £5 one-off from plusnet in the UK.