# Winlink and LoRa Mesh: Complementary Systems

<div id="bkmrk-key-message%3A-winlink" style="background:#fff3cd;border-left:4px solid #ffc107;padding:12px 16px;margin-bottom:20px;"> **Key Message:** Winlink and LoRa mesh serve different but complementary roles in emergency communications. Serious EMCOMM operators use both - choose the right tool for each message type. </div><div id="bkmrk-bridge-fcc-caveat" style="background:#fff3cd;border:2px solid #dc3545;padding:12px 16px;margin-bottom:20px;">**Legal note on bridging mesh to Winlink/amateur radio.** Default-encrypted Meshtastic/MeshCore traffic **cannot lawfully be transmitted on amateur (Part 97) frequencies**. A mesh→Winlink (or mesh→APRS) bridge is lawful only if a **licensed amateur** keys the amateur leg and the content is **plaintext** (decrypted at the gateway) — 47 CFR §97.113(a)(4) prohibits messages encoded to obscure their meaning on amateur bands, and the operator must ID per §97.119. The LoRa mesh itself runs unlicensed under Part 15; only the Winlink/amateur side carries the licensing and plaintext requirements.

</div>## What Is Winlink?

 **Winlink** (formally the Winlink Global Radio Email system, also known as Winlink 2000 or WL2K) is a worldwide radio messaging system that provides email capability over amateur radio and government HF radio networks. Winlink allows licensed amateur radio operators and authorized agencies to send and receive email-formatted messages via radio, completely independent of the internet - although it also supports internet-connected gateways (Radio Message Servers, or RMS) when internet is available.

 Winlink operates on HF (shortwave), VHF, and UHF frequencies. Common access modes include:

- **Packet radio (AX.25):** VHF/UHF packet at 1200 or 9600 baud (traditional AX.25)
- **VARA FM:** a separate sound-card protocol for VHF/UHF (not AX.25 packet) — both are distinct Winlink access modes operated under Part 97
- **VARA HF / PACTOR:** HF digital modes for long-range communication without internet gateways
- **Winlink telnet:** Internet-connected mode when internet is available
- **ARDOP:** Open-source HF mode for Winlink operation

 Winlink's killer feature is its role in the **Winlink 2000 network**: a constellation of volunteer-operated Radio Message Servers (RMS) that [store and forward](https://wiki.meshamerica.com/books/meshtastic-repeaters/page/store-and-forward) messages globally. A message sent via Winlink from a field site in a disaster area can be received as a normal email by a Red Cross logistics manager anywhere in the world with an internet connection - even if the field site has no internet, no cell service, and no land lines. The sender needs an HF radio, a Winlink-capable TNC/modem, a computer running Winlink client software (e.g., Winlink Express), and a valid amateur license.

## Winlink's Role in EMCOMM for Formal Message Traffic

 Winlink excels at **formal, structured message traffic** - the kind that needs to be sent, received, archived, and acted upon by agencies that use email as their normal communication medium:

- **ICS forms:** Winlink supports transmission of standard ICS forms (ICS-213 general message, ICS-214 activity log, ICS-309 communications log, etc.) in a format that can be decoded and displayed at the receiving end without specialized software.
- **File attachments:** Winlink can carry binary file attachments (images, spreadsheets, maps) over radio - a capability mesh does not have.
- **Email to/from the internet:** Winlink messages addressed to normal email addresses are delivered when any RMS in the network has internet connectivity. This is essential for coordinating with agencies that aren't radio-equipped.
- **Global reach via Winlink network:** HF-connected Winlink can span thousands of miles. An operator in a disaster zone can exchange messages with a national-level EOC or agency headquarters regardless of local infrastructure status.
- **Message store-and-forward:** If the destination RMS is temporarily unavailable, messages are stored and delivered when connectivity is restored.

## What LoRa Mesh Does That Winlink Doesn't

<table id="bkmrk-capability-lora-mesh" style="width:100%;border-collapse:collapse;"> <thead style="background:#2c3e50;color:#FFFFFF;"> <tr> <th>Capability</th> <th>LoRa Mesh (Meshtastic)</th> <th>Winlink</th> </tr> </thead> <tbody> <tr> <td>Real-time position sharing</td> <td style="color:#008000;font-weight:bold;">Yes - automatic, continuous GPS broadcast</td> <td>No - would require manual Winlink message with position</td> </tr> <tr style="background:#f8f9fa;"> <td>Low-latency short messaging</td> <td style="color:#008000;font-weight:bold;">Often within ~15 seconds for direct/low-hop links, no operator setup — but latency varies with hops/congestion and delivery is best-effort (not guaranteed); multi-hop or congested conditions can take a minute or more</td> <td>No - Winlink sessions take 30 seconds to several minutes to complete</td> </tr> <tr> <td>Group messaging (broadcast)</td> <td style="color:#008000;font-weight:bold;">Yes - channel-wide broadcast to all nodes</td> <td>No - Winlink is point-to-point or point-to-RMS</td> </tr> <tr style="background:#f8f9fa;"> <td>Zero infrastructure required</td> <td style="color:#008000;font-weight:bold;">Yes - ad-hoc mesh, no servers</td> <td>Partial - Winlink Peer-to-Peer (P2P) works without RMS, but is limited</td> </tr> <tr> <td>Non-licensed user access</td> <td style="color:#008000;font-weight:bold;">Yes - no license required when using FCC-certified equipment within Part 15.247 limits (1 W conducted, must accept interference)</td> <td>No - requires amateur radio license or special authorization</td> </tr> <tr style="background:#f8f9fa;"> <td>Low hardware cost</td> <td style="color:#008000;font-weight:bold;">$30 - 80 per node</td> <td>$150 - 1000+ for radio + TNC/modem</td> </tr> </tbody></table>

