Single-file browser tool for visualising Reticulum announce propagation. Click any node to originate an announce and watch it traverse a configurable topology respecting Full, AP, Boundary, and Roaming interface rules.
- HTML 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Internal announces do not propagate out on Roaming interfaces per the Reticulum manual's interface-mode graph. Set internal.roaming to false in the PROP matrix, update the static rules table, tooltips and mode legend, and reorder Internal before Roaming to mirror the manual table layout. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
| announce-sim.html | ||
| README.md | ||
| reticulum_logo.png | ||
| rns-announce-sim-screenshot.png | ||
Reticulum Announce Propagation Simulator
A browser-based, single-file interactive tool for exploring how announces propagate through a Reticulum network. Click any node to originate an announce and watch it traverse the topology step by step, respecting the propagation rules of each interface mode.
Features
- BFS-based propagation simulation — announces spread hop by hop with animated packet steps and a full propagation log
- Five interface modes — Full, Access Point, Boundary, Roaming, and Internal, each with distinct forwarding rules
- Clickable mode badges — change the interface mode on any edge directly in the graph
- Preset topologies — quickly load representative configurations (Default Mix, All Full, AP Demo, Boundary Demo, Roaming Demo, Internal Demo)
- Intermediate relay hop — insert an optional transport node between the two hubs to experiment with multi-hop behaviour
- Dark / light theme — toggle with the button in the header; preference is saved across sessions
- Responsive layout — works in both landscape (two-column) and portrait (stacked) orientations
Usage
Open announce-sim.html directly in any modern browser — no build step, no server required.
Interface Modes
| Mode | Behaviour |
|---|---|
| Full / Gateway | Standard transport. Forwards to Full, Boundary, Roaming and Internal interfaces. |
| Access Point | Announces are never auto-broadcast onto an AP interface. AP clients can still announce outward. |
| Boundary | Marks the edge between significantly different network segments. Roaming announces cannot cross, and boundary announces are not pushed into Internal interfaces. |
| Roaming | For physically mobile interfaces. Announces cannot cross a Boundary or reach another Roaming interface. |
| Internal | Protected inner segment. Announces arriving on a Boundary interface are not pushed onto Internal interfaces, but Internal announces do propagate out to Boundary. Recursive path requests are enabled by default so destinations across the boundary stay reachable. |
Transport nodes (dashed ring) apply these rules at each hop. Non-transport nodes receive announces but do not forward them. For the purpose of announce propagation, the Full and Gateway modes are identical.
Propagation Rules
Forwarding is determined by the receiving interface mode of the transport node and the outgoing interface mode of the next hop:
| → Full | → AP | → Boundary | → Roaming | |
|---|---|---|---|---|
| Full in | ✓ | ✓ | ✓ | ✓ |
| AP in | ✓ | — | ✓ | — |
| Boundary in | ✓ | ✓ | — | — |
| Roaming in | — | — | — | — |
License
MIT
