Reticulum - Post Internet Network - Why HF Modems?

Summary of Technological Concepts & Product/Project Features

Core topic: Reticulum for a “post internet network”

• The speaker frames Reticulum as a way to keep community communication working if normal internet connectivity is disrupted (e.g., disasters, infrastructure failures, human error, or cyber/intentional attacks).
• The goal is resilience: radio-based networking with no dependence on internet links.

HF encrypted communication demo (constraints noted)

• A demo is shown to illustrate that encrypted communication is possible over HF using Reticulum.
• The speaker emphasizes compliance with amateur radio regulations:
  • They note encryption restrictions on certain amateur bands.
  • During the walkthrough, they transmit at very low power into a dummy load to avoid actual RF broadcasting.

Interoperability with radios (primary use case)

• Key claim: Reticulum interoperates with HF radios (not just a networking concept).
• The workflow includes:
  • Selecting a radio
  • Starting Reticulum
  • Choosing a modem configuration via blueprints

Modem integration via “blueprints”

• Reticulum is started in a “nerd-free” way using predefined configurations (“blueprints”).
• Two main HF modem integrations are highlighted:
  • Modem 73: uses QPSK modulation in the demonstrated “balanced/reliability” mode
  • Mercury: another HF modem option (demonstrated later)

QPSK modulation mode selection + reliability/speed tradeoff

• The modem 73 integration supports multiple modulation schemes.
• Modes are selectable based on a tradeoff:
  • Speed vs reliability
• Example:
  • A “balanced” mode is used in the first demo.
  • The mode list shifts toward faster transmission at the cost of robustness.

Mesh Chat + Network Visualizer as the user-facing UX

• The user-facing workflow includes:
  • Mesh Chat (a fork used for simple text messaging)
  • Network Visualizer with auto-updating to confirm nodes/messages are appearing
• Positioned as an operational interface for testing and community use.

“Plug-and-play” Linux platform: MCOM tools

• The speaker is building a simplified operational environment called MCOM tools (a Linux distribution/version).
• It already supports hardware detection (radio selection, CAT/audio device setup) and is being extended to run Reticulum + HF modems.
• Described benefits:
  • Select a supported radio model
  • Plug in USB
  • Auto-detect CAT control and the audio device
  • Choose a blueprint (e.g., modem 73 or Mercury)
  • Reticulum then manages modem processing and radio control

Mercury mode switching + behind-the-scenes validation

• Switching from modem 73 to Mercury changes only the communication mode while keeping the same Reticulum identity.
• The speaker checks running processes (e.g., ps filtered for “mercury”) to demonstrate that:
  • Mercury is launched with the selected parameters (index/mode)
  • It dynamically determines sound-card input/output
  • It configures CAT control (including mention of rig control)

Operational procedure (SOP) for resilience

• The proposed approach is “HF link regardless of what’s going on”:
  • If internet is down or external connectivity is compromised, the community can switch primary communications to HF.
  • Example rotation:
    • Mercury as primary for one window
    • Then modem 73 (reliability/balanced) for the next
• Emphasis: keep it turnkey/simple so someone can serve as the “Reticulum network engineer” for the group.

“Resistance radio” concept + regulatory caution

• “Resistance radio” is described as a preparedness concept:
  • The ability to communicate even if governments suppress radio or disrupt inbound/outbound internet infrastructure.
• The speaker explicitly says they are not advocating breaking FCC regulations.
• The intent is to be able to “flip on” HF links legally within permitted usage.

HF performance expectations vs low-power line-of-sight

• The speaker argues HF provides much better non-line-of-sight range than typical low-cost LOS radio gear (which might offer a few miles depending on setup).
• Rough ranges claimed:
  • 6–300 miles (within their Southwest use case; “works all day”)
  • ~1,000 miles (mid/long-range boundary)
  • 1,000+ miles (long range)
• Key point: in an internet outage scenario, HF with Reticulum could be “tremendous.”

Encryption note about the modems themselves

• They state modem 73 and Mercury do not provide encryption “on their own.”
• Reticulum is positioned as the networking layer that enables end-to-end encrypted operation, while the modems focus on modulation/demodulation.

Training/pilots for targeted HF communication

• The speaker is preparing public training and small pilot programs to teach targeted HF comms, including:
  • Tuning for specific distances (e.g., 50 mi, 300 mi, 100 mi)
  • Choosing time-of-day, antenna strategies, and techniques
• They suggest using the modems without Reticulum first to assess conditions and improve targeting.

Main speakers / sources

Speaker

• “Tech Prepper” (referred to as “I’m the tech prepper” / “I’m the Tech Prepper” throughout)

Project/tool sources mentioned

• Reticulum (main networking stack)
• MeshChat (fork used for text messaging)
• Modem 73 (open-source HF modem integration)
• Mercury (open-source HF modem integration)
• MCOM tools (speaker’s Linux-based plug-and-play platform)
• Network Visualizer (tool used to observe Reticulum topology/traffic)