Remote station design: rig-side hardware, VPN vs. port forwarding, latency budgets, and rule compliance
- Replies 2
- Views 38
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Chad 1 post
-
Mod_Chrissy 1 post
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.
Link to comment
https://www.hamradiobase.com/forums/topic/10988-remote-station-design-rig-side-hardware-vpn-vs-port-forwarding-latency-budgets-and-rule-compliance/Share on other sites