rnsd transport node relaying holon announces between holonserve (apps :4243) and off-host clients (clients :4242 -> host :4262). Hard rule documented: NO uplink interface (causes mesh-loop interference that blocks announce re-propagation). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| config | ||
| .gitignore | ||
| docker-compose.yml | ||
| README.md | ||
rmesh-rns-transport
A dedicated Reticulum transport node (rnsd, enable_transport=Yes) that relays
holon announces between holonserve and off-host clients (e.g. a laptop running
holonfetch). It exists because rnsd-rs / rmesh-reticulum do not relay announces
to remote TCP clients.
Topology
holonserve --(rmesh-internal)--> apps :4243 ┐
├─ rmesh-rns-transport (transport=Yes)
client (laptop) --(tailnet :4262)--> clients :4242 ┘
holonserve sets RMESH_RETICULUM_HOST=rmesh-rns-transport / RMESH_RETICULUM_PORT=4243.
A client adds a TCPClientInterface to <netcup-tailnet-ip>:4262.
The one hard rule
Never add an uplink interface (a TCPClientInterface to another transport node such
as rnsd-rs). It creates a mesh loop / path-table interference that silently stops the
node from re-propagating holonserve's periodic announces to clients. Keep it to exactly
the two TCPServerInterfaces above. (See holonserve NOTES.md for the debug story.)
Deploy
docker compose up -d # reuses rmesh-holonserve-rmesh-holonserve:latest image
Requires the external rmesh-internal network and the holonserve image already built.