A working wiki for Reticulum in Scotland. It documents the ScotMesh backbone, the projects we are building on it, and the practical notes that come out of actually running the thing. Everything you need to get on the network is on this page; the rest of the wiki is depth.
Backbone status
Live from the node itself — the same feed as rns.scotmesh.net, refreshed every two minutes. If the strip below is blank or says unknown, treat the backbone as unconfirmed and check the node page directly.
Connecting to the ScotMesh backbone
The backbone is a public Reticulum transport node hosted in Dalgety Bay, Fife. Anyone may connect, there is nothing to register, and it costs nothing. Pick one of the three ways in below. If you have never used Reticulum, the full walkthrough takes you from nothing to connected and explains each step.
Over the internet (TCP)
The normal way. Add this to your Reticulum config, or add it from the interface screen in MeshChatX if you would rather not edit files.
[[ScotMesh Backbone]]
type = TCPClientInterface
enabled = yes
target_host = rns.scotmesh.net
target_port = 4242
Over I2P
Works from behind CGNAT or a firewall you do not control, because no port needs forwarding at either end. Needs a local I2P router with the SAMv3 bridge enabled — see access over I2P.
[[ScotMesh I2P]]
type = I2PInterface
enabled = yes
peers = a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p
Over LoRa radio
No ScotMesh radio is on air yet — it is on the milestone list below. These are the settings the network uses, so that any radio built now will hear the others when they arrive. Every radio must match all five exactly: a board with a different spreading factor is not weakly connected, it is completely deaf, and nothing reports an error.
| ScotMesh 433 | ScotMesh 868 | |
|---|---|---|
| Frequency | 433.775 MHz | 867.500 MHz |
| Bandwidth | 125 kHz | 125 kHz |
| Spreading factor | 8 | 9 |
| Coding rate | 4/5 | 4/5 |
| TX power | 7 dBm | 22 dBm |
rnode.scotmesh.net flashes a board from your browser and applies either profile in one click. Boards, cables, Bluetooth and the config-file version of these settings are on the RNode page.
Whichever way in you chose: restart Reticulum, then run rnstatus. The ScotMesh interface should show as Up. If it does not, when it does not work lists the usual causes.
What runs on the backbone
Once connected, these are the addresses to paste into your client. Each one is explained in The ScotMesh Backbone.
| Service | Address | Use it with |
|---|---|---|
| TCP entry point | rns.scotmesh.net:4242
|
Any Reticulum client |
| I2P entry point | a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p
|
Any Reticulum client, via i2pd |
Chat hub (RRC), room scotmesh
|
004e5a15da221d9a236b0e8d74195f13
|
MeshChatX, rrc
|
| LXMF propagation node | c283b754e0acc11ce48d2f5e29167e0c
|
Sideband, MeshChatX, Nomad Network |
| Nomad Network node | 10a839df2c50635bcb0c8a299b9ca0f8
|
Nomad Network, MeshChatX |
| Transport instance | 20b962cd814444f7812e409e7c47f319
|
Shows up in rnpath and node maps
|
The node peers outward to rebelnet.uk, rns.cybercore.uk and rmap.world, so a client connected here can reach the rest of the public Reticulum network. The live node page is rns.scotmesh.net.
Milestones
Where the network actually is, rather than where we would like it to be. Updated by hand as things land.
| Milestone | Notes | |
|---|---|---|
| ✔ | Reticulum backbone online | Public transport node at rns.scotmesh.net:4242, peered into the wider network.
|
| ✔ | Reachable over I2P | No port forwarding needed at either end. |
| ✔ | Chat hub running | RRC hub with the scotmesh room.
|
| ✔ | Propagation node running | Offline message delivery for the region. |
| ✔ | Web flasher for RNodes | rnode.scotmesh.net, with both ScotMesh profiles built in. |
| ✘ | 433 MHz RNode on air | Not yet built. |
| ✘ | 868 MHz RNode on air | Not yet built. |
Where next
The wiki is arranged by what you are trying to do. Much of it is still an outline — if a page looks thin, it has not been written yet rather than deliberately left out.
| I have never used Reticulum | Read in order: what Reticulum is → how it compares to Meshtastic, MeshCore and LoRaWAN → connecting to ScotMesh → choosing a client → first steps. |
| I am connected — what can I do? | Join the chat room, send messages that arrive even when the other person is offline via the propagation node, or browse and host pages on Nomad Network. |
| I want to put a radio on air | RNode for boards, flashing and the settings above; antennas and siting for making it actually reach anywhere. |
| I want to help carry traffic | Running your own transport node. Tell us when it is up and we will peer with you. |
| Something is broken | Troubleshooting, then known bugs and workarounds — the 12-hour lockout and the i2pd crash are both in there. |
| What is ScotMesh building? | The project index: MeshTransit and MeshCore as a Reticulum interface. |
| What does that word mean? | The glossary. |
About the node itself — where it runs, who we peer with, what to expect — is in The ScotMesh node. Or use the search box at the top of any page.