Remote station design: VPN or port-forward, where to put the latency, and what the rules expect from you
- Replies 2
- Views 27
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
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?
Link to comment
https://www.hamradiobase.com/forums/topic/11393-remote-station-design-vpn-or-port-forward-where-to-put-the-latency-and-what-the-rules-expect-from-you/Share on other sites