Video summary

Reticulum - RV Network Tour

Main summary

Key takeaways

Technology

Summary (Reticulum RV Network Tour)

Purpose / setup style

  • The creator (“Tech Prepper”) demonstrates a practical, real-world Reticulum network built to be used “in the field” from an RV during a short family trip in northern Arizona (north of Flagstaff).
  • The video is a quick tour, not a complete configuration walkthrough. The creator mentions a ~30-page notebook of configuration/reference networks they plan to share later.

Core hardware + roles

  • R-node / antenna on the RV roof: An R-node (roof device) that connects into the rest of the RV network stack.
  • Dell 7220 transport machine: A Dell 7220 acts as the Reticulum transport/router, providing 4 interfaces. Routing/forwarding depends on destination.
  • “Lower device” support: The roof node communicates with the rest of the network stack, allowing Reticulum to forward messages between different mediums.

The 4 transport mediums (4 interfaces) on the Dell 7220

  1. HF packet radio interface

    • Uses an HF radio connected via a DigiRig mobile.
    • Software-based TNC: Direwolf.
    • Notes include an HF antenna setup intended for long-ish range / NVIS-style operation.
    • The video mentions HF range capability, but not a full verified range test.

  2. Local Wi‑Fi output to the RV travel router

    • The transport provides Wi‑Fi without requiring repeated reconfiguration.
    • The creator explicitly says they “love this thing” because it avoids repeated setup effort.

  3. Internet connection via Starlink

    • The RV travel router uses Starlink to provide “cloud reachability.”
    • This allows connecting back to the home/remote side via a TCP server running on the creator’s end.

  4. Reticulum “AR node” interface to the roof device

    • The RV roof node is the local radio presence; transport and nodes coordinate message routing.

Antennas / propagation goal

  • Mentions an HF half-wave antenna mounted around 6 ft height aimed at NVIS propagation.
  • Expected capability is roughly ~300 miles and closer, presented as capability rather than confirmed by a full test in the video.

External / cloud components

  • A TCP client ↔ TCP gateway endpoint acts as a new interface so the network can connect over the internet.
  • Referenced “remote/online” elements include:
    • Bentobox (server/broker) and Bentobox mobile
    • NeoSmith 724 (appears as a connected device; some users are online via internet)
    • TTP Transport (running at the house and participating in delivery)

Apps / interfaces used

  • Columba (Android):
    • Introduced as a new chat/UI app.
    • The creator describes it as having the cleanest interface so far.
    • Shows contacts/devices such as Bentobox, Bentobox mobile, NeoSmith, TTP Transport, and the creator (“Tech Prepper”).
  • The creator says they plan to move away from Sideband and wait for MeshChat X until later development (mentions “until September”).
  • They also mention experimenting with NomadNet/pages (page-like serving resembling small web pages), though it’s not being run in this moment.

Key behavioral insight about Reticulum (not “full mesh visibility”)

Reticulum networks don’t behave like a typical IP mesh where everyone has a single unified view.

  • From one device’s perspective (the creator’s main radio), they may only “see” certain directly reachable peers.
  • Other peers appear through different transports (e.g., internet vs radio).
  • When switching viewpoint to the RV transport, the device can see:
    • the local radio neighbor(s) (e.g., the field notebook/phone)
    • plus internet-connected peers reachable through Starlink/TCP.

Demo highlights (message delivery and mode switching)

  • Live scenario without internet

    • They demonstrate sending while driving/walking out over the lower radio link.
    • Examples include being in airplane mode with no Wi‑Fi/Bluetooth/internet.
    • Messages route over radio only, with reception via the roof/R-node and forwarding through Reticulum.

  • Message routing differs by medium

    • Messages are sent to:
      • a phone near the creator (local radio)
      • then to Bentobox/TTP transport via the internet (Starlink/TCP path)
    • They use “delivered” status updates and mention a network visualizer that shows changing visibility.

  • Network visualizer usage

    • They use a network visualizer to show which devices appear “in view” from different nodes.
    • Workflow shown:
      1. send a ping
      2. observe delivery status
      3. return to the visualizer to see updated nodes appear

Security / privacy / architecture claim

  • The creator hints that the ability to reach the internet securely and privately via these transports will be discussed in a future video (deep dive promised).

Main speakers / sources

  • The Tech Prepper (primary speaker; setup author and demonstrator)

Reticulum components / systems referenced

  • Dell 7220 transport
  • AR node / R node on the RV roof
  • Starlink TCP gateway/server components (including “TTP Transport” / TCP server, and “Bentobox” / “Bentobox mobile”)

Android app referenced

  • Columba (user-facing interface)

Original video