Six ways to use this node, from the most basic to the most curious. None of them requires an account, a registration, or anything but a Reticulum client. The gateway has two doors, TCP and I2P: same node, same transport identity behind both.

Add this interface to your Reticulum configuration (~/.reticulum/config, under [interfaces]), then restart rnsd or your client:

You can also download this stanza as a file.

The gateway is a BackboneInterface in gateway mode with transport enabled: it forwards paths and announces for you, so a client with only this interface sees the whole network reachable from here. It listens on TCP; the LoRa radio on the LoRa page is linked to it — and to the second node below — by a TCP uplink of its own to each.

If the TCP port is filtered where you are, or you would rather not have your ISP see you talking to rns.arborisis.com, the same gateway is reachable as an I2P destination. You need an I2P router on your side (i2pd or Java I2P) with the SAM bridge enabled on its default port; then add:

No DNS, no IP address, no port to open on either side. Expect a slower start: an I2P tunnel takes a minute or two to come up, and the link carries less traffic than TCP — enough for messages and pages, which is what this node is for. The node's router is behind NAT and accepts no inbound router connections; that is a property of I2P routers, not of this destination, and it does not stop you from reaching it.

Arborisis Belgium 2 is a second Reticulum instance on a second machine, with a public door of its own on another address, another server and another tunnel: nothing on its path is shared with the gateway above, and its transport identity is its own. The two nodes are wired to each other. Add it next to the first stanza, not instead of it — a client with both has two ways in and takes the one that works:

The same second node over I2P, from its own router:

The stanza file above carries both nodes. Whether the second door answers right now is on the Status page — dialled in earnest, out to the internet and back in by the other path.

Within radio range, an RNode on the same channel as Arborisis Belgium Rnode (869.525 MHz · 125 kHz · SF8 · CR 4/5) reaches it with no internet at all — and, through it, both nodes of this page: the radio holds an uplink to each. The stanza, the band and what to expect are on the LoRa page.

If your client is not always online, messages sent to you are held here until you sync. In Sideband, MeshChat or NomadNet, select this node as your propagation node:

The node peers automatically with other propagation nodes (up to 100), so mail deposited elsewhere finds its way here, and mail deposited here finds its way out. Message store: 50 GB, oldest and largest messages purged first when full.

The second node runs a propagation node of its own, declared a static peer of this one — synchronised first, never evicted by the peer limit. Register on either; your mail is held on both, and if the machine behind one is off, the other still answers:

On a phone, the address is the same thirty-two characters as a QR code — the way NomadNet itself shows an address, so any scanner reads it back as text you can paste into Sideband:

Open [ Channels ] in NomadNet, add a new hub with this address, connect, then /list and /join lobby:

More on the rooms and the etiquette on the Chat page.

In Sideband, start a conversation with this address, open its Object details, and request telemetry. The node answers with its transport statistics, the state of the propagation node, the machine's load, memory, storage and uptime, and its position:

Requests are answered for anyone; nothing is sent unless asked. If your client is offline when the answer leaves, it waits for you on the propagation node above.

Everything on these pages, and a few things that are not, from a conversation. In Sideband, MeshChat or NomadNet, write to this address and send /help:

/status is the node right now, /history the last day as curves, /connect this very stanza (/connect file sends it as a file, /connect lora the radio's), /git the repositories and when they were last refreshed, /sign a line in the guestbook, /whoami what the node sees of you. /subscribe is the one thing no page can do: the bot writes to you when the node's state changes, and sends a daily digest — the only case where this node keeps your address, until /unsubscribe. It also sits in the hub's #lobby and answers !status. It reads the same measurement as these pages, and answers unavailable rather than guess.

Git works over Reticulum as over any other remote — the git-remote-rns helper is installed with Reticulum itself, so with rns on your system this just works:

- arborisis/arborisis-reticulum — The public web page of this node, and the API it reads

- upstream/reticulum — Reticulum Network Stack — the stack this node runs, mirrored from GitHub

- upstream/lxmf — LXMF — the message format and propagation node this node runs

- upstream/nomadnet — NomadNet — the page node and client, mirrored from GitHub

These are mirrors, refreshed from their upstream by the node every 24 hours. Reading needs no identity. To browse them instead — tree, files, commits, releases, statistics — open the Git node's own pages:

| Service | Address |

| ---- | ---- |

| NomadNet node (this page server) | ead3db61cc6eded01ff14377c1a9974c |

| LXMF propagation node | 4f51d3c606c1af5de79a6d6c8c09dc59 |

| RRC hub | 8637879d020faba7a099b3978fde5d85 |

| Git node — repositories (rns://) | 13a3f291dca1da5af23bdeb33adb7d38 |

| Git node — pages | 5df9932f419b768852123222d71a025c |

| Telemetry (Sideband, LXMF) | aebfc1e85edab874c14b622df20f41b2 |

| Bot (LXMF) | f3d717927e44b3b0546d66aca4f80583 |

| Transport identity (the gateway's name on the network) | 3aa2b18213d3238a121f112a9a63541f |

| Second node — gateway, TCP | rns2.arborisis.com:4242 |

| Second node — transport identity (its own) | daf98ea968fc81878a8286c2792ca1e6 |

| Second node — LXMF propagation node (static peer of this one) | 015ecb8938f5379fa0912ca29e0a04d3 |

| Second node — gateway over I2P | i2xv2k2tllq5asahxiz4oxr4qtmu4r2npkryhvhp37j3uhda6eba.b32.i2p |

| LoRa radio — transport identity (its own) | e54d7f60bb12156c7301bf2cad2f6405 |

| LoRa radio — interface hash (as RMAP lists it) | b41cc49821798c0ab41a1717c275d5d9 |

| Gateway over I2P (same transport identity) | ifyotoc7rq2ha4qoszzqw4js3tmlj4eg24whmxfrqk46csbabu4a.b32.i2p |

A permanent link to this page from anywhere on the network:

Everything above makes you a client: you see the network through this node, nothing you run is reachable through you. Standing up a node of your own that others can route through — a relay — is a different, and not much harder, thing. See the Relay page.