Remote Shack: Control Your Amateur Radio Station from Anywhere

An antenna belongs where it works well. You belong where you live. Those two places are rarely the same, and remote operation grew out of exactly that gap.

The principle is simple: transceiver, amplifier, tuner and antenna live at a fixed site, and you reach them over the Internet. Three things travel down that link, and it pays to think of them separately from the start. First, control commands, meaning CAT: frequency, mode, PTT, filters. Second, audio in both directions. Third, optionally, spectrum and waterfall data. Most remote-operation problems are really a problem with exactly one of those three streams, and knowing which one is misbehaving is half the troubleshooting done.

Why bother

The most common reason is space. If you live on the third floor of a rented flat, a three-element Yagi is not going on the balcony, and depending on the house rules neither is a wire. What is legally possible and what is not, we unpacked in Antennas and tenancy law in Austria. A site in the countryside, at your brother's place, at a cabin or at a club colleague's house solves the problem without you having to move house.

The second reason is the noise floor. In built-up areas, 40 metres in the evening will happily sit at S7, and that is rarely down to one single source. It is the sum of switching supplies, LED drivers, PV inverters and the neighbour's charger. How to hunt those down is covered in our EMC guide. The catch is that some of it simply cannot be switched off, and at that point a quiet site ten kilometres away is worth more than any preamp.

Two more reasons get discussed less often. One is time: if you work away from home during the week, remote access means being on the air on a Tuesday evening rather than only at weekends. The other is access. For operators who can no longer manage the loft or the cellar easily, remote operation is not a convenience feature. It is often the difference between still being active and no longer being active.

Start for free: wfview

If you own an Icom station, getting started costs nothing. wfview is free open-source software for Windows, macOS and Linux, and it has become the obvious answer to the question of where to begin.

For radios with a built-in network port, meaning the IC-7610, IC-9700, IC-705, IC-905, IC-R8600 and, on the Kenwood side, the TS-890S, wfview connects straight to the radio's IP address. For everything else, above all the widespread IC-7300, there is server mode: a computer at the site hangs off the transceiver over USB and becomes the network device itself. That can be an old laptop or a Raspberry Pi.

Three points matter here, and they are stated plainly in the manual. wfview uses three UDP ports, 50001 for control, 50002 for receive audio and 50003 for transmit audio, and those port numbers must not be remapped, because they are part of the protocol itself. For the codec, Opus at one channel is the right choice, using four to ten times less bandwidth than PCM depending on the comparison. And the user management is deliberately basic: the manual says outright that passwords are not well encrypted and that you should not use a sensitive password there. Which is exactly why wfview belongs behind a VPN rather than on the open Internet.

Typical audio latency, according to the project, is under 75 ms on a LAN and under 200 ms over the Internet. For SSB that is plenty. For CW it gets marginal depending on your link. More on that below.

Play

Worth a footnote because of where it points: wfview now has a headless fork called wfweb that makes the station operable from a browser, audio and digital modes included. If you would rather not install client software at all, that is an interesting direction.

The manufacturer solutions

FlexRadio SmartLink

The FLEX-6000 series is popular for remote work because the radio is fundamentally a network device with an antenna socket. SmartSDR looks the same on the LAN as it does over the Internet, audio, waterfall and control share one connection, and the latency is remarkably low.

One widespread claim about it is wrong, however, and an earlier version of this article repeated it: SmartLink does not generally avoid port forwarding. FlexRadio's own helpdesk states that the router at the station site must be able to accept an incoming connection from the Internet, typically through port forwarding. SmartLink tries to set this up automatically via UPnP, which often works and often does not. When it does not, you end up either forwarding ports manually or reaching for one of the overlay networks described below.

Icom RS-BA1 and the IC-7760

Icom's RS-BA1 version 2 is the in-house solution, split into a server part at the site and a client. It does more than wfview when it comes to integration with the Icom world, and it costs money for the privilege. If you own an IC-7610 anyway, try both and decide.

