ScotMesh RNS Network
The ScotMesh node
From the ScotMesh wiki
The ScotMesh node is a public Reticulum transport node for Scotland, reachable as rns.scotmesh.net. Anyone can connect to it, there is no registration and it costs nothing. It is the front page of this book; the pages after it cover each service in turn.
What it does
The node does four things:
• Carries traffic. It is a transport node with enable_transport on, so anything connected to it can reach anything it can reach: other ScotMesh users, and through our peers, the wider public Reticulum network. It relays encrypted packets only; it cannot read them.
• Hosts the chat room. An RRC (Reticulum Relay Chat) hub with the scotmesh room. See The chat room.
• Serves pages. A Nomad Network node with connection details and news, browsable from inside Reticulum with no internet needed.
• Holds messages for people who are offline. An LXMF propagation node, so a message sent to someone whose radio is off or who is out of range is delivered when they reappear.
Every address is on Services and addresses.
Where it is and what it runs on
The node is hosted in Dalgety Bay, Fife. It runs on Ubuntu, with one Reticulum daemon (rnsd) shared by the chat hub (rrc-hub (github.com/thatSFguy/reticulum-relay-chat)), the propagation node (lxmd), the Nomad Network node and an I2P router (i2pd) for the I2P entry point.
Its live status, updated every two minutes from the daemon itself, is on rns.scotmesh.net and at the top of this wiki's home page.
Ways in
TCP, rns.scotmesh.net port 4242
Use it when: You have an ordinary internet connection
Details: Connecting to ScotMesh
I2P
Use it when: You are behind CGNAT or a firewall you do not control
Details: Access over I2P
LoRa radio
Use it when: You are within range of a ScotMesh gateway
Details: RNode
What to expect
• Uptime. It is run by volunteers on a single machine. It is up almost all of the time, but it restarts for updates and it can go down. Reticulum copes with that: paths are found again when the node returns, and the propagation node delivers what was held.
• Reconnecting. Clients that reconnect quickly after a restart are welcome; the node's listener does not block them for it (see Known bugs and workarounds for why that needs saying).
• Privacy. The node sees which addresses are talking, as any transport node must, and nothing else. Messages, pages and files are encrypted end to end. Messages held by the propagation node are encrypted for their recipient. The chat hub keeps the chat room's messages for 7 days so newcomers can catch up; see The chat room.
• Announces. The node's services announce themselves every hour, so once you are connected they appear in your client's lists by themselves.
When it breaks
Check the status strip first. If it says the node is down, someone already knows. If it says up and you cannot connect, work through Troubleshooting, then tell us on the ScotMesh Discord (discord.gg/ytxfyuDmSt) or in the chat room once you are back on.
Running one yourself
The network gets more resilient with every transport node that is not ours. Running your own transport node explains what it commits you to and how to peer with us.
This is a copy of wiki.scotmesh.net/wiki/The_ScotMesh_node, last edited 2026-09-11. To change it, edit the page on the web wiki; this copy follows within 10 minutes.