Building a remote HF station: radio-side options, VPN vs. port forwarding, latency budgets and what the rules expect
- Replies 2
- Views 29
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Mike 1 post
This thread is for comparing approaches to remote station control, from a single rig at a second QTH to a shared remote base. The basic question is how you get audio, CAT/CI-V and PTT across the internet reliably, safely and legally. Here is a rough map of the options, with some questions to start the discussion.
1. Radios with native network support. The Icom IC-7610 has a LAN port and works with Icom's RS-BA1 remote software, so the rig itself handles the network side of control and audio. FlexRadio takes this further: the radio is already a network device, and SmartSDR with SmartLink can reach it from outside the home network. Yaesu's SCU-LAN10 adds a network interface to supported models, so check Yaesu's compatibility list for your exact radio and firmware instead of assuming. In all three cases the vendor's client is the simplest path. Third-party clients such as wfview exist for some Icom radios if you want something different.
2. A small computer at the radio. A RigPi (Raspberry Pi-based) or a mini-PC running Hamlib, a sound interface, and a remote audio tool covers radios with no LAN port. It also gives you a place to run relay control, an antenna switch, a rotator, and a watchdog. The weak spot is that rigctld has no authentication. Port 4532 should never be reachable from the internet.
3. Receive-only tools as a sanity check. A WebSDR or KiwiSDR near your remote location is useful for checking whether a band is actually open, or whether your signal is getting out. They are not control systems, but they make a good second opinion on what your transmitted signal sounds like. Hosted remote-station services such as RemoteHams.com are a different model again: you use someone else's station under their access rules. Read their current terms, since I am not going to quote them from memory.
Security basics worth agreeing on. Avoid forwarding the radio's ports straight to the internet. A WireGuard or other VPN into the remote LAN, or a mesh VPN, is much safer, and the radio, Pi and PC then stay on private addresses. Put station gear on its own VLAN or at least its own subnet, change every default password, keep router and Pi firmware updated, and turn off UPnP unless you know exactly what it is opening. If a vendor's cloud relay such as SmartLink is used, it is still worth understanding what it exposes and what account security it relies on.
Latency and jitter. SSB is usually forgiving of a few hundred milliseconds of round-trip delay, though break-in and pileup work feel sluggish. CW is harder: local keying with the keyer at the radio end is often better than sending key-down events across the net. Jitter and packet loss hurt more than a steady delay, so a wired connection at both ends is worth the effort. For FT8 and similar modes, running the decoder at the radio end avoids audio-stream timing issues, and both ends should be time-synced.
Fail-safes. If the link drops while you are transmitting, what happens? A remote station should have a transmit time-out, a way to cut the carrier locally or by independent path, a remotely controllable power switch, SWR and temperature monitoring, and positive feedback on antenna and tuner state. A camera or a status page helps too.
Rules. Remote control is generally allowed, but the details depend on the country. Usually the licence requirements and band privileges of the station's location apply, there must be an identified control operator, and the station must be able to be shut down promptly. Some countries have extra requirements for automatic or unattended operation or for operating from abroad. This is a general outline, not legal advice, so check your national regulator and the licence conditions for both the operator and the station location.
Questions for the thread: Are you using the vendor client or a Hamlib-based setup? How are you handling remote access: VPN, cloud relay or port forwarding? And what is your plan if the link dies mid-transmission?
Link to comment
https://www.hamradiobase.com/forums/topic/11513-building-a-remote-hf-station-radio-side-options-vpn-vs-port-forwarding-latency-budgets-and-what-the-rules-expect/Share on other sites