Three ways home for field firmware
Why a browser flasher, UF2 fallback, and explicit bootloader path are one recovery system rather than redundant conveniences.
A remote node is only as good as its recovery path. RatTunnel treats update safety, identity, observability, and radio behavior as first-class product features.
Field firmware has to survive poor links, duplicate traffic, abrupt power loss, and operator mistakes while remaining serviceable without a specialized development setup.
Engineering approachA bounded route table, duplicate suppression, watchdog recovery, persistent runtime settings, and three update paths make the node legible and recoverable. A browser flasher exposes configuration without hiding the radio details.
Reticulum-compatible announcements, learned routes, forwarding, and jittered relay queues.
X25519 and Ed25519 peer messaging plus an optional ephemeral-identity boot mode.
Web flasher, UF2 fallback, watchdog, diagnostics, and explicit bootloader entry.
Related writeups document implementation patterns, tradeoffs, and recovery considerations from this work.
Why a browser flasher, UF2 fallback, and explicit bootloader path are one recovery system rather than redundant conveniences.
Public repository metadata and source are included where the project is available for review.