Skip to main content

Crate rusty_esp_iroh_bridge

Crate rusty_esp_iroh_bridge 

Source
Expand description

rusty_esp_iroh-bridge — the Janus bridge (N3).

A std process (a Pi, a P4, a laptop) holds one iroh endpoint and fronts N radio neighbours that cannot run iroh themselves: a C6 over ESP-NOW, a LoRa node. Each neighbour links to the bridge with rusty_esp_signal’s authenticated session (the neighbour’s key stays on the neighbour; the bridge keeps the session), sends its own signed manifest, and its telemetry is re-framed onto janus/media/1. The home computer asks the bridge Request::Neighbours and gets each neighbour’s DID, manifest and signature verbatim — it verifies the neighbour, not the bridge.

Re-exports§

pub use neighbour::BridgeCore;
pub use neighbour::BridgeCounters;
pub use neighbour::CODEC_NEIGHBOUR_TELEMETRY;
pub use neighbour::Event;
pub use neighbour::NeighbourPacket;
pub use neighbour::Reach;
pub use radio::BROADCAST;
pub use radio::FakeBus;
pub use radio::FakeRadio;
pub use radio::PeerAddr;
pub use radio::Radio;

Modules§

neighbour
The bridge’s side of every neighbour: the rusty_esp_signal handshake answered, the session kept, the neighbour’s own signed manifest received and verified, its telemetry attributed.
radio
The radio seam: what the bridge needs from an ESP-NOW or LoRa attachment, and an in-memory bus that stands in for one on the host.
sim
The neighbour’s side, on the host: what a C6 or a LoRa node does over rusty_esp_signal to appear behind a bridge. A firmware implements the same four steps over its radio; this is the reference the tests and the example drive.

Structs§

Bridge
The radio loop and the fan-out of its events.
CoreHandle
A NeighbourSource over the shared core.
DynRng
A boxed Rng as a sized one: the link’s handshake takes &mut impl Rng, and a core that owns any RNG needs this shim.
HostRng
The operating system’s random source as the family’s Rng seam, for the bridge’s handshakes on a host.