Ham Radio and Software-Defined Networking: When IP Meets RF

Somewhere around 2015, I realized my two professional worlds — network engineering and amateur radio — were converging faster than I expected. The same principles driving enterprise SDN (software-defined networking) were showing up in ham radio mesh networks, remote station control, and digital infrastructure. If you come from an IT background, ham radio networking will feel strangely familiar. If you come from traditional ham radio, this is where things get interesting.

What SDN Actually Means for Hams

In the enterprise world, SDN separates the control plane (the brains deciding where traffic goes) from the data plane (the actual packet forwarding). The network becomes programmable, flexible, and centrally manageable.

In ham radio, we're seeing a parallel evolution:

• Traditional repeaters = static, hardware-defined routing (your signal goes in, comes out, done)
• Linked repeater systems (AllStar/EchoLink) = early software control over audio routing
• AREDN mesh networks = full IP networking with dynamic routing over RF
• Modern remote stations = complete separation of the operator interface from the radio hardware

The trend is clear: the intelligence is moving from hardware into software, and RF is becoming just another transport medium in a larger networked system.

AREDN: The Ham SDN Platform

AREDN (Amateur Radio Emergency Data Network) is the most mature example of software-defined networking in amateur radio. It takes commercial Wi-Fi hardware (Ubiquiti, MikroTik, TP-Link), reflashes it with custom firmware, and creates a self-healing mesh network operating on amateur frequencies in the 900 MHz, 2.4 GHz, 3.4 GHz, and 5.8 GHz bands.

How It Works

Each AREDN node runs a Linux-based firmware with OLSR (Optimized Link State Routing). Nodes discover each other, calculate optimal paths, and route IP traffic dynamically. Add a new node? The mesh reconfigures itself. Lose a node? Traffic reroutes around the failure.

The network stack is standard TCP/IP. Any application that works over Ethernet works over AREDN: VoIP phones, video cameras, web servers, file shares, even PBX systems.

Practical AREDN Setup

A basic AREDN node costs about $50-80:

• Hardware: MikroTik hAP ac lite (for 2.4/5 GHz) or Ubiquiti Rocket M5 (for 5 GHz point-to-point)
• Antenna: Depends on application — omnidirectional for local mesh, sector for coverage area, dish for long-haul links
• Power: PoE, typically 12-24V DC

Flashing is straightforward — download the AREDN firmware for your specific hardware, flash via TFTP or web interface, and configure via the built-in web UI. The node announces itself to neighbors automatically.

Our county ARES group runs 14 AREDN nodes across hilltops and public safety buildings. During a wildfire drill last year, we carried real-time camera feeds, VoIP traffic between command posts, and a shared mapping application — all over amateur radio spectrum with zero commercial infrastructure dependency.

Bandwidth Realities

ARDEN on 5.8 GHz with 20 MHz channel width delivers roughly 30-80 Mbps on short links (under 5 km line-of-sight). Longer links with higher gain antennas can maintain 10-20 Mbps at 20 km.

On 2.4 GHz with 5 MHz channel width (to fit within amateur allocations): expect 2-5 Mbps. Still enough for compressed video and VoIP.

900 MHz links in Part 97 spectrum: 1-3 Mbps but much better penetration through foliage and buildings.

IP Over HF: The Slow Lane

At the other extreme, hams have been running IP over HF since the 1980s. Modern approaches include:

VARA HF: Up to 8 kbps on a single HF channel. Used primarily for Winlink email but capable of carrying any TCP traffic. The protocol adapts to channel conditions in real-time.

New Packet Radio (NPR): A 70cm digital data system capable of 200-500 kbps. Uses custom modems and a TDMA structure more similar to LTE than traditional packet radio. Still experimental but operational in several countries.

HF mesh concepts: Projects like the Xiegu XPA125B's built-in networking features hint at where HF data is heading — radios that are network-aware from the ground up, not just audio devices with a modem bolted on.

Building a Ham Radio Network: Architecture Principles

Layer Model

Think of your ham radio network in layers, just like enterprise networking:

Physical layer: The RF links — frequency, power, antenna, propagation Data link layer: The modulation and framing — AREDN's 802.11 variant, AX.25, VARA Network layer: IP routing — OLSR in AREDN, static routes in simple setups Transport layer: TCP/UDP — standard protocols Application layer: What you actually want to do — email, voice, video, remote control

