MANET Software for Military Field Teams: Mobile Ad-Hoc Mesh Networking

Mobile Ad-Hoc Networks (MANETs) solve a fundamental tactical problem: how do you create a data network when there is no infrastructure to connect to? In a MANET, every node is simultaneously a communication device and a router. Packets travel from source to destination by hopping through intermediate nodes, forming a self-organizing mesh that adapts as nodes move, join, or leave the network.

For military field teams — squad and platoon level operations where fixed communication infrastructure is unavailable or has been destroyed — MANET provides data connectivity for situational awareness applications, position reporting, and digital messaging without dependence on base station coverage. Understanding how MANET software works, and how to integrate it into tactical applications, is an increasingly essential skill for defense software developers.

Why Infrastructure-Free Networking Is Critical at Squad Level

The tactical internet concept — connecting every soldier to a shared digital picture — requires connectivity. In garrison and at operational headquarters, that connectivity comes from cellular networks, military satellite, or fixed tactical communication infrastructure. At the squad and platoon level in offensive operations, none of these may be available. The squad leader moves faster than the communication infrastructure can follow.

Even when radio infrastructure exists, direct P2P communication has tactical advantages. A message that travels directly between two radios within line of sight reaches its destination in milliseconds with high reliability. The same message routed through a TAK Server at a brigade headquarters travels farther, may encounter QoS constraints, and depends on the link to headquarters remaining up. For time-critical tactical data exchange at close range — position sharing within a squad during a room-clearing operation — local MANET is the appropriate transport.

Routing Protocols: OLSR and BATMAN

OLSR (Optimized Link State Routing, RFC 3626) is the most widely deployed proactive MANET routing protocol. In OLSR, each node maintains a complete topology map of the network by periodically broadcasting HELLO messages (which advertise the node's one-hop neighbors) and TC (Topology Control) messages (which propagate link state information through the network). The MPR (Multipoint Relay) optimization in OLSR reduces broadcast overhead by selecting a subset of neighbors to relay TC messages, reducing the number of redundant transmissions in dense networks.

OLSR's proactive nature means routing tables are always current — no route discovery delay when sending a packet. The trade-off is continuous control plane traffic (HELLO and TC messages) that consumes bandwidth even when no data is being sent. In bandwidth-constrained tactical radio environments, the control plane overhead of OLSR must be tuned against the available bandwidth budget.

BATMAN (Better Approach To Mobile Adhoc Networking) takes a different approach: instead of maintaining a topology map, each node only knows which neighbor is the best next hop toward any given destination. Nodes periodically originate OGM (Originator Message) packets. Each node rebroadcasts OGMs it receives, attenuating their quality metric. After convergence, each node knows which neighbor produced the highest-quality OGM from each destination — that neighbor is the best next hop.

BATMAN's key advantage over OLSR is scalability: the distributed routing information requires less memory and less processing than a full topology map, making BATMAN better suited to large networks with many nodes. Its disadvantage is that path quality is computed from the quality of OGM reception history rather than from explicit link metrics, which can make it less responsive to rapidly changing link conditions.

Commercial Military MANET Radios: Software APIs

Silvus StreamCaster radios (SC3500, SC4200) are widely deployed MANET radios based on the MN-MIMO (Mobile Networked MIMO) waveform. They present themselves to connected devices as standard IP network interfaces — once a device is connected to a StreamCaster via USB, Ethernet, or Wi-Fi, it has IP connectivity to all other devices on the StreamCaster mesh. From the application's perspective, the MANET is a transparent IP transport. Applications communicate using standard sockets without any MANET-specific code.

Silvus provides a management API (HTTP REST over the radio's management interface) that allows applications to query the network topology (which radios are connected, RSSI to each neighbor, data rate), set radio parameters (frequency, bandwidth, transmit power), and monitor link quality. Applications that need to adapt their behavior to network conditions — reducing sync frequency when bandwidth is low, alerting when a node loses mesh connectivity — use this management API.

Persistent Systems MPU5 is another widely deployed military MANET platform, using a custom waveform (Wave Relay) optimized for throughput and latency. Like Silvus, the MPU5 presents as an IP interface to connected devices and provides a management API for network visibility. The API returns per-node metrics including goodput (actual data throughput, distinct from raw link rate), latency, and packet loss rate.

App Integration: MANET as Transparent Transport

The correct integration pattern for tactical applications is to treat MANET as a transparent IP transport. The application should not have MANET-specific logic for its data transport — it should use standard UDP or TCP sockets, and the MANET layer should handle routing. This pattern provides two benefits: the application is network-agnostic (it can use cellular, Wi-Fi, or MANET interchangeably), and MANET radio replacement or upgrade does not require application changes.

What the application does need to handle is the specific QoS characteristics of MANET transport: variable bandwidth, variable latency, and occasional packet loss as nodes move in and out of range. Applications that stream position data should use UDP with a short TTL rather than TCP persistent connections — TCP's retransmission behavior can cause cascading delays when a MANET link momentarily drops. Applications that require reliable delivery should implement their own lightweight acknowledgment layer tuned for MANET latency characteristics rather than relying on TCP.

Bandwidth Management: Priority Scheduling

A typical military MANET radio provides 1–5 Mbps usable throughput under good conditions, dropping to 200–500 Kbps in difficult RF environments. Sharing this bandwidth between voice, position tracking data, messaging, and file synchronization requires prioritization.

The standard approach is DSCP (Differentiated Services Code Point) marking on IP packets, which MANET radio firmware uses to schedule transmission priority. Voice packets (VoIP for push-to-talk audio) get EF (Expedited Forwarding) DSCP marking — they preempt all other traffic. Position reports get AF41 (Assured Forwarding 4, class 1) — high priority but not voice-level preemption. File synchronization and map tile delivery get CS1 (lower than best-effort) — they fill available bandwidth without affecting operational traffic.