## What Winlink Does That Mesh Doesn't

<table id="bkmrk-capability-winlink-l" style="width:100%;border-collapse:collapse;"> <thead style="background:#2c3e50;color:#FFFFFF;"> <tr> <th>Capability</th> <th>Winlink</th> <th>LoRa Mesh (Meshtastic)</th> </tr> </thead> <tbody> <tr> <td>Email with internet delivery</td> <td style="color:#008000;font-weight:bold;">Yes - messages delivered to any email address via Winlink network</td> <td>No - mesh is local; requires a bridge for internet delivery</td> </tr> <tr style="background:#f8f9fa;"> <td>File attachments</td> <td style="color:#008000;font-weight:bold;">Yes - binary attachments supported</td> <td>No binary file attachments; payloads limited to ~228-237 bytes (text and structured app messages such as position/telemetry)</td> </tr> <tr> <td>ICS form transmission</td> <td style="color:#008000;font-weight:bold;">Yes - structured form data preserved end-to-end</td> <td>No - would require manual encoding into short (~228-237 byte) messages</td> </tr> <tr style="background:#f8f9fa;"> <td>Global reach via HF</td> <td style="color:#008000;font-weight:bold;">Yes - HF radio covers thousands of miles</td> <td>No - LoRa 915 MHz single-hop range is typically a few km in terrain to tens of km with line of sight; total mesh reach extends via multi-hop relaying but remains regional, not global</td> </tr> <tr> <td>Message store-and-forward reliability</td> <td style="color:#008000;font-weight:bold;">Yes - Winlink stores messages until delivered</td> <td>Partial - Meshtastic retries but does not guarantee delivery indefinitely</td> </tr> </tbody></table>

## Why Serious EMCOMM Operators Want Both

 The decision between Winlink and mesh is a false choice. They operate on different timescales, serve different traffic types, and complement each other in a well-designed EMCOMM capability stack:

<div id="bkmrk-emcomm-capability-st" style="background:#d4edda;border:1px solid #c3e6cb;padding:16px;margin:16px 0;">### EMCOMM Capability Stack Example

 <table style="width:100%;border-collapse:collapse;"> <thead style="background:#155724;color:#FFFFFF;"> <tr><th>Traffic Type</th><th>Best Tool</th><th>Rationale</th></tr> </thead> <tbody> <tr> <td>Continuous position tracking of 10 field teams</td> <td>**LoRa Mesh**</td> <td>Automatic, zero operator overhead, real-time</td> </tr> <tr style="background:#f8f9fa;"> <td>"Team B is moving to grid 4-7" (tactical)</td> <td>**LoRa Mesh or Voice**</td> <td>Short text fits a mesh message; voice for immediate confirmation</td> </tr> <tr> <td>ICS-213 resource request to state EOC</td> <td>**Winlink**</td> <td>Structured form, needs email delivery to agency staff</td> </tr> <tr style="background:#f8f9fa;"> <td>Shelter status report (needs agency record)</td> <td>**Winlink**</td> <td>Creates archival email record; attachments possible</td> </tr> <tr> <td>Mass casualty alert (immediate, local)</td> <td>**Voice + LoRa Mesh broadcast**</td> <td>Voice for immediate acknowledgment; mesh broadcast for record</td> </tr> <tr style="background:#f8f9fa;"> <td>Coordination with non-radio agency (ARC HQ)</td> <td>**Winlink**</td> <td>Email delivery to non-amateur recipients via Winlink network</td> </tr> </tbody> </table>

</div>## Recommended Equipment for Combined Winlink + Mesh Capability

- **Meshtastic node:** Any Meshtastic-compatible hardware (e.g., T-Beam, WisBlock) - $30 - 80. (Note: the Heltec HTCC-AB02S is *not* a supported Meshtastic device — choose hardware from the current Meshtastic supported-device list.)
- **Winlink VHF station:** VHF/UHF radio (Kenwood TM-V71A, Icom IC-2730, etc.) + Signalink USB or VARA FM-capable sound card interface - $200 - 400
- **Winlink HF station (for long-range):** HF radio (Icom IC-7300 or similar) + PACTOR or VARA HF modem - $700 - 2000+
- **Common laptop:** Running both Meshtastic web client and Winlink Express - one laptop serves both. If you bridge mesh content onto the Winlink/amateur leg, that content must be plaintext and the amateur leg must be keyed by a licensed amateur (see the legal note at the top of this page).