More interesting is what Icom did with the IC-7760. The radio comes in two parts, a control head and an RF deck, and the two talk to each other over LAN, either within the house or across the Internet. A three-metre control cable ships with it; for anything longer you use an ordinary network cable. Up to five control heads can be registered with the RF deck, with only one taking control at a time. Icom states that the radio adjusts its buffer under network delay and jitter so that CW keying stays precise. That is the genuinely interesting part of this architecture: the RF deck can finally sit where it belongs, close to the feed point, rather than where there happens to be desk space.

Kenwood: KNS, ARCP-890 and ARCP-990

Kenwood calls its system the Network Command System, KNS for short. On the TS-890S, which has a network port built in, ARCP-890 controls the radio directly over LAN or Internet, with audio handled by the VoIP function built into both the radio and ARCP-890. In the classic arrangement you additionally need ARHP-890 as the host program and ARVP-10 for voice. For the TS-990S there is the corresponding ARCP-990.

What is no longer available

The RemoteRig RRC-1258MkII boxes from Microbit were the standard answer to the remote question for years, because they needed no PC and simply extended a radio's detachable control head across the Internet. They are no longer sold. They still turn up on the used market, and if you have a pair, keep them. As a new build, that route is closed.

Rolling your own with a Raspberry Pi and Hamlib

If you do not own an Icom, or you simply like building things yourself, free software gets you just as far. The skeleton has three parts.

Hamlib with rigctld handles control. The daemon attaches to the transceiver's serial or USB port and offers the CAT commands over TCP/IP, port 4532 by default. Programs such as WSJT-X, FLRig, CQRLOG or Gpredict connect to it across the network as though the radio were sitting next to them. Hamlib covers virtually any transceiver that has a CAT interface at all.

For audio, Mumble has proven itself, because it is designed for low latency and sounds good on little bandwidth. At the site the transceiver's AF is digitised through a USB audio interface; at the operator end it goes the other way into a microphone. Discord or TeamSpeak work too, but they are noticeably more sluggish, because they were built for conversations rather than for PTT.

For hardware, a Raspberry Pi from model 4 onwards is enough. Power draw stays in the five to fifteen watt range, which makes continuous operation realistic even on a solar supply. What that means for sizing a battery is in Akkublick. We collected further uses for a Pi in the shack in a separate article.

The advantage of this build is that every piece can be swapped individually. The drawback is that you are now looking after three services instead of one, and that debugging them across an Internet link teaches you how little fun that is.

Play

The networking problem nobody mentions: CGNAT

This is where most remote projects die, before they have properly started. Many Internet connections no longer get their own public IPv4 address; they share one with hundreds of other customers. That is called Carrier-Grade NAT, and it particularly affects mobile and LTE connections, which is exactly what you often have available at a cabin or a garden plot.

The consequence: port forwarding does not work. There is nothing to forward, because your router has no address that anyone outside could reach. You can write firewall rules for hours and nothing will change.

Finding out whether you are affected takes two minutes. Check which WAN IP address your router holds and compare it with the address a site like ifconfig.me reports. If the two differ, or if the WAN address starts somewhere between 100.64 and 100.127, you are behind CGNAT.

The answer is an overlay network. These services build the connection outward from both ends, which any firewall happily allows, and then connect your devices directly to one another. From the software's point of view it looks like a local network.

• Tailscale is the quickest to set up, builds on WireGuard and is free for personal use. We walked through a concrete example using the IC-705: IC-705 remote operation with Tailscale.
• ZeroTier does the same job with a slightly different philosophy and is equally common in the remote community, not least as the way out for FlexRadio setups stuck behind CGNAT.
• Plain WireGuard is the option without a third-party service in the middle. It does require that at least one of the two ends is reachable from outside, for example a small hosted server that both ends meet at.

One side effect worth taking: if everything runs through an encrypted tunnel anyway, half the security chapter takes care of itself.

Latency: what actually counts

The number everyone looks at is ping. Consistency matters more.

