Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Remote station control: choosing between RS-BA1, SCU-LAN10, RigPi, Flex SmartLink and Kiwi/WebSDR, and what to sort out first (security, latency, rules)

ci_cover.jpg

Remote operation gets discussed as if it were one thing, but it is really several different setups that share the word "remote". Which one you pick decides your security exposure, your latency budget and your regulatory position. I'd like to compare notes by layer.

1. Receive-only remote. WebSDR (the Twente-style software by PA3FWM) and KiwiSDR are browser-based receivers. You aren't controlling your own radio, you are borrowing someone else's receiver and antenna. They are useful for checking propagation, seeing whether your signal is getting out (if you know a receiver near your target path), and for TDoA-style location work with several Kiwis. No transmit means no control-operator questions, but the shared receivers have user limits and you can't choose the antenna.

2. Radios with a network stack built in. FlexRadio is the clearest case, because the radio is already a network device. SmartSDR runs on the client, and SmartLink handles authentication and connection setup over the internet. The IC-7610 is similar in spirit: it has a LAN port, and Icom's RS-BA1 software on the client talks to it directly. As I understand it, RS-BA1 defaults to a small set of UDP ports (commonly documented as 50001 to 50003 for control, serial and audio), but check your own manual before you forward anything. The open-source wfview project is another client for Icom's LAN protocol, so you aren't locked into one program.

3. A server box next to a radio that wasn't designed for it. The Yaesu SCU-LAN10 sits between the radio and your network and carries CAT and audio. A RigPi (Raspberry Pi running Hamlib-style rig control plus a web interface) covers a lot of older radios with a CAT port. In both cases you still need to decide where digital-mode software runs, how audio gets to you, and how PTT behaves if the connection dies mid-transmission.

4. Hosted or shared remote bases. RemoteHams.com is one of the services built around connecting operators to remote stations. Whether you are renting time or sharing your own station, read the service's current terms and licensing requirements yourself. They change, and I'd rather not guess at them here.

Three questions I'd like opinions on:

Security: is a VPN (WireGuard or similar) into the home network the right default, rather than port-forwarding the radio's protocol? Raw CAT or rigctld exposed to the internet has no meaningful authentication.

Latency: for SSB and FT8, a few hundred milliseconds is usually tolerable, but QSK CW and fast contest exchanges are another matter. Where does each of these tools start to hurt?

Rules: the operator's licence privileges, the station's location and the control-point requirements don't always line up. What should people check before they go on the air from a different country or call area?

  • Replies 2
  • Views 14
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On security, I'd treat the radio and its LAN interface like an IoT device that was never meant to face the internet. Put it on its own VLAN or at least its own subnet, keep the firmware current, and reach it through a VPN endpoint rather than forwarding UDP ports. WireGuard is lightweight and holds up well on mobile and hotel connections. Overlay-network tools that avoid port forwarding also help if you're behind CGNAT, where you can't forward anything anyway.

If you must publish a web interface (a RigPi front end, for example), put it behind a reverse proxy with TLS, strong unique credentials and rate limiting. Never expose rigctld or a raw serial-over-IP bridge. Anyone who reaches that port can change frequency or key the transmitter.

The other half of security is the physical station. A remote site needs a way to power-cycle gear (a network-switchable PDU on a separate path from the radio's own link), a watchdog that drops PTT if the session ends, and ideally some indication of SWR, temperature and antenna switch state. If an amplifier is involved, think hard about what happens if the tuner or antenna relay is in the wrong position when you connect.

On the latency question, SmartLink and RS-BA1 are designed for audio streaming, so they behave better than a generic remote desktop plus a virtual audio cable. But anything that passes the panadapter or waterfall will use much more bandwidth than the audio alone. Lower the display rate if your link is marginal.

  • Moderators

For latency, separate delay from jitter. A constant 150 ms is workable for SSB because you adapt to it. Variable delay and packet loss are what make voice choppy and PTT unpredictable. Wired Ethernet on the client side beats Wi-Fi for that reason, and a larger audio buffer will often sound better than a minimal one.

For FT8 and similar modes, a common approach is to run WSJT-X (or whatever decoder you use) on a machine at the station and remote-desktop into it, rather than streaming audio across the internet. The time-critical part then stays local, and you only need the screen link to be tolerable. Just keep the server clock disciplined.

For CW, sending by keying over the internet in real time is the hard case. It is generally better to send from a keyer or text-to-CW function at the station end, so timing is generated locally and your link only carries characters. Full break-in with a long path will never feel like being at the key.

On the rules, I'd read the actual regulations of both places involved, not summaries. In the US, Part 97 covers station control and the control operator's responsibilities (sections on control types and on telecommand are the ones to look at), including requirements about limiting transmission if the control link fails. Other countries have their own licence conditions, and some tie the station licence to a named address or require the operator's privileges to match the station's location. Reciprocal or visitor licensing doesn't necessarily cover remote operation either. Contest and award sponsors also publish their own remote-operation rules, which can differ from the regulator's. Check them before you plan a weekend around a particular station, because the answer may not be what you expect.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.