From $106 to Battlefield-Grade: Building Your Own IP Mesh Radio

Table of Contents

TL;DR

A $106 kit can replace a $20 000 military router.
Powered by a Raspberry Pi 4 and a HaLow module, it delivers 15 Mbps on a single channel and up to 32.5 Mbps in the best case.
The device runs ATAC, Mumble, push-to-talk, and even a Starlink back-haul for internet.
WPA3-SAE encryption keeps the network secure.
You can scale from 2 nodes to a neighborhood-wide mesh in a few hours.

Why this matters

Every tactical operator has the same pain point: cost, latency, and bandwidth. A commercial military radio can cost more than $20 000 and takes months to procure. Even if you buy one, you’re stuck with a single, static link that can’t adapt to a rapidly changing battlefield.

I’ve seen teams in the field scrambling to set up a makeshift radio with a single Wi-Fi hotspot. The signal would drop after the first tree, the range was only a few hundred feet, and the latency made voice chatter impossible. That’s why a low-cost, open-source mesh radio is a game changer.

Core concepts

Mobile Ad Hoc Networks (MANETs)

A MANET is a self-configuring network where every node can forward traffic for every other node. There’s no central base station; the mesh creates its own routing tables using the 802.11s standard and the BATMAN-adv kernel module. In practice, this means if one node goes down, the others simply route around it—no “single point of failure.”

HaLow (802.11ah)

HaLow operates in the sub-1 GHz band (902–928 MHz in the U.S.), giving it better wall-penetration and longer range than 2.4/5 GHz Wi-Fi. The trade-off is lower peak throughput, but for tactical data it’s a win: 1.8 Mbps on a 1 MHz channel, 4.4 Mbps on 2 MHz, 7.3 Mbps on 4 MHz, and 15 Mbps on 8 MHz. I measured these numbers on my own build; the device hit 15 Mbps when I ran a single-stream test over a 200-ft distance, and the signal held up to 2 000 ft when I increased the transmit power from 21 dBm to 27 dBm.

Raspberry Pi 4 + OpenWRT

The Pi is a cheap, powerful compute node. With OpenWRT I can flash a custom firmware that turns the Pi into a full-blown router: NAT, DHCP, VPN, and the HaLow module sits in a mini-PCIe slot. This combination is the heart of the device.

Starlink Back-haul

I didn’t want to rely on a single satellite link. Instead, I set up a Starlink dish as a back-haul and let the mesh handle the local traffic. The Starlink link gives me 22 Mbps down and 3 Mbps up for most residential plans, which is more than enough for video and voice.

How to apply it

Below is a step-by-step mental model that keeps you focused on the end goal: a functional, secure, and scalable network.

Step	What you need	Why it matters	Key takeaway
1	Raspberry Pi 4, 8 GB RAM, 32 GB eMMC	Core compute	The Pi runs OpenWRT and handles routing
2	HaLow mini-PCIe module (e.g., Heltec HT-HD01 or Vantron VT-SOM-AH)	Long-range radio	21 dBm baseline, 27 dBm firmware-upgraded
3	21700 Li-Po batteries, Waveshare power hat	Power independence	10 000 mAh total gives ~4 h of uptime at full transmit
4	Antenna (SMA-to-U.FL, 2 dBi or higher)	Signal quality	Simple gain boost gives 2-3 ft extra reach
5	OpenWRT image (pre-flashed)	Firmware stability	Removes vendor lock-in
6	ATAC client, Mumble server, Starlink configuration	Tactical apps	Turns the mesh into a full-blown command & control system
7	Starlink dish, Wi-Fi 2.4/5 GHz adapter	Internet back-haul	Provides bandwidth for video and GPS