For SSB, anything under roughly 200 ms goes unnoticed. You feel the delay when switching, but it does not get in the way. CW is stricter: under 100 ms you can work properly, under 50 ms you barely notice a difference from local operation, and above that, listening to your own sending starts to become unpleasant. It is no accident that Icom explicitly advertises buffer adjustment for CW keying on the IC-7760. For FT8, FT4 and other digital modes, latency is practically irrelevant as long as the clocks are right, because decoding happens in fixed time windows regardless.

The real enemy is jitter, the variation in transit time. A link with a steady 150 ms is more pleasant than one bouncing between 40 and 180 ms, because every buffer has to be sized for the worst case. Packet loss above one percent shows up as dropouts in the audio and as stuck commands in the control path. If your router does QoS, the remote traffic deserves priority, especially if someone at home is streaming at the same time.

Bandwidth is usually wildly overestimated. Pure audio in both directions gets by on 128 kbit/s. With control, a camera and a modest waterfall you are at two to five Mbit/s. Only if you want the full waterfall of an SDR station at high resolution does it go into double digits. And that is upload at the station end, not download, because that is where the data comes from.

What has to be at the far end

The golden rule: anything you would have to touch when something goes wrong, you must also be able to touch remotely.

Top of the list is the network-controlled power strip. It is not a luxury, it is the insurance policy for the whole project. When the transceiver locks up or the router drifts into a strange state, a remote power cycle is the difference between a two-minute outage and a car journey. One thing matters here: the computer that controls the power strip must not itself hang off the switched side. That sounds obvious and is still regularly wired up wrong.

Next is a UPS, which helps less against long outages than against the brief dips after which a computer fails to come back up cleanly. Models with a network port can be monitored and can shut things down in an orderly fashion.

An IP camera with night vision sounds like a toy and is not. Being able to look at an SWR meter while sitting three hundred kilometres away answers questions no software will answer for you. Whether the rotator is actually turning, for instance.

On antennas, the fewer moving parts, the better you sleep. Remote switches are standard, both off the shelf and home-built with a relay board and a microcontroller. An automatic tuner at the site saves you retuning from a distance. Motor-adjustable antennas cover many bands on one cable, but they also bring a motor, which at minus fifteen degrees in January does exactly what motors do then.

And finally the watchdog. Something has to put the station into a safe state if the link drops mid-transmission. Without that mechanism, a crashed client can leave PTT asserted, and then you are transmitting a carrier until somebody drives out there. That is the point where remote operation stops being a hobby project and becomes a responsibility.

Security

A station reachable over the Internet is a transmitter somebody else could key. Treat it accordingly.

The short version: no open ports. Everything goes through a VPN or overlay network, and that means everything, including the camera and the web interface of the power strip. Those devices in particular are rarely built for a hostile network and often go years without firmware updates.

Then the usual obvious things that nonetheless need saying: unique passwords rather than reused ones, two-factor authentication where available, regular updates to the operating system and the VPN server. For monitoring, something small like Uptime Kuma is enough to tell you when the station stops answering. That is worth more than it sounds: you do not want to discover on Friday evening that nothing has been running since Tuesday.

If HAMNET is within reach, the whole connection path can be thought about differently. How that network is built is covered in HAMNET in Austria.

The legal position in Austria

Our earlier version was imprecise here, so let us go through it properly.

Remote operation is explicitly provided for in Austria. The TKG 2021 defines a remote station in § 3 Z 44 as "eine Amateurfunkstelle, die von einem Funkamateur fernbedient wird", an amateur station operated remotely by a radio amateur. And § 78a Abs 1 Z 5 records that "im Fall einer Remotefunkstelle die persönliche Anwesenheit des Inhabers der Bewilligung nicht erforderlich ist", meaning the licence holder need not be physically present. That is the decisive clause, because presence would otherwise be the sticking point.

