5fa32811d5
RNode firmware frames every LoRa packet as [1-byte header][payload]: on TX it writes `random(256) & 0xF0` (split-flag clear for a single packet), and on RX it reads+strips that byte before handing the packet to RNS. Our bridge sent the raw RNS packet, so a real RNode consumed our flags byte as its header and gave RNS a 1-byte-shifted packet that failed validation — the node received our RF but never registered us as a destination. Prepend a 0x00 RNode header (single, non-split) to the Reticulum announce. Verified live: node .116 now emits an announce event for our dest hash and registers "Archy-Messh" as an LXMF delivery contact. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
archy-messh
Research + firmware project exploring a single LoRa device that can speak, relay, and repeat between three independent mesh networking protocols:
- Meshtastic
- MeshCore
- Reticulum (via RNode-style modem firmware)
Goal: one ESP32-based device that acts as a tri-protocol repeater/bridge —
not a fork of any single project, and not affiliated with or dependent on
the archy (Archipelago) codebase. This repo is intentionally standalone.
Status
Architecture phase done — see docs/ARCHITECTURE.md for the protocol
research, hardware constraints (target: Heltec WiFi LoRa 32 V3), and
phased plan. Phase 0 (host-side bridge across 3 separate stock-firmware
boards) is written — see host-bridge/ — but not yet hardware-tested; no
LoRa boards have been attached to the dev machine this was written on.
Layout
docs/— protocol research notes and architecture/design docshost-bridge/— Phase 0: Python bridge relaying text between real Meshtastic/MeshCore/RNode-Reticulum boards over each project's official client protocolfirmware/— Phase 1+ embedded firmware (once Phase 0 is validated on hardware)hardware/— reference hardware notes / board selection
Non-goals (for now)
- Not reimplementing any of the three protocols from scratch in v1
- Not targeting non-ESP32 hardware initially
- Not touching/depending on the
archy(Archipelago) repo in any way