A complete Reticulum infrastructure node delivers multiple services simultaneously: packet routing across physical interfaces, store-and-forward message propagation, real-time group chat, automated field assistance, and distributed Micron page hosting.

This guide explains how to orchestrate the complete suite of pure-Go Reticulum daemons both interactively for testing and as persistent background services in production.

A full Reticulum node comprises five cooperating components:

T282828

399

| Daemon | Role | Layer | Function |

|--------|------|-------|----------|

| gornsd T383838-s | Transport Daemon | Layer 3 | Owns all physical network interfaces (TCP server, AutoInterface, LoRa radios). Provides the shared IPC socket. |

| golxmd T383838-p | LXMF Propagation Node | Layer 4 | Caches, synchronizes, and delivers asynchronous encrypted messages for offline peers across the mesh. |

| gorrcd | Chat Hub Daemon | Layer 4 | Manages persistent Reticulum Relay Chat (RRC) rooms, channel history, and client notifications. |

| gorrcbot | Autonomous Field Assistant | Layer 4 | Connects to the local hub, providing offline station databases, navigation tools, and telemetry to chat users. On a field node it is also the Go Reticulum Lifesaver (GRL): it reads a GNSS receiver, answers T383838/whereami locally, and serves the captive survival portal to any smartphone that joins the node's Wi-Fi. |

| gonomadnet | Micron Server & TUI | Layer 7 | Serves Micron markdown pages and file downloads over Reticulum, with an interactive terminal UI for the operator. |

In Reticulum, only one process may bind a given physical network interface, listen on port T3838384242, or open a serial LoRa RNode device. If multiple independent Reticulum instances attempt to start on the same machine without coordination, whichever starts first claims the interfaces, while subsequent processes fail or fall back to unstable routing loops.

To solve this, Reticulum uses a Shared Instance architecture:

1. T383838gornsd -s starts first: It substantiates all interface drivers defined in T383838~/.reticulum/config and creates a local IPC socket (T383838@rns/default on Linux, or local domain socket / TCP loopback on macOS).

2. Client daemons attach: When T383838golxmd, T383838gorrcd, T383838gorrcbot, or T383838gonomadnet start up with T383838share_instance = yes (the default), they detect the active shared socket and route all packets through T383838gornsd.

3. No contention: Every daemon gains full access to all radios, TCP links, and neighbor announcements through a single, stable transport layer.

For development, testing, or field laptops, T383838go-nomadnet includes a one-stop orchestration script:

T282828

1. Stops any stale or orphaned stack processes.

2. Compiles the latest tools with WebAssembly plugin support (T383838-tags=wago).

3. Launches T383838gornsd -s and waits for the shared-instance IPC socket to appear.

4. Starts T383838golxmd -p (LXMF propagation node).

5. Starts T383838gorrcd (chat hub) and T383838gorrcbot (chat assistant).

6. Hands the terminal foreground to the T383838gonomadnet interactive TUI.

• T383838--headless: Start T383838gonomadnet as a background daemon (T383838-d) instead of launching the TUI.

• T383838--no-build: Skip re-compiling and use existing binaries on T383838$PATH.

• T383838-h, --help: Display usage summary.

To cleanly shut down all background daemons started by the script:

T282828

For permanent infrastructure servers, manage each component as an independent systemd service unit.

T383838/etc/systemd/system/gornsd.service:

T282828

T383838/etc/systemd/system/golxmd.service:

T282828

T383838/etc/systemd/system/gorrcd.service:

T282828

T383838/etc/systemd/system/gorrcbot.service:

T282828

T383838/etc/systemd/system/gonomadnet.service:

T282828

Enable and start the entire stack:

T282828

Once running, verify node status across each layer:

T282828

Confirm T383838Shared Instance[0] is running and that your physical interfaces report T383838Status: Up.

T282828

T282828

T282828

On a portable or vehicle node, T383838gorrcbot takes on a second role: it is the

Go Reticulum Lifesaver, the survival communicator described in

gorrcbot — The Go Reticulum Lifesaver.

Three settings turn it on, and all are optional:

T282828

What that buys a field node:

• A position the node knows without a network. T383838/whereami prints the Plus

Code, both coordinates, the Maidenhead grid, the altitude, the heading, the fix

quality, the local solar time, and the daylight remaining — all computed

in-process.

• One-word questions. T383838tower near, T383838tide near, and T383838sun inherit the live

fix, so nothing has to be typed with cold hands. T383838/sos raises a RED beacon at

the verified position and attaches the receiver facts to it.

• A heading while standing still. A magnetometer supplies the orientation a

receiver cannot, the World Magnetic Model converts it to true north from the

node's own position, and T383838tower near then prints the turn that aims a

directional antenna — T383838[Turn 15° RIGHT · 1 o'clock] — instead of a bearing to

interpret.

• A dashboard with no app. A traveler's phone in airplane mode that joins the

node's Wi-Fi has the survival dashboard opened for it by the operating

system's captive-network probe, with the Plus Code, a copy button, a live

compass rose pointing at the nearest repeater, the SOS button, and the offline

field assistant.

• The same answers on both paths. The portal and the radio commands share one

command registry restricted to its offline commands, and one GNSS receiver, so

the two can never disagree.

The portal binds an HTTP listener, so put it on the field node's own access point

(and behind the node's firewall on a shared network), or leave T383838portal_addr

empty to bind nothing at all.