The competent authority is the Fernmeldebüro, not the RTR. We got that wrong previously. The RTR handles plenty in the telecoms field, but amateur licences go through the Fernmeldebüro at fb.gv.at.

The Amateurfunkverordnung itself, correctly abbreviated AFV rather than AFU-VO, contains nothing specific on remote operation. What it does contain and what matters to us: § 5 Abs 1 ties the digit in the call sign to the federal state of the fixed location named in the licence. Remote shutdown capability is regulated in §§ 32 and 38, but for beacons and repeaters. And § 12 permits linking amateur stations by Internet technology within a narrow frame, namely for testing new transmission techniques. That is a different thing from accessing your own station, and the two get confused often.

In practice: it is the location of the transmitting equipment that constitutes the station, not where you happen to be sitting. If the radio is in Carinthia and you are in Hamburg, an OE8 station is on the air. Exactly what your licence requires for additional locations is best settled directly with the Fernmeldebüro before you build, not afterwards. We summarised the wider legal framework in Amateur radio legislation in Austria.

Remote in contests: read the rules

Logs get disqualified here regularly because somebody did not read the rules. In CQ WW, remote operation is permitted, but under a clear condition: the physical location of all transmitters, receivers and antennas must be at one station location. Remote receivers outside that location are not permitted. Category and licence limits apply unchanged.

So what does not work is monitoring your own signal through a WebSDR in Scandinavia while your antenna in Carinthia transmits. Individual contests do know tightly bounded exceptions. In CQ 160, for Single Operator Assisted, exactly one remote receiver within 100 kilometres of the transmitter site is allowed. Rules like these change, so the plain advice is to read the current rulebook before the contest.

Without a station of your own: the DARC remote stations

Worth mentioning because many people do not know it exists: the DARC runs a network of remote stations that members can use through a client program. A map shows which station is currently online. The requirements are DARC membership and a Class A licence; each session is limited to 60 minutes, after which you simply log in again.

For operators with no antenna options of their own, that is a realistic way of getting on the bands at all, and for everyone else a good chance to try remote operation before spending money.

Play

The order to do it in

1. On your own LAN first. Radio, computer, software, all in the house. If it is not clean there, it will not improve across the Internet.
2. Then the tunnel. Set up Tailscale or WireGuard and check that you can reach the station from a mobile network. Only once that stands does radio come back into it.
3. Then the fallback layer. Power strip, UPS, watchdog. Before the station moves to its final site, not after.
4. Only then move it. And test everything again at the new site, including a deliberately induced power failure. Pull the plug and see whether it all comes back up by itself.
5. Document it. IP addresses, ports, credentials, cabling, all on one page. At the moment you need it, you will be somewhere else with no access to the very box you would have to describe.

Conclusion

Remote operation is no longer an exclusive subject. With wfview, a Raspberry Pi and Tailscale, a working setup costs under a hundred euros in extra hardware, provided the transceiver speaks CAT. The expensive solutions buy you convenience and integration, not fundamentally more capability.

The real hurdles sit somewhere other than most people expect. They are not in the software but in the network, CGNAT above all, and in the question of what happens when you are not there. Plan the power strip and the watchdog in from the start and you have a station that runs. Save them for later and you have a project that keeps putting you in the car.

73 – your oeradio.at editorial team

---

Transparency notice

This article was researched and written with AI support (Claude, Anthropic) and revised on 21 September 2026. Sources included the wfview manual, the FlexRadio helpdesk, product documentation from Icom and Kenwood, the ÖVSV wiki on the framework for remote stations in Austria, the statutory texts in the RIS, the CQ WW rules and the DARC remote station project. The title image shows an antenna installation in a residential area (photo: Wikideas1, CC0, via Wikimedia Commons); the further photographs also come from Wikimedia Commons and are credited at each figure. Editorial responsibility and review rest with the oeradio.at team. We accept no liability for accuracy or completeness; legal questions in individual cases are for the Fernmeldebüro. Corrections and additions, from operators of their own remote stations too, are welcome at [email protected].