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 412.9 km/s
Aurora 1
Updated 14:00 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: rig-side hardware, VPN vs. port forwarding, latency budgets, and rule compliance

ci_cover.jpg

Remote operation covers a lot of different setups under one label, and the right design depends on which one you mean. A few common categories:

Receive-only remotes. WebSDR and KiwiSDR nodes are shared receivers that you listen to through a browser. They are useful for checking propagation, hearing your own signal at a distance, or comparing antennas. They can't transmit, so none of the licensing questions about control operators apply to them. KiwiSDR coverage is typically HF up to about 30 MHz, and the audio you hear is subject to the node owner's bandwidth limits and user slots.

Your own transceiver at a remote QTH. This is where it gets interesting. Options include the Icom IC-7610 with RS-BA1 (or other Icom-supported remote software), a Yaesu radio with an SCU-LAN10 network unit (check the manual for which models it supports and what it exposes, such as CAT and audio), a FlexRadio using SmartSDR with SmartLink, or a generic radio paired with a small computer such as a RigPi, which wraps Hamlib-style rig control, audio, and a web interface around a Raspberry Pi. Each approach moves the rig-side logic to a different place, and that affects how much you have to trust and secure.

Shared or hosted remote stations. Services like RemoteHams.com let operators connect to stations hosted by other people. Whether you can use one depends on your license class, the host's rules, and the regulations of the country where the transmitter sits. Read the terms carefully rather than assuming access equals privileges.

Here are the design points I'd like feedback on.

1. Network exposure. The worst setup is forwarding a radio's control port, or an RDP/VNC port, straight to the internet. Radios and their companion boxes are not hardened network devices. A safer pattern is a VPN endpoint, either WireGuard on a router or a mesh VPN overlay, with the radio and its controller sitting on a separate VLAN that only the VPN can reach. Keep firmware current on the router, the controller, and the radio, and disable UPnP unless you know exactly what it is opening. FlexRadio's SmartLink and similar vendor services exist for convenience, so understand what they require (port mappings, account authentication) before enabling them.

2. Latency and jitter. Raw round-trip time matters less than how steady it is. For SSB, 100 to 200 ms of one-way delay is tolerable for most people, though it makes break-in conversation awkward. For CW, the better approach is to send keying as text or timed events to a keyer at the rig side instead of streaming key-down and key-up in real time. Digital modes like FT8 care more about clock accuracy than latency, so run the decoding at the remote end or keep both ends tightly synced. Wired Ethernet on both sides beats Wi-Fi, and bufferbloat on a home uplink can ruin audio during uploads, so consider enabling smart queueing on the router.

3. Fail-safes. Assume the link will drop mid-transmission. You want a hardware or software watchdog that unkeys the transmitter if the connection is lost, a remotely switchable power strip that is not on the same network path as the radio, a transmit timeout, and SWR or antenna-tuner protection so an automatic tuner or antenna-switch fault can't leave the amplifier into a bad load. If you run an amplifier remotely, interlocks and temperature monitoring deserve serious thought.

4. Rules. Details vary by country, so check your regulator's text rather than relying on forum summaries. In general, the licensee remains responsible for the transmissions, the control operator must be able to shut the station down, and the rules of the country where the transmitter is located usually apply, along with your own license privileges. In the U.S., remote control of a station falls under the Part 97 control-operator and station-control provisions, and the location of the station, not the operator, matters for things like contest categories and some power limits. Contest sponsors and awards such as DXCC have their own remote-operation rules, so check those before you operate remotely.

What are people running at the rig end, and how are you handling the network boundary? I'm especially curious about IC-7610 versus Flex for remote use, and whether a RigPi-style controller is worth it over vendor software.

  • Replies 2
  • Views 38
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the vendor-versus-DIY question: the main practical difference is where audio and CAT get packaged. With RS-BA1 or SmartSDR, the vendor decides the codec, ports, and authentication, which makes setup easier but gives you less room to change anything. A RigPi or a similar Pi-based box lets you use whatever radio you like and add things like band-decoder outputs, antenna switch control, and a local keyer, at the cost of more maintenance. You become the one patching the OS.

For the network side, I'd put the rig, controller, amplifier controller, and switch on their own VLAN, allow only the VPN subnet into it, and block outbound internet from everything except what needs it (NTP, for example). That way, even if one of these devices has a vulnerability, it can't be used as a foothold into the rest of the house network.

  • Moderators

One thing worth separating is the CW question. Streaming key-down and key-up over a jittery link produces uneven timing, which is why a lot of remote setups send text or timing packets to a keyer at the station instead. If you're mostly SSB or digital, that matters less, but the same logic applies to PTT: put the sequencing (PTT, amp relay, antenna switching) at the remote end so a late packet can't leave you transmitting into the wrong antenna.

On rules, I'd also suggest keeping a short written operating plan for the station: who the control operator is, how it shuts down on a link failure, and how you'd reach someone physically at the site. It isn't a legal requirement everywhere, but it forces you to answer the questions a regulator, a contest committee, or a landlord might ask. And if you plan to use a hosted service or operate in another country, read the host's terms and that country's license conditions first, because a remote contact doesn't change which rules apply.

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.