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 design: VPN or port-forward, where to put the latency, and what the rules expect from you

ci_cover.jpg

I'd like to pull the scattered remote-operation questions into one technical thread. The same ones keep coming up: which radio ecosystem to build around, how to keep the control link off the open internet, what latency really breaks, and what the licence conditions require once the transmitter is somewhere you aren't.

Receive-only versus full remote. WebSDR and KiwiSDR are different from remote control. A WebSDR (the Twente-style software many clubs and individuals run) and a KiwiSDR (a wideband HF SDR covering roughly 0 to 30 MHz) let many listeners share one receiver through a browser. They are useful for checking propagation, hearing your own signal from elsewhere, or monitoring a beacon. You cannot transmit through them, so none of the control or licensing questions below apply. Remote-base services such as RemoteHams.com sit in a different category because a transmitter is involved. Check the host's current documentation and access rules for how a given station is shared or controlled, since those details can change.

Radio-side options. The Icom IC-7610 has a LAN port, and Icom's RS-BA1 software handles control and audio from a remote PC. Open-source projects such as wfview also support certain Icom LAN radios, so check the current compatibility list for your model. The Yaesu SCU-LAN10 is a network interface unit for supported Yaesu radios, which means the model and firmware need checking before you buy. FlexRadio takes a different approach: the SDR runs on its own network node, and SmartSDR with SmartLink is the vendor's route to operating it over the internet. RigPi, a Raspberry Pi-based controller, is a common choice for the ancillary jobs: Hamlib-based rig control, antenna switching, rotator control and relays, usually with a web interface. A typical station uses one of the radio-native options plus a small controller for everything the radio doesn't handle.

Security. The easy way to get remote access working is to forward the radio's control and audio ports on the router. The manuals list the default UDP ports for these radios, but check them for your model. I'd avoid that. Consumer radio firmware was not written to face the internet, and a forwarded CAT or audio port is an attack surface. The usual better pattern is a VPN, such as WireGuard or an overlay network, terminating on a small always-on device at the station, with the radio only reachable from the inside. Beyond that: put the radio, amplifier and controller on a separate VLAN or at least a separate subnet, change every default credential, keep the controller's OS patched, and think about what happens if your ISP uses CGNAT, which breaks inbound connections and may force you to use an outbound tunnel to a relay.

Latency and jitter. Round-trip time matters less than people expect, but jitter and buffering matter a lot. SSB and FM conversation tolerate a few hundred milliseconds, though PTT feels sluggish. CW is harder: sending keying over the network means timing is vulnerable to jitter, so the better designs send text or buffered keying events to a keyer at the station instead of streaming raw key-down and key-up. Full break-in QSK over a long path is mostly not realistic. For FT8 and similar modes, run the decoder and the clock at the station side, because the clock accuracy that matters is the one on the radio's end. Wired Ethernet on both ends beats Wi-Fi almost every time.

Rules. This varies by country, so treat this as a checklist and not legal advice. In general, the licensee remains responsible for every emission, even when remote. You need a way to shut the transmitter off if the link drops, which in practice means a TX timeout or watchdog, SWR and temperature protection, and a way to power-cycle remotely. The operator's licence class and the station's location may both affect which bands and powers are allowed, and operating a station in another country can involve reciprocal-licence or CEPT-type rules. Contests and awards often have their own definitions of station location and remote operation, so read the current rules for each one. On encryption, the concern in most rules is the on-air emission. Tunnelling the control link over a VPN is a different matter, but confirm with your regulator if you are unsure.

Where do you draw the line between a quick RS-BA1 or SmartLink setup and a proper VPN-based station? What failure modes have people planned for before leaving a station unattended?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the VPN question, I'd treat it as the default and port forwarding as the exception. The vendor software is convenient, but the radio's own network stack becomes the thing the internet sees. With a VPN endpoint on a Pi or a router, you expose one well-understood service, you can restrict it by key, and the radio never sees a stranger's packet. The trade-off is added latency from the tunnel and any relay, and some audio apps are fussy about MTU, so test with the real software before you commit.

The other thing I'd add is a dead-man design. Do not rely on the remote operator's software to unkey the transmitter when the link dies. Have something at the station that independently drops PTT if packets stop arriving, plus a hard TX timeout in the radio itself. A controller like RigPi with a web relay can power the amplifier off, but it should be on a separate path from the radio so a single network fault does not leave you without control of both.

  • Moderators

One thing worth separating is audio latency from control latency. Many people blame the internet when the real delay is buffering in the software. Most remote audio clients let you set a jitter buffer. A small one gives snappy audio on a clean wired link but chops up on a congested one, and a large one sounds smooth but makes PTT turnaround feel slow. Try it at your worst time of day, not just when the network is quiet.

For CW, a station-side keyer is the sensible answer. If you only ever do digital modes, the problem mostly disappears because the radio, decoder and clock are all together. For contesting, I'd read the rules for each contest before building anything, because some limit where the transmitter and receiver can be relative to each other, and some treat a remote station differently from a local one. It is easy to build a great remote station and then discover it is not eligible for the category you wanted.

On the SCU-LAN10 and Icom RS-BA1 side, check the firmware and software versions together. These interface units and the radios' firmware have been updated over time, and mismatched versions are a classic cause of audio dropouts that look like network trouble.

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.