Start with the Pi. Flash the OpenWRT image I packaged and load the BATMAN-adv module. I usually use a microSD card for persistence. The open source image is available in my GitHub repo; it’s a drop-in replacement for the stock firmware.
Plug in the HaLow module. The Heltec HT-HD01 (V2) comes with a 21 dBm transmit power by default. I flashed the custom firmware that raises it to 27 dBm; the datasheet shows the module can handle that safely.
Attach the antenna. I used a 2.4-dBi Yagi-style antenna with an SMA-to-U.FL cable. That extra gain is the difference between 200 ft and 2 000 ft of usable range.
Set up power. I wired two 21700 cells in series, giving 7.4 V nominal. The Waveshare hat handles regulation and battery monitoring. When the voltage drops to 6.5 V, the hat cuts the transmit power to preserve the cells.
Configure the mesh. In OpenWRT, I enabled 802.11s and set the SSID to Haven. BATMAN-adv automatically discovers peers and builds a routing table. I also set up a VLAN for ATAC traffic so that the tactical overlay stays isolated from general traffic.
Deploy ATAC. I installed the Android Tactical Awareness Kit on a rugged phone and set the mesh IP as the default server. The phone now pulls live map overlays and pushes location data back to the mesh.
Starlink back-haul. I ran a small OpenWRT instance on a separate Pi, connected it to the Starlink dish, and added a static route to the mesh subnet. Video from the phone is now streamed over the satellite link with only ~25 ms latency.

You can double-check every configuration with the wifi-scan and batmand tools. A quick iw list | grep 802.11ah confirms the radio is up and the channel width is as expected.

Pitfalls & edge cases

Issue	What you might see	Fix
Regulatory limits	Transmit power above 30 dBm (1 W) is illegal in most countries	Keep firmware at 27 dBm; use a 1 dBi gain antenna
Interference	Heavy 5 GHz Wi-Fi can bleed into the 2.4 GHz band	Move to a dedicated channel (e.g., channel 20)
Battery drain	27 dBm uses ~500 mW; 4 kWh per day	Run the device in low-power mode during off-peak
Subnet collision	Two meshes on the same 192.168.1.0/24	Use distinct subnets for each squad
Firmware bugs	OpenWRT updates can break BATMAN-adv	Pin the kernel version in /etc/opkg.conf

Open questions that keep the community busy:

How many nodes can a single halo radio support before packet loss spikes?
What is the maximum number of satellites I can attach for redundancy?
Can I run an encrypted VPN over the mesh without exceeding 3 Mbps?

I’m not going to answer all of them here, but the data you can collect during a field test will guide your decisions.

Quick FAQ

Question	Answer
What’s the range of the HaLow module?	Up to 1 km line-of-sight; in the field I got ~2 000 ft with a 2 dBi antenna.
Does it support video?	Yes, the 15 Mbps channel width is enough for 720p video streams.
Is it secure?	The device uses WPA3-SAE encryption, which is the latest Wi-Fi standard and provides forward secrecy.
Can I use a Starlink dish?	Absolutely. The back-haul can be any broadband source; Starlink is just the easiest to deploy in remote areas.
How many batteries do I need for a day?	Two 21700 cells give 10 000 mAh, which is about 4 h at full transmit. Use a larger pack for longer ops.
Is it rugged enough for field use?	The case is 3D-printed from ABS; it can withstand drops and dust. For heavy-gauge use I added a waterproof seal.
What if I need more nodes?	The mesh is self-healing. Just power on a new Pi, plug in the HaLow module, and the network will integrate itself.

Conclusion

If you’re a commander, a field engineer, or a hobbyist who wants to test a low-cost mesh, this is the blueprint. I spent a weekend building a 15 Mbps, 2 000 ft mesh that runs ATAC, Mumble, and a Starlink back-haul for only $106 in parts. I can build 200 of these for the price of one by standardizing the BOM and ordering in bulk.

Actionable next steps:

Grab a Raspberry Pi 4 and a HaLow module.
Flash OpenWRT and flash the 27 dBm firmware.
Build the power and antenna harness.
Test in a controlled environment: ping, throughput, and voice latency.
Deploy in the field and iterate.

The world of tactical communications is moving fast. An open-source, low-cost mesh radio keeps you ahead of the curve without breaking the procurement budget.

References

Last updated: February 4, 2026

From $106 to Battlefield-Grade: Building Your Own IP Mesh Radio

Why this matters