This layered approach means you can swap components independently. Running VoIP? You don't care whether the underlying transport is 5.8 GHz AREDN, 70cm NPR, or a 2-meter packet link. The application doesn't need to know.

Addressing and DNS

ARDEN assigns addresses from the 10.0.0.0/8 private space based on your callsign. Each node gets a predictable hostname: callsign-nodename.local.mesh. A distributed DNS system resolves names across the mesh.

For standalone ham networks, I recommend:

• Use 10.x.x.x for all ham network addressing
• Document your addressing scheme (write it down!)
• Run a local DNS server on at least one node
• Keep your ham network completely separate from your home/internet network (bridging is asking for trouble, both technically and legally)

Network Services Worth Running

Once you have a mesh running, deploy services that are actually useful in an emergency:

PBX (Private Branch Exchange): FreePBX on a Raspberry Pi gives you a phone system. In a disaster, plug in VoIP phones at any AREDN node and you have comms without cell service.

Chat: Run a Mattermost or Rocket.Chat server. Text communication uses minimal bandwidth and works even on degraded links.

File sharing: Nextcloud gives you a shared drive accessible from any node. Upload situation reports, maps, photos — available to all connected users.

Video: IP cameras at key locations, viewable from any node. Use RTSP streams rather than cloud-dependent cameras.

Winlink gateway: Bridge your mesh to the HF Winlink network for long-haul email when internet is down.

SDN Concepts Applied to Ham Infrastructure

Programmable Repeater Linking

AllStar Link runs on Linux and can be scripted. You can write logic that:

• Links repeaters during emergencies automatically when triggered
• Creates time-based connections (link to the state net at 7 PM, disconnect at 8 PM)
• Routes audio based on DTMF commands or network events

This is SDN thinking applied to analog repeaters — the control logic is in software, separate from the RF hardware.

Remote Station Control as Network Service

A modern remote HF station (using RemoteHams, SmartSDR with SmartLink, or Win4IcomSuite) is essentially a network service. The radio hardware provides an API, the control software is a client, and the network (whether internet, mesh, or VPN) connects them.

Design considerations:

• Latency: <150ms for CW, <300ms for SSB, <500ms for digital modes
• Bandwidth: 200-500 kbps for audio streaming, 2-5 Mbps for full spectrum display
• Reliability: QoS tagging on your network to prioritize radio traffic over background data

Automation and Monitoring

Run SNMP monitoring on your AREDN nodes. Tools like LibreNMS or Zabbix can alert you when links degrade, nodes go offline, or bandwidth drops below usable thresholds. Apply the same network monitoring discipline you'd use at work.

I run a Grafana dashboard showing all my AREDN link SNR values, throughput, and node uptimes. When a link starts degrading (usually due to foliage growth blocking the path), I see it before users complain.

Legal Considerations

Part 97 Requirements

All amateur radio networking must comply with FCC Part 97 rules:

• No encryption (except for spacecraft control): Your network traffic must be unencrypted. This means no HTTPS, no SSH, no VPN tunnels carrying encrypted payloads over amateur spectrum. Use encryption only on internet-connected portions.
• Station identification: Your callsign must be associated with your node and transmitted every 10 minutes.
• No commercial use: The network can't carry business traffic, even in emergencies.
• No obscuring content: All traffic must be openly readable. This is the biggest operational limitation.

Practical Implications

The encryption prohibition means:

• Web servers must be HTTP, not HTTPS
• Email can't use TLS
• No WPA on Wi-Fi (AREDN uses no encryption by design)
• Video streams must be unencrypted

This limits what applications you can directly port from the internet, but for emergency communications purposes, it's rarely a practical problem. You're not running a bank over ham radio.

Where This Is Heading

The future of ham radio networking looks like:

• Higher bandwidth on microwave bands: 10 GHz and above offer huge spectrum with line-of-sight links
• Cognitive radio: Software-defined radios that sense spectrum availability and adapt (think of it as SDN applied to the physical layer)
• Integration with LoRa/Meshtastic: Low-power mesh for telemetry and short messages, AREDN for high-bandwidth backbone
• Network slicing: Different QoS for voice, video, and data over the same RF infrastructure

If you're a network engineer who's also a ham, you're in the perfect position to build the future of amateur radio infrastructure. The principles are identical — the medium is just more interesting.