A radio, not a port. Arborisis Belgium Rnode is an RNode on air at 869.525 MHz, running a Reticulum transport of its own: anyone within range with an RNode on the same channel reaches it, and through it everyone else on the air — no internet, no account, no permission. The aim is plain: as much of Belgium on Reticulum over LoRa as possible, one radio at a time.

| | |

| ---- | ---- |

| Frequency | 869.525 MHz |

| Bandwidth | 125 kHz |

| Spreading factor | SF8 |

| Coding rate | 4/5 |

| TX power | 22 dBm |

| Board | Heltec WiFi LoRa 32 V3 |

| Transport identity (the radio's own) | e54d7f60bb12156c7301bf2cad2f6405 |

| Interface hash (as RMAP lists it) | b41cc49821798c0ab41a1717c275d5d9 |

869.525 MHz sits in the 869.4–869.65 MHz band, open across Europe up to 500 mW e.r.p. with a 10 % duty cycle, no licence needed. Same four parameters on both sides and the two radios hear each other; change one and they never will.

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

txpower is yours to pick — for your antenna and for the band's duty cycle; this page does not choose it for you. The same stanza is at the end of the downloadable interface file, under the TCP and I2P ones.

This radio keeps a transport of its own — the identity in the table above — and holds two TCP uplinks, in boundary mode: one to rns.arborisis.com:4242, one to rns2.arborisis.com:4242, the second node of the Connect page. What reaches it over the air is routed on by whichever of the two is up, the whole network answers back, and the internet's announces stay off the air unless a LoRa client asks for a path. One radio, two doors: the air keeps a road into the network when the machine behind either node is off.

What the Status page measures is the uplink as the first node sees it: the radio's announce one hop away over an open connection — or two hops away, relayed by the second node, which is what the first node sees once the direct uplink is gone and the other still carries. While the direct one holds, the second is declared, not measured: the path table keeps the shortest route.

An RNode is an off-the-shelf LoRa board and a firmware you flash in a minute — the hardware page of the Reticulum manual lists which boards, and rnodeconf does the flashing. Set these four parameters, put the antenna as high as you can, and you are the next dot on the map: discoverable = yes on your interface is all it takes to appear on https://rmap.world. Then sign the guestbook with the radio's name and it is listed on the Belgium page too, by hand.

A radio that also carries a client interface to the gateway — the Relay page — is the missing piece between the air and the internet: yours could be that piece before ours is.

The firmware this radio runs, pre-set to this channel and this gateway, is ours to give: Arborisis Relay, a fork of RTNode. One Heltec WiFi LoRa 32 V3, a USB cable, Chrome or Edge, and https://rns.arborisis.com/relay flashes the board and configures it — a name, your WiFi, where the antenna is — from the same tab. It comes up listening here, uplinked to rns.arborisis.com:4242 and to rns2.arborisis.com:4242 — one door per node, so it stays on the network when the machine behind either is off —, and on rmap.world within hours if you let it. The same page has the image and the esptool line for anyone without Web Serial.