Reticulum Mesh Node
Tactical Mesh Service · Reticulum Mesh Client · Air Defense Management System
A full Reticulum service node — transport, LXMF propagation, a NomadNet page node and a public Wall board — powering the TMS RMC ADMS messaging client: secure, resilient communication that keeps working without centralized infrastructure.
Live status
The Reticulum transport backbone, bundled into the app by default — devices connect and route through the mesh automatically, with no manual setup required.
An LXMF store-and-forward relay: it holds messages for recipients who are offline and delivers them once they reconnect — so nothing is lost when a device is away.
Hosts pages and content served entirely inside the mesh over Reticulum — reachable from the NomadNet browser in the app, with no internet required.
A public broadcast board on the mesh: post once and every subscriber sees it — with history, polls and moderation, delivered over LXMF right inside the app's chat.
A shared common operating picture on the mesh: markers, drawings and their attachments sync between every TMS RMC device and stay available offline — the same objects also bridge to ATAK / WinTAK, all carried over LXMF.
Meteorological and oceanographic conditions for the operating area, pulled from the weather service and cached here — so devices get forecasts, winds aloft and sea state over the mesh, as METOC symbols on the map, without any of them needing internet access.
The air picture over the operating area: aircraft broadcasting ADS-B are collected here from the OpenSky network and handed to devices over the mesh, so the traffic overhead shows on the map without any device needing internet access — or a receiver of its own.
The sea picture for the operating area: vessels broadcasting AIS are received here as a live stream and handed to devices over the mesh — names, types, courses and speeds on the map, with no device needing internet access or a receiver of its own.
Orbital elements for the satellites worth watching, fetched here once a day and handed to devices over the mesh. Nothing is streamed: a device that has the elements computes passes, ground tracks and footprints itself — for days, with no node and no internet at all.
Real-time voice and video calls — one-to-one or group, push-to-talk or open mic — relayed through this node's media server so devices connect reliably across NATs, Wi-Fi and mobile networks.
An optional encrypted overlay. Devices with WireGuard enabled reach the node privately over the tunnel, while everyone else keeps the public path — a second, hardened route to the mesh.
Bridges the mesh to the TAK ecosystem: positions, chat, map objects and files cross between TMS RMC devices and ATAK / WinTAK over Cursor-on-Target — so the two worlds share one picture, carried on the infrastructure-independent mesh.
Keeps the node's clock on UTC from the reference-time coordinator (chrony) — one time base for every node service and for the TAK bridge, so markers, messages and reports agree on when things happened.
Checking node status…
Questions or support: support@micro-gis.com