12. OFF-GRID MESH + REMOTE ACCESS (Phase 2/3)

12.1 Tailscale (software mesh — needs internet on both ends)

Connects truck, home RAG, Hetzner, phone, cyberdeck. Stable 100.x addresses across any transport. Subnet router on the Cudy LT18 (rev 3.4 — owned, OpenWrt; was GL.iNet) exposes the whole truck network; smart boxes (OptiPlex, Pi, phone) also run their own clients. See §4.1 for the subnet-router concept + the opkg-feasibility caveat + tailnet ACL lockdown. Does NOT extend radio range — networking mesh, not radio mesh. Hiking scenario: if truck has internet AND your phone has signal, you reach everything (truck cams, Hetzner, home RAG) — different internet on each end is fine.

12.2 Wi-Fi HaLow (radio — extends range, carries full IP)

915 MHz, ~1 mile line of sight (less in PNW timber), megabit IP. Routes internet — truck (Starlink/cell) → HaLow → remote device with no cell GETS internet (carries real IP, unlike Meshtastic's kbps text/GPS). On-demand snapshots + telemetry keep power low. Compact board preferred over full Pi. Mesh nodes extend range further. ⚠️ Canada ISED 915MHz power rules differ from US FCC.

Tailscale over HaLow: works — HaLow provides the IP path, Tailscale rides on top for consistent addressing. Off-grid: cyberdeck → HaLow → truck → (truck's internet) → Tailscale world.

12.3 Meshtastic vs HaLow (decided)

Meshtastic = kbps text/GPS only, CANNOT carry images/video. Your need (range + image-if-needed + truck-data) = HaLow. Meshtastic only if you just want GPS+text. Middle options exist (LoRa tuned faster, ESP32+LoRa telemetry) but none carry images — image requirement forces HaLow.

12.4 Cyberdeck (Phase 3)

Pi 4/5 + HaLow (+optional Meshtastic) + screen + keyboard + battery + antenna in a rugged Pelican case. On-demand truck snapshots/telemetry, SSH to the truck OptiPlex (or the home RAG box via Tailscale), cached RAG field reference. Talks to the always-on Pi 3 B+ (instant), escalates to the OptiPlex via WOL. Build after main system + HaLow link proven.

12.5 What Works When