ScotMesh Wiki - User contributions [en-gb]

Troubleshooting

2026-09-17T12:36:45Z

ScotMesh: Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

Symptom first, then the usual cause and what to do. Start with the three commands, then find your symptom below. Faults that took someone more than an hour to work out have their own entries in [[Known bugs and workarounds]].

== The three commands ==

{| class="wikitable"
! Command !! Tells you
|-
| <code>rnstatus</code> || Every interface: Up or Down, and traffic in and out. '''Run this first.'''
|-
| <code>rnpath -t <address></code> || Whether your node knows a path to an address, how many hops, and via which interface. Add <code>-t</code> to ask the network if it does not.
|-
| <code>rnprobe <address></code> || Sends a probe and reports the round-trip time, proving the destination is actually there and answering.
|}

If you installed Reticulum in a virtual environment, use the full path, for example <code>~/reticulum/bin/rnstatus</code>. In MeshChatX the same information is on the Interfaces page and in its log.

== Reading rnstatus ==

<syntaxhighlight lang="text">TCPInterface[ScotMesh Backbone/rns.scotmesh.net:4242]
Status : Up
Traffic : ↑1.2 KB ↓14.8 KB</syntaxhighlight>

* '''Status: Up''' means the connection is open. It does not by itself mean the far end is a working transport node; traffic climbing does.
* '''Traffic''' should rise within a minute or two of connecting, because announces arrive. Up with no traffic for five minutes is a fault.
* An interface '''missing entirely''' from the list was not loaded: usually indentation in the config file.

== Symptoms ==

=== Interface shows Down ===

{| class="wikitable"
! If it is !! Then
|-
| The TCP interface || No route out, or a typo in the hostname or port. <code>ping rns.scotmesh.net</code>; check the [[Main Page|status strip]] to see whether the node itself is down.
|-
| The I2P interface, in the first ten minutes || Normal. Tunnels are still being built.
|-
| The I2P interface, for longer || Is i2pd running, and is SAM enabled on port 7656? If i2pd keeps restarting, see [[Known bugs and workarounds]].
|-
| An RNode || Wrong port, or the board is not in the right mode. <code>rnodeconf -i /dev/ttyUSB0</code> should answer; if not, check the cable and that nothing else has the port open.
|}

=== Interface is not in the list at all ===

The config file did not load that block. Check that it sits under <code>[interfaces]</code>, that <code><nowiki>[[Name]]</nowiki></code> is indented two spaces and its settings four, and that <code>enabled = yes</code> is present. <code>rnsd -v</code> prints config errors on start.

=== No path to a destination ===

You cannot reach what has not announced. Wait a couple of minutes after connecting, then <code>rnpath -t <address></code> to ask for it. If a path never appears, either the address is wrong, the destination is offline, or nothing between you and it is a transport node.

=== A client hangs on “securing link” ===

The far end is not answering the link request. If it is our node, and other hubs work from the same client, you may have been locked out by the fast-flapping block; [[Known bugs and workarounds]] explains. Otherwise the destination has gone away since it announced; wait for the next announce.

=== Messages do not arrive ===

* The recipient is offline and neither of you has a [[Propagation node|propagation node]] set. Set ours.
* You have one set but have not synced: ask your client to fetch from the propagation node.
* The recipient has never announced to you. Ask them to announce (every client has a button), or paste their address.

=== My node never appears on anyone's list ===

You are announcing too rarely. Nodes announce every six hours by default; set 30 to 60 minutes ([[Running your own transport node#3. Announce often enough|how]]). Node maps such as rmap.world also need the node to be reachable from their side.

=== Two LoRa radios cannot hear each other ===

Frequency, bandwidth, spreading factor and coding rate must match exactly. A mismatch gives no error; the radios are simply deaf to each other. Compare against the [[RNode|ScotMesh profile]]. Then check the antenna is for the right band and actually connected: transmitting into no antenna at 22 dBm can damage the radio.

=== Everything worked yesterday ===

Restart <code>rnsd</code> (or the app). Reticulum keeps paths and links in memory, and after a long run with interfaces coming and going a restart clears stale state. Then check the status strip: the node itself may have restarted.

== Reading the daemon log ==

<code>rnsd -vv</code> in a terminal shows what the daemon is doing in real time: interfaces coming up, announces received, paths learned, link requests. Most puzzles are solved by watching it for a minute while you try the thing that fails. As a service, <code>journalctl -u rnsd -f</code> shows the same.

== Still stuck ==

Ask in [[The chat room|the chat room]] if you can reach it, or on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord] if you cannot. Include the output of <code>rnstatus</code> and what you expected to happen.

[[Category:Operations]]

The ScotMesh node

2026-09-17T12:36:44Z

ScotMesh: rrc-hub retired: the chat room is run by the ScotMesh chat hub

The '''ScotMesh node''' is a public Reticulum [[Glossary#Transport node|transport node]] for Scotland, reachable as <code>rns.scotmesh.net</code>. 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 <code>enable_transport</code> on, so anything connected to it can reach anything it can reach: other ScotMesh users, and through [[Who we peer with|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 <code>scotmesh</code> 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|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 (<code>rnsd</code>) shared by the propagation node (<code>lxmd</code>), the Nomad Network node and an I2P router (<code>i2pd</code>) for the [[Access over I2P|I2P entry point]].

Its live status, updated every two minutes from the daemon itself, is on [https://rns.scotmesh.net rns.scotmesh.net] and at the top of this wiki's [[Main Page|home page]].

== Ways in ==

{| class="wikitable"
! Way in !! Use it when !! Details
|-
| TCP, <code>rns.scotmesh.net</code> port 4242 || You have an ordinary internet connection || [[Connecting to ScotMesh]]
|-
| I2P || You are behind CGNAT or a firewall you do not control || [[Access over I2P]]
|-
| LoRa radio || You are within range of a ScotMesh gateway || [[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|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 [https://discord.gg/ytxfyuDmSt ScotMesh Discord] 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.

[[Category:The ScotMesh Backbone]]

Services and addresses

2026-09-17T12:36:43Z

ScotMesh: Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

Every address for the ScotMesh node in one place. This is the page to copy from; each service is explained on its own page.

== Entry points ==

{| class="wikitable"
! Way in !! Address !! Notes
|-
| TCP || <code>rns.scotmesh.net</code>, port <code>4242</code> || The normal route. Interface type <code>TCPClientInterface</code>. See [[Connecting to ScotMesh]].
|-
| I2P || <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code> || For networks that block outbound connections. Interface type <code>I2PInterface</code>. See [[Access over I2P]].
|-
| LoRa || ScotMesh 868 radio profile || Within range of a gateway only. See [[RNode]].
|}

== Services ==

{| class="wikitable"
! Service !! Address !! Reached from
|-
| Chat hub (RRC), room <code>scotmesh</code> || <code>004e5a15da221d9a236b0e8d74195f13</code> || MeshChatX, Ratspeak, rrc-tui, rrc-gui, WeeChat, Eridanus. See [[The chat room]].
|-
| LXMF propagation node || <code>c283b754e0acc11ce48d2f5e29167e0c</code> || Sideband, MeshChatX, Nomad Network, usually picked automatically. See [[Propagation node]].
|-
| Nomad Network node || <code>10a839df2c50635bcb0c8a299b9ca0f8</code> || Nomad Network, MeshChatX. Entry page <code>10a839df2c50635bcb0c8a299b9ca0f8:/page/index.mu</code>. See [[Nomad Network]].
|-
| Transport instance || <code>20b962cd814444f7812e409e7c47f319</code> || Not something you connect to: it is the node's own identity, and what appears in <code>rnpath</code> output and on node maps. Announced as “ScotMesh Backbone”.
|}

== Radio profile ==

Every radio on the network must use exactly these settings; see [[RNode]] for why.

{| class="wikitable"
! !! ScotMesh 868
|-
| Frequency || 869.4625 MHz
|-
| Bandwidth || 125 kHz
|-
| Spreading factor || 9
|-
| Coding rate || 4/5
|-
| TX power || 22 dBm
|}

== Which addresses could change ==

* The '''hostname and port''' are stable.
* The '''destination addresses''' (chat hub, propagation node, Nomad Network node, transport instance) are derived from identity keys the node keeps backed up. They would only change if a key were lost or deliberately replaced, and we would say so here and on [https://rns.scotmesh.net rns.scotmesh.net].
* The '''I2P address''' is derived from a random key. It is backed up too, but of all the addresses it is the one most likely to change one day, so check here if it stops working.

[[Category:The ScotMesh Backbone]]

ScotMesh microReticulum

2026-09-17T12:36:42Z

ScotMesh: Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

'''ScotMesh microReticulum''' is our build of [https://github.com/attermann/microReticulum_Firmware attermann's microReticulum firmware]. It turns a LoRa board into its own Reticulum transport node, so a board on a hill or a roof can relay for the mesh with no Raspberry Pi. On top of upstream it adds:

* the SenseCAP Solar Node P1;
* battery reporting;
* a NomadNet page you can manage the node from over the mesh;
* a small telemetry API;
* a position on [https://rmap.world rmap.world].

Source: [https://github.com/ScotMesh/microReticulum_Firmware github.com/ScotMesh/microReticulum_Firmware]. Firmware: [https://rnode.scotmesh.net rnode.scotmesh.net] (choose ''Standalone node'').

== Boards ==

{| class="wikitable"
|-
! Board
! Node pages & API
! Firmware update over the air
|-
| Seeed SenseCAP Solar Node P1 🏴󠁧󠁢󠁳󠁣󠁴󠁿 built by ScotMesh
| Yes
| Bluetooth update window, or USB bootloader
|-
| Heltec V2/V3/V4, Heltec Wireless Tracker V2, XIAO ESP32S3, T-Beam Supreme, T-Deck
| Yes
| WiFi update window
|-
| T-Beam, T3S3, LoRa32 v1/v2/v2.1, RNode NG 2.0/2.1, Feather ESP32, generic ESP32
| Yes
| USB only (one firmware slot)
|-
| RAK4631, RAK3401, T-Echo
| Original microReticulum pages (the new ones don't fit their flash yet)
| USB
|}

== Setting a node up ==

# Open [https://rnode.scotmesh.net rnode.scotmesh.net] in Chrome or Edge on a computer. Choose '''Standalone node''', pick your board, and flash.
# On the configure step:
#* pick '''ScotMesh 868''';
#* give the node a name;
#* choose its role (normally ''Fixed relay'');
#* paste your identity hash under ''Remote management''. That makes you its admin.
# The node restarts in transport mode and announces its NomadNet page. You can do everything else from that page over the mesh.

== Using the node's page ==

Open the node's NomadNet address in Nomad Network or MeshChatX. You'll find the address:

* at the end of the flasher;
* on the node's ''About'' page;
* in the node's announce.

Every page is small enough to arrive in '''one LoRa packet''', so it loads first time even on weak links. Most are 150–300 bytes, and the limit is 409.

''The screenshots below are the real pages, fetched over LoRa from our bench P1 (3 hops, through rns.scotmesh.net and a gateway). What you see in your browser depends on its colours.''

=== Home page ===

[[File:home.png|frameless|upright=2.2|The node's home page as a visitor sees it]]

The home page shows:

* the node's name;
* its battery, as a bar (green / amber / red) with % and voltage, plus <span style="color:#22cc55;">▲</span> while charging or <span style="color:#dd9933;">▼</span> while discharging;
* uptime and the number of known routes.

An admin can also show the radio settings, airtime and an operator line. The footer always shows the firmware version and the board. ''Not identified'' means your browser hasn't identified to the node. That's fine for visitors.

=== Routes and neighbours ===

[[File:routes.png|frameless|upright=2.2|Routes page with short addresses]]

'''Routes''' lists the node's path table: destination, hops and when it was last heard. '''Neighbours''' lists the transport nodes it hears directly, with their names where they announce one. To change the view:

* tick ''Short'' for 8-character addresses (or leave it off for full ones);
* set ''Rows'' and press ''Apply'';
* use ''next'' and ''back'' to page through.

An admin can hide both pages from visitors.

=== Becoming an admin ===

You are an admin if your identity is on the node's remote-management list (the same list <code>rnstatus -R</code> checks). In your browser, choose '''Identify''' for the node (NomadNet: the ''Identify'' option on the page; MeshChatX: ''identify to this node'') and reload. The page then shows 🛡️ ''Verified identity'' and an '''Admin''' link. There is no password to log in with: being identified is being logged in.

[[File:home-admin.png|frameless|upright=2.2|Home page seen by an admin]]

Admins see every row. A <code>*</code> marks rows that visitors don't see.

If an admin has switched on '''password registration''', a visitor who has identified sees ''Register''. Entering the password adds their identity as an admin, or puts them in a queue for an existing admin to approve.

=== The admin pages ===

[[File:admin-hub.png|frameless|upright=2.2|Admin hub]]

The hub shows battery and uptime, and warns you when a radio trial needs confirming or someone is waiting for approval. It links to three sections.

{| class="wikitable"
|-
! Section
! Pages
|-
| Settings
| '''Name & announce''': renaming announces straight away. Announce every 30 min, 1 h, 3 h, 6 h or 12 h.<br />
'''Home page''': what visitors see, telemetry API on or off, and a visitor preview.<br />
'''Map''': rmap.world position.<br />
'''Radio''', '''Role''', '''Power'''
|-
| Access
| '''Admins''': add by identity hash; remove with confirmation.<br />
'''Password''' registration.<br />
'''Change log''': every admin change, with time and who made it.
|-
| Device
| '''Health''': free RAM and flash, starts and last reset reason, noise floor, last RSSI/SNR, airtime, packets, table sizes.<br />
'''Lights & Bluetooth''', '''Logs''' (last five log lines), '''Maintenance''', '''Restart & update''', '''About'''
|}

[[File:settings.png|frameless|upright=2.2|Settings section]]

[[File:device.png|frameless|upright=2.2|Device section]]

==== Name & announce ====

[[File:name.png|frameless|upright=2.2|Name and announce page]]

Change the name, set an optional operator line (e.g. a callsign) and set how often the node announces its page. Longer intervals save airtime on a busy channel. Renaming announces at once.

==== Home page layout ====

[[File:home-layout.png|frameless|upright=2.2|Home page layout settings]]

Tick what visitors may see. ''Preview'' shows the page as a visitor would see it. ''Telemetry API'' turns the <code>/api</code> endpoints on or off.

==== Radio and role ====

[[File:radio.png|frameless|upright=2.2|Radio page]]

'''Radio changes are a trial.''' Enter new settings (or pick ''ScotMesh 868'') and press ''Try these''. The node uses them for five minutes. Reconnect on the new settings and press ''Keep''. If you don't, the node goes back to the old settings by itself, so a mistake can't strand a remote node.

[[File:role.png|frameless|upright=2.2|Role page]]

'''Role''':

* ''Fixed relay'': forwards for everyone. Use it for hilltop and roof nodes.
* ''Access point'': for a node that serves nearby clients.
* ''Mobile'': for a node that moves.
* ''End device'': never forwards.

A role change applies after a restart.

==== Power ====

[[File:power.png|frameless|upright=2.2|Power page]]

Below a chosen battery level, the node can lower its TX power to 10 dBm or turn its radio off until it has charged. It can also keep its radio off below 3.3 V to protect the cell.

==== Admins and password registration ====

[[File:admins.png|frameless|upright=2.2|Admins page]]

[[File:password.png|frameless|upright=2.2|Password registration page]]

* '''Admins''' (up to 8): paste a 32-character identity hash and press ''Add''. Tap an identity to remove it; you're asked to confirm. The node won't remove its last admin.
* '''Password registration''' is off by default. An admin sets a password. Someone who knows it can identify to the node and register their own identity as an admin.
** Three wrong tries lock that identity for 15 minutes.
** Ten wrong tries in an hour pause registration.
** With ''Needs approval'' ticked, new registrations wait for an existing admin.

==== Health, lights and Bluetooth ====

[[File:health.png|frameless|upright=2.2|Health page]]

[[File:lights.png|frameless|upright=2.2|Lights and Bluetooth page]]

'''Lights''':

* the activity LEDs can be on, off, or on only for the first 10 minutes after a start;
* ''Blink 30 s'' helps you find a node on a mast;
* error patterns always show.

'''Bluetooth''' can be turned off to save power on a sealed box. ''Unpair all'' forgets paired phones.

==== Maintenance ====

[[File:maintenance.png|frameless|upright=2.2|Maintenance page]]

From here you can:

* announce now;
* restart automatically every day or every week;
* clear stored routes and data;
* factory reset. This keeps the node's identity and its admins.
* full reset. The node forgets its identity too: new addresses, no admins, no settings. Use it to hand a node on, or before re-flashing it as a different node. Afterwards it needs USB to make it yours again (the flasher's ''Reconfigure'' path).

Anything disruptive asks you to confirm, with a link that works once, for two minutes.

=== Restart and firmware updates without a cable ===

[[File:update.png|frameless|upright=2.2|Restart and update page]]

Updates are started from the node's page over the mesh, but the firmware itself is too big to send over LoRa, so someone has to be near the node with a phone or laptop for the transfer. The node accepts the new image's hash by itself afterwards; you don't need <code>rnodeconf</code> or the flasher.

'''WiFi update''' (ESP32 boards with two firmware slots: Heltec V2/V3/V4, Tracker V2, XIAO ESP32S3, T-Beam Supreme, T-Deck):

# ''Device → Restart & update → WiFi update → Yes, start''. The page shows a one-time WiFi password. Write it down; it is shown once.
# The node restarts as a WiFi access point called '''ScotMesh-Update''', off the mesh, for '''20 minutes'''.
# Within WiFi range, join that network with the password and open '''<nowiki><nowiki>http://192.168.4.1</nowiki></nowiki>'''.
# Choose the <code>.bin</code> from inside the board's release zip (for example <code>rnode_firmware_heltec32v3.bin</code>) and press ''Update''. The node verifies it and restarts into the new firmware.

A WiFi update leaves the node running from its second firmware slot. That's fine for the flasher (it always resets the slot choice), but if you later update by hand with <code>esptool</code> or <code>rnodeconf</code>, write <code>boot_app0.bin</code> at <code>0xE000</code> as well as the firmware, or the board keeps booting the old slot and refuses to start transport ("device init failed").

If nothing is uploaded in 20 minutes, or the upload fails, the node restarts unchanged. The 4 MB boards (T-Beam, T3S3, LoRa32, RNode NG, Feather, generic ESP32) have one firmware slot and can only be updated over USB.

'''Bluetooth update''' (SenseCAP P1):

# This restarts the node with a Bluetooth firmware-update service for '''20 minutes'''. It advertises as <code>SenseCAP P1 DFU</code>.
# Within Bluetooth range, open '''nRF Device Firmware Update''' or '''nRF Connect''' on a phone.
# Send the node's <code>rnode_firmware_seeed_solar_node_p1.zip</code> from the [https://github.com/ScotMesh/microReticulum_Firmware/releases releases].

If nothing connects, the node restarts normally when the window closes.

'''USB bootloader''' is for someone on site with a laptop. The node waits in its bootloader until it is flashed (for example from rnode.scotmesh.net) or reset.

None of these start below 30 % battery unless the node is charging.

=== Starting a node from scratch ===

The flasher keeps a node's identity, settings and routes across a reflash, which is what you want for an update. To wipe a node and start again (a second-hand board, or one you want new addresses for), tick '''Start from scratch: erase everything first''' on the flasher's Flash step. On ESP32 boards that erases the whole flash; on the P1 and other nRF52 boards it asks the firmware for a full reset and wipes the EEPROM. Either way the node comes back with a new identity and the flasher provisions and configures it again.

== Showing the node on rmap.world ==

[[File:map.png|frameless|upright=2.2|Map page after saving a position]]

# On ''Settings → Map'', paste the node's position straight from Google Maps. Right-click the spot and click the coordinates, e.g. <code>56.19858019391934, -3.1666195614405708</code>. Degrees-minutes-seconds works too.
# Set its height in metres.
# Choose ''Exact'' or ''~1 km''.
# Tick ''Publish'' and save.

The node then sends the standard Reticulum interface-discovery announce on the announce interval. It's the same announce a PC node sends with <code>discoverable = yes</code>. rns.scotmesh.net peers with rmap.world, so the announce reaches the map through the backbone.

The position is public once published. Use ''~1 km'' if that matters.

== Telemetry API ==

For trackers and dashboards, the node answers plain JSON requests on the same NomadNet address.

* '''No identity is needed.'''
* An admin can switch the API off under ''Home page''.
* Each reply fits in one packet.
* List endpoints page with <code>o</code> (offset) and <code>n</code> (rows), and add <code>"more": true</code> when there are more rows.

{| class="wikitable"
|-
! Path
! Request data
! Reply (real examples from the bench P1)
|-
| <code>/api</code>
| —
| <code>{"v":1,"api":["bat","up","radio","net","sys","health","pos","paths","nbrs","all"]}</code>
|-
| <code>/api/bat</code>
| —
| <code>{"percent":96,"voltage":4.11,"charging":true}</code>
|-
| <code>/api/up</code>
| —
| <code>{"uptime":134,"reset":"soft-reset"}</code>: seconds since start, and why it last started
|-
| <code>/api/radio</code>
| —
| <code>{"freq":869462500,"bw":125000,"sf":9,"cr":5,"txp":22,"airtime":4.4,"noise":-105,"rssi":-59,"snr":10}</code>
|-
| <code>/api/net</code>
| —
| <code>{"routes":159,"neighbours":1,"rx":20,"tx":18,"links":1}</code>
|-
| <code>/api/sys</code>
| —
| <code>{"fw":"v1.86-scotmesh.3","board":"SenseCAP P1","name":"…","free_ram":33472,"free_flash":1822720}</code>
|-
| <code>/api/health</code>
| —
| <code>{"free_ram":33472,"free_flash":1822720,"reboots":7,"reset":"soft-reset","paths":159,"paths_max":500,"announces":0,"neighbours":1}</code>
|-
| <code>/api/pos</code>
| —
| <code>{"lat":56.19858,"lon":-3.16662,"height":310}</code>, or <code>{"error":"not published"}</code>
|-
| <code>/api/all</code>
| —
| battery + uptime + network + airtime in one reply
|-
| <code>/api/paths</code>
| <code>{"o":0,"n":5,"s":0}</code>
| <code><nowiki>{"total":159,"o":0,"cols":["dest","hops","age_s","via"],"rows":[[…],…],"more":true}</nowiki></code>
|-
| <code>/api/nbrs</code>
| <code>{"o":0,"n":5,"s":1}</code>
| <code>{"total":1,"o":0,"cols":["dest","age_s","name"],"rows":[…]}</code>
|}

<code>s=1</code> gives 8-character addresses. Unknown paths answer <code>{"error":"unknown endpoint","see":"/api"}</code>. If the node is short of memory, it answers <code>{"error":"busy"}</code>.

Here's a tracker in Python. It needs Reticulum installed and connected to the mesh, e.g. with a TCP interface to <code>rns.scotmesh.net</code> port 4242:

<syntaxhighlight lang="text">import RNS, json, time
RNS.Reticulum()
node = bytes.fromhex("cb37c17f7280d61d66b5278a02313d25") # the node's NomadNet address
if not RNS.Transport.has_path(node):
RNS.Transport.request_path(node)
while not RNS.Transport.has_path(node): time.sleep(0.5)
dest = RNS.Destination(RNS.Identity.recall(node), RNS.Destination.OUT,
RNS.Destination.SINGLE, "nomadnetwork", "node")
link = RNS.Link(dest) # no identify() needed
while link.status != RNS.Link.ACTIVE: time.sleep(0.2)
link.request("/api/all", response_callback=lambda r: print(json.loads(r.response)))
link.request("/api/paths", data={"o": 0, "n": 5},
response_callback=lambda r: print(json.loads(r.response)))</syntaxhighlight>
Keep one link open and poll every few minutes. Each request and reply is a single small packet (typically 3–5 s round trip over three hops).

== Good to know ==

<ul>
<li>The node keeps its settings in its own flash. Its identity and admin list survive firmware updates and a factory reset.</li>
<li>One exception: RNode NG 2.0/2.1 and LoRa32 v2.1 nodes flashed with v1.86-scotmesh.2 or earlier get a new identity when updated to .4 or later, because those boards moved to a larger app slot (2.25 MB) to fit the pages. Add the node's new identity to your admin list again afterwards. Updates after that keep the identity.</li>
<li>Memory is watched:
<ul>
<li>pages and the API never copy the route table;</li>
<li>the change log is a fixed 1.3 KB file;</li>
<li>below about 8 KB of free RAM, the node answers "busy" rather than risk running out.</li></ul>

''Health'' and <code>/api/health</code> show free RAM, so a slow leak shows up as a trend.</li>
<li>The LEDs on the P1:
<ul>
<li>white flash: packet received;</li>
<li>blue flash: packet sent;</li>
<li>blue and white alternating fast: the radio failed to start (the node restarts itself after a few seconds).</li></ul></li>
<li>Full debug logging stays in the firmware. Connect over USB and open a serial console at 115200 to see it.</li>
<li>Upstream differences and the full change history are in the repository's README.</li></ul>

[[Category:Hardware]]

ScotMesh Mail

2026-09-17T12:36:41Z

ScotMesh: Repository is private: drop the dead link

'''ScotMesh Mail''' is email over Reticulum. Your Reticulum identity is your login, so there are no passwords. Mail between people on the mesh never touches the internet, and a gateway links <code>@mail.scotmesh.net</code> to ordinary email.

== What it is ==

A mail server, '''rmail''', and the ways to use it:

* '''MeshChatX''': a plugin with folders, writing and replying, encrypted and signed mail, and your mail key.
* '''Nomad Network''': the server is also a node with webmail pages, readable in NomadNet or MeshChatX's page browser.
* '''Sideband''' and any other LXMF app: message the server's '''postmaster'''. It sends a notice when mail arrives, can forward whole messages, and takes commands such as <code>STATUS</code>, <code>INBOX</code>, <code>READ</code> and <code>REPLY</code>. Start a message with <code>to: someone@…</code> to send mail.

Several identities can share one mailbox, for example your phone and your laptop, or a group's shared address. Mail can be kept encrypted on the server with keys only the mailbox's members hold. Mail is text only and kept small, because it crosses radio links: attachments are refused.

Servers announce themselves like Nomad Network nodes, and anyone can run one. Addresses look like <code>name@<server address>.rns</code> on the mesh, and <code>name@mail.scotmesh.net</code> from the internet.

== Status ==

'''Prototype''', as of 13 September 2026. The ScotMesh server is running and joined to [[The ScotMesh Backbone|the backbone]], with the first mailbox. Sign-up is by invitation only. Mail from the internet is waiting on its firewall port being opened, and mail to the internet may land in spam folders for now, because the server's address can't be given a matching reverse DNS name.

== Where to find it ==

{| class="wikitable"
! What !! Address
|-
| Mail server || <code>45b45ffb1ce546993728cb31e9846b95</code>
|-
| Postmaster (LXMF) || <code>044b450f5f66efc790c25d703121d4a5</code>
|-
| Webmail (Nomad Network) || <code>65f06cd68ddedd8929471af0d82c1a7d:/page/index.mu</code>
|-
| Internet domain || <code>mail.scotmesh.net</code>
|}

It runs on ScotMesh's own server alongside the [[ScotMesh chat hub|chat hub]], and stores messages for mailboxes that are away through the [[Propagation node|propagation node]]. The code is in a private repository for now and has no licence yet.

== Who is working on it ==

Alex.

== Next ==

* Open the mail port so internet mail can arrive, and send a first message each way.
* Try the MeshChatX plugin with real users, and write a how-to page like [[The chat room]].
* Choose a licence and publish the code.
* Send out the first invitations.

[[Category:Projects]]

ScotMesh firmware

2026-09-17T12:36:41Z

ScotMesh: Firmware repository moved to ScotMesh/microReticulum_Firmware

'''ScotMesh firmware''' is our build of [https://github.com/attermann/microReticulum_Firmware microReticulum], the firmware that turns a LoRa board into a self-contained Reticulum [[Glossary#Transport node|transport node]]: a relay that carries traffic for everyone around it, with no Raspberry Pi or computer attached. We add the things a node needs when nobody can get to it: a page to look after it from anywhere on the mesh, a small telemetry feed, and firmware updates without a cable.

This page explains why we build it and what it adds. The complete guide to every page and setting is [[ScotMesh microReticulum]].

== Why Scotland needs it ==

Scotland is a big country for its population. The places that most need a network that does not depend on the internet or the mobile networks are glens, islands, hill farms and villages at the end of single-track roads. They are also the places where a relay has to sit on a hilltop or a mast, run on sunlight, and get through a winter without anyone visiting.

That changes what a node's firmware has to do. A relay in a city can be walked to in ten minutes. A solar node on a Highland hill or an island can be hours away by road and ferry, and in bad weather out of reach for weeks. So for us:

* '''Every visit is expensive.''' Anything that would normally need a laptop and a USB cable should be possible over the mesh instead.
* '''Nodes run on batteries and sunlight.''' Their owners need to see battery and charging from far away, and the node should protect itself when the sun does not come out.
* '''Settings change after installation.''' A radio gets retuned, a node gets renamed, looking after it passes to someone else. None of that should mean a trip up a hill.
* '''Firmware needs updating''' without taking the node down from the mast, and without any risk of leaving it dead if an update goes wrong.

Upstream microReticulum is an excellent base, but it assumes the owner is nearby with a USB cable. The ScotMesh build adds the remote side. The more of Scotland the network reaches, the more of its nodes will be remote ones, which is why this matters more here than in most places.

== What it adds ==

{| class="wikitable"
! Feature !! What it does
|-
| '''The node's own page''' || A [[Nomad Network]] page served from the radio board: name, battery bar with charging arrow, uptime, routes and neighbours. Every page fits in a single LoRa packet, so it loads first time even over a weak link.
|-
| '''Remote management''' || Admin pages for the node's owners: name and announce interval, radio settings (tried for five minutes, then kept or undone automatically), role, power saving, admins and password registration, a change log, health, lights and Bluetooth, logs, maintenance and restart.
|-
| '''Telemetry''' || A small JSON feed (battery, uptime, radio, routes, neighbours, position) that anyone can read without an identity, for dashboards and trackers.
|-
| '''Updates without a cable''' || A 20-minute update window opened from the admin page: over Bluetooth on the SenseCAP Solar Node P1, over WiFi on ESP32 boards with two firmware slots.
|-
| '''rmap.world''' || Puts the node on the Reticulum network map, with an exact or approximate position.
|-
| '''Full reset''' || Wipes the node back to a new identity, from its page or from the [https://rnode.scotmesh.net flasher].
|-
| '''SenseCAP Solar Node P1''' || Support for Seeed's solar node: battery reporting, charging, the solar-friendly power settings above.
|}

== Looking after a node from home ==

[[File:scotmesh-remote-management.svg|center|frameless|1000px|How an admin reaches a remote node: laptop, internet, the ScotMesh backbone, a LoRa gateway, then the solar node]]

You open the node's address in a Nomad Network browser, exactly like any other node. Your request crosses the internet to the [[The ScotMesh node|ScotMesh backbone]], goes out over LoRa through one or more radio hops, and the node answers with a page small enough to fit in one radio packet.

Anyone can read the public page and the telemetry. The admin pages only open for identities on the node's admin list: you add yourself when you set the node up with the [https://rnode.scotmesh.net flasher], and admins can add others from the page itself. There is no password to type over the radio; being [[Glossary#Identity|identified]] is being logged in.

== The node's own page ==

<gallery mode="packed" heights="230px">
File:home.png|The home page, as a visitor sees it
File:admin-hub.png|The admin hub
File:health.png|Health: memory, starts, radio, tables
File:radio.png|Radio changes are a five-minute trial
File:map.png|Position for rmap.world, pasted from Google Maps
File:update.png|Restart and firmware update
</gallery>

These are the real pages, fetched over LoRa from our bench SenseCAP P1 through three hops. The [[ScotMesh microReticulum]] guide goes through every one.

== Updating without a cable ==

[[File:scotmesh-update-flow.svg|center|frameless|upright=3.6|Update flow: open the window from home, someone nearby uploads, the node checks the image and comes back]]

Firmware images are far too big to send over LoRa, so an update still needs someone within Bluetooth or WiFi range of the node, with a phone. What it no longer needs is a cable, a laptop, or taking the node down from where it is mounted.

[[File:wifi-update-page.png|right|frameless|upright=0.9|The upload page a WiFi update window serves at 192.168.4.1]]

* '''SenseCAP Solar Node P1:''' the node advertises as ''SenseCAP P1 DFU'' for 20 minutes. Send it the release zip with Nordic's free '''nRF Device Firmware Update''' app ([https://play.google.com/store/apps/details?id=no.nordicsemi.android.dfu Android], [https://apps.apple.com/app/nrf-device-firmware-update/id1624454660 iPhone]).
* '''Heltec V2/V3/V4, Wireless Tracker V2, XIAO ESP32S3, T-Beam Supreme, T-Deck:''' the node becomes a WiFi hotspot called ''ScotMesh-Update'' for 20 minutes, protected by a one-time password shown on the admin page. Join it, open <code><nowiki>http://192.168.4.1</nowiki></code> and upload the <code>.bin</code> from the release.
* '''T-Beam, T3S3, LoRa32, RNode NG, Feather and generic ESP32:''' these boards have a single firmware slot, so they update over USB with the [https://rnode.scotmesh.net flasher].

The step-by-step guide, with app links, is at [https://rnode.scotmesh.net/update.html rnode.scotmesh.net/update.html].

'''Why it is safe.''' Every node checks at start-up that its firmware is the image its owner installed, and refuses to carry traffic if it is not. An update started from the admin page tells the node to accept the next image once, so it comes straight back on the mesh with its identity, admins and settings intact. If nothing is uploaded within 20 minutes, or an upload fails, the node restarts on the firmware it already had.
<div style="clear:both"></div>

== Boards ==

{| class="wikitable"
! Boards !! Node page and remote management !! Update without a cable
|-
| SenseCAP Solar Node P1 || Yes || Bluetooth window
|-
| Heltec V2, V3, V4, Wireless Tracker V2, XIAO ESP32S3, T-Beam Supreme, T-Deck || Yes || WiFi window
|-
| T-Beam, T3S3, LoRa32 v1, v2, v2.1, RNode NG 2.0, 2.1, Feather ESP32, generic ESP32 || Yes || No: one firmware slot, update over USB
|-
| RAK4631, RAK3401, T-Echo || Upstream microReticulum page || No
|}

== Getting it ==

* '''Flash it from a browser:''' [https://rnode.scotmesh.net rnode.scotmesh.net], choose ''Standalone node''. It fetches the firmware, flashes it, and walks you through naming the node, choosing its radio profile and adding yourself as its admin.
* '''Releases:''' [https://github.com/ScotMesh/microReticulum_Firmware/releases github.com/ScotMesh/microReticulum_Firmware/releases]
* '''Source and changes from upstream:''' [https://github.com/ScotMesh/microReticulum_Firmware github.com/ScotMesh/microReticulum_Firmware]

[[Category:Hardware]]

ScotMesh chat hub

2026-09-17T12:36:40Z

ScotMesh: Released 1.0.1; code is public at ScotMesh/scotmesh-chat

'''The ScotMesh chat hub''' runs ScotMesh's chat room: one conversation that people reach from an RRC chat client, as an LXMF group, or on a Nomad Network page, with everyone seeing the same messages under the same names. How to join is on [[The chat room]].

== What it is ==

One program that connects to [[The ScotMesh Backbone|the backbone]] over TCP, with no Reticulum daemon of its own, and serves three ways into the same room:

* '''The RRC room''' <code>#scotmesh</code>, for MeshChatX, NomadNet, rrc-tui and WeeChat.
* '''The LXMF group''', for Sideband, Columba, MeshChatX and NomadNet. Messages arrive as <code>Name: message</code>.
* '''The chat page''', read in NomadNet or MeshChatX, where you can post once you identify.

Each Reticulum identity holds one name everywhere, and lookalikes of a name that is taken are refused. When you come back you catch up on what you missed. LXMF delivery can be turned off or left automatic. Operators can moderate, and what they do is logged. Messages are kept for 7 days. The [[Propagation node|propagation node]] holds group messages for members who are away.

It replaced the earlier RRC hub and LXMF bridge.

== Status ==

'''Live''' on ScotMesh's own server. The latest release is [https://github.com/ScotMesh/scotmesh-chat/releases/tag/v1.0.1 v1.0.1] (15 September 2026).

== Where to find it ==

{| class="wikitable"
! Way in !! Address
|-
| RRC room || hub <code>004e5a15da221d9a236b0e8d74195f13</code>, room <code>scotmesh</code>
|-
| LXMF group || <code>625ad393ca4df62a1382f9d936322a0a</code>
|-
| Chat page || <code>c229a2c7d410e00b71f877375ae846bf:/page/index.mu</code>
|}

Commands are on [[Chat commands]]. The code is public at [https://github.com/ScotMesh/scotmesh-chat github.com/ScotMesh/scotmesh-chat], under the MIT licence.

== Who is working on it ==

Alex.

[[Category:Projects]]

RNode

2026-09-17T12:36:39Z

ScotMesh: Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

An '''RNode''' is a LoRa board running RNode firmware. It is not a Meshtastic or MeshCore radio, though much of the same hardware can be reflashed into one. It is the standard way to put Reticulum on the air.

== ScotMesh radio settings ==

Every radio on the network must use '''identical''' settings. This is not a tolerance thing: a board with a different spreading factor is completely deaf to the others, and nothing reports an error. If two of your radios cannot hear each other, check these before anything else.

{| class="wikitable"
|-
!
! ScotMesh 868
|-
| '''Frequency'''
| 869.4625 MHz
|-
| '''Bandwidth'''
| 125 kHz
|-
| '''Spreading factor'''
| 9
|-
| '''Coding rate'''
| 4/5
|-
| '''TX power'''
| 22 dBm
|}

'''ScotMesh 868 moved from 867.5 MHz to 869.4625 MHz on 11 September 2026''' to keep within Ofcom's rules. It now sits in the UK's 869.40–869.65 MHz sub-band, which allows up to 500 mW ERP with a 10% duty cycle; the old frequency's sub-band allows only 25 mW. A radio still on 867.5 MHz cannot hear the network, so retune it: the flasher's Configure step, the node's Radio page, or <code>rnodeconf -T</code> below.

As Reticulum config values, those are:

<syntaxhighlight lang="text"> # ScotMesh 868
[[ScotMesh RNode]]
type = RNodeInterface
enabled = yes
port = /dev/ttyUSB0
frequency = 869462500
bandwidth = 125000
txpower = 22
spreadingfactor = 9
codingrate = 5</syntaxhighlight>
== Flashing a board ==

The easiest way is [https://rnode.scotmesh.net rnode.scotmesh.net], the '''ScotMesh Flasher'''. It flashes the board from your browser over USB — nothing to install. Open it in Chrome or Edge on a desktop (Firefox and Safari do not implement WebSerial, and it will not work on a phone), plug the board in, and follow the steps:

# '''What are you building?''' — an ''RNode radio'' (for a computer or phone running Sideband, MeshChatX or NomadNet) or a ''standalone node'' (a self-contained microReticulum transport node — see below).
# '''Your hardware''' — pick the board and its band.
# '''Firmware''' — the latest release is fetched for you from the site's own mirror and its checksum verified.
# '''Connect''' and '''Flash''' — pick the port from the browser prompt; nRF52 boards are put into their bootloader automatically (press reset twice if that fails).
# '''Provision''' — the board's identity block and firmware hash are written and verified, the same as <code>rnodeconf --autoinstall</code>.
# '''Configure''' — for an RNode radio only Bluetooth; the radio profile is set by the app you connect it to, so the ScotMesh values are shown for you to enter there. For a standalone node: the ScotMesh 868 profile, a name, its role and the identities allowed to manage it.

If the board does not appear in the port list, hold its BOOT button while plugging it in, and check you are using a data USB cable rather than a charge-only one.

=== Standalone node (microReticulum) ===

The same boards can run [https://github.com/ScotMesh/microReticulum_Firmware microReticulum], the RNode firmware with a Reticulum transport stack built in. The board then ''is'' the node: it has its own identity, routes for others, serves a NomadNet page and can be managed over the mesh with <code>rnstatus -R</code> — no Raspberry Pi or computer attached. That is what ScotMesh uses for solar and hilltop relays; [[ScotMesh firmware]] explains what our build adds. Choose '''Standalone node''' in the flasher; the '''Seeed SenseCAP Solar Node P1''' (solar charger and battery built in) is the reference board and is built by ScotMesh — it does not exist in the upstream firmware. ''Reconfigure an existing node'' on the flasher's first screen connects over USB or Bluetooth to change settings later.

The command-line route does the same job and works on any platform:

<syntaxhighlight lang="text">pip install rns
rnodeconf --autoinstall
rnodeconf -T --freq 869462500 --bw 125000 --sf 9 --cr 5 --txp 22 /dev/ttyUSB0
rnodeconf -i /dev/ttyUSB0</syntaxhighlight>
<code>--autoinstall</code> is interactive: it detects the board, confirms the model with you, and installs the correct signed firmware. The second command writes the ScotMesh defaults into the device. The third prints them back so you can check.

== Supported boards ==

* Heltec LoRa32 v2, v3, v4
* Heltec Mesh Node T114
* LilyGO LoRa32 v1.0, v2.0, v2.1
* LilyGO LoRa32 T3S3
* LilyGO T-Beam, T-Beam Supreme
* LilyGO T-Deck
* LilyGO T-Echo
* RAK4631
* Seeed XIAO ESP32S3 with Wio-SX1262 (868 version)
* Homebrew RNode

'''Buy the board for the band you want.''' ScotMesh uses 868 MHz only, and many boards are also sold for other bands. A board built for another band cannot be moved to 868 MHz by changing settings — the radio and the antenna are physically different parts.

== Serial or Bluetooth ==

Over USB there is nothing to configure: the board appears as a serial port and Reticulum talks to it. That is the right choice for a node that stays in one place.

For a phone, or a board you would rather not tether, use the Bluetooth buttons on [https://rnode.scotmesh.net rnode.scotmesh.net], or from the command line:

<syntaxhighlight lang="text">rnodeconf -b /dev/ttyUSB0 # Bluetooth on
rnodeconf -p /dev/ttyUSB0 # pairing mode
rnodeconf -B /dev/ttyUSB0 # Bluetooth off</syntaxhighlight>
Not every supported board has Bluetooth. An Android phone with Sideband and an RNode paired over Bluetooth is a complete off-grid messenger with no phone network involved.

== Legal ==

Transmit power and transmit time are both regulated, and the limits differ by band and sub-band. The figures above are what ScotMesh uses; confirm what applies to your situation before transmitting.

If you are operating under an amateur licence, set <code>id_callsign</code> and <code>id_interval</code> on the interface so it identifies periodically. Set <code>airtime_limit_short</code> and <code>airtime_limit_long</code> to keep within duty-cycle limits — they are easy to exceed on a busy link.

[[Category:Hardware]]

Project index

2026-09-17T12:36:38Z

ScotMesh: Drop 433 MHz (scrapped); current firmware and chat hub versions; ScotMesh repo links

What ScotMesh is building on Reticulum, and where each piece has got to. Every project has a page with the same five things: what it is, its status, where to find it, who is working on it, and what comes next.

== Status words ==

{| class="wikitable"
! Status !! Meaning
|-
| '''Idea''' || Talked about; nothing written down beyond a page here.
|-
| '''Design''' || Specified in enough detail to build, no working code yet.
|-
| '''Prototype''' || Runs, for the people building it.
|-
| '''Live''' || In use on the network.
|-
| '''Paused''' || Not being worked on, but not abandoned.
|-
| '''Retired''' || Replaced or dropped; the page stays for the record.
|}

== Projects ==

{| class="wikitable"
! Project !! What it is !! Status !! Where
|-
| [[The ScotMesh node]] || The public transport node, chat hub, propagation node and Nomad Network node for Scotland || Live || [https://rns.scotmesh.net rns.scotmesh.net]
|-
| [[RNode|ScotMesh Flasher]] || Set up an RNode radio or a standalone node from a browser, with the ScotMesh radio profile built in || Live || [https://rnode.scotmesh.net rnode.scotmesh.net]
|-
| [[ScotMesh firmware]] || Our build of microReticulum for solar and hilltop relays: remote management from the node's own page, telemetry, updates without a cable, the SenseCAP Solar Node P1 || Live (v1.86-scotmesh.6) || [https://github.com/ScotMesh/microReticulum_Firmware GitHub]
|-
| LoRa gateways || ScotMesh radios on air, linking LoRa users to the backbone || Prototype: the first gateway is on air in Fife, on the ScotMesh 868 profile || [[RNode]]
|-
| [[Reticulum over MeshCore and Meshtastic]] || Carry Reticulum traffic over MeshCore and Meshtastic radios, so existing meshes become Reticulum bearers || Live: gateway at The Pole, Cadham || [https://github.com/ScotMesh/RNS_Over_Meshcore MeshCore], [https://github.com/ScotMesh/RNS_Over_Meshtastic Meshtastic]
|-
| [[ScotMesh chat hub]] || The chat room: one conversation reached over RRC, as an LXMF group or on a Nomad Network page, with one name per identity || Live (v1.0.1) || [[The chat room]]
|-
| [[ScotMesh Mail]] || Email over Reticulum: identity login, a MeshChatX plugin, Nomad Network webmail, a postmaster for Sideband, and <code>@mail.scotmesh.net</code> to the internet || Prototype || [[ScotMesh Mail#Where to find it|Addresses]]
|-
| This wiki || Documentation for all of the above || Live || You are reading it
|}

== Adding a project ==

Copy an existing project page, keep the five sections, and add a row here. A project with no page is not a project yet. Anything ScotMesh-built that lives in a repository should link to it, and say what licence it is under.

[[Category:Projects]]

Main Page

2026-09-17T12:36:37Z

ScotMesh: Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

{{DISPLAYTITLE:ScotMesh Reticulum Wiki}}
<div class="sm-otherwiki"><span class="sm-ow-logos"><span class="sm-ow-logo sm-ow-mt" title="Meshtastic"></span><span class="sm-ow-logo sm-ow-mc" title="MeshCore"></span></span><span class="sm-ow-text">Looking for <b>MeshCore</b> or <b>Meshtastic</b>? They have their own wiki at [https://wiki.scotmesh.uk wiki.scotmesh.uk] →</span></div>
<div class="sm-hero">
<div class="sm-hero-title">A free, encrypted network for Scotland that anyone can join.</div>
<div class="sm-hero-sub">Reticulum carries messages, chat, files and pages over the internet and over LoRa radio, and keeps working when the things underneath it do not. Connecting takes about five minutes.</div>
<div class="sm-hero-actions"><span class="sm-btn sm-btn-primary">[[Connecting to ScotMesh|Connect in five minutes →]]</span><span class="sm-btn sm-btn-secondary">[[What Reticulum is|What is Reticulum?]]</span></div>
<div class="sm-hero-facts"><span>No sign-up</span><span>No hardware needed</span><span>Free, run by the community</span><span>Encrypted end to end</span></div>
</div>

<div class="sm-welcome">
'''Welcome.''' ScotMesh runs the Reticulum backbone for Scotland and writes this wiki; you are very welcome to use both, and to add to either. Whether you have never heard of Reticulum or you want to put a solar relay on a hill, there is a page here for you. Pick where you are:
</div>

<div class="sm-cards">
<div class="sm-card">
=== I just want to try it ===
Install one app, type in one address, and you are on the network with everyone else: messaging, chat, files and pages.

'''[[Connecting to ScotMesh|Connect in five minutes →]]'''

Then [[First steps]]: say hello in the chat room and send your first message.
</div>
<div class="sm-card">
=== I want to understand it first ===
No addresses to configure, no accounts, no company in the middle. Reticulum is unusual, and it is worth knowing why.

'''[[What Reticulum is|What Reticulum is →]]'''

Then [[How Reticulum works]], [[How it compares]] with Meshtastic and MeshCore, and the [[Glossary]].
</div>
<div class="sm-card">
=== I want to put a radio on air ===
A LoRa board becomes a Reticulum radio for your laptop or phone, or a self-contained relay you can look after from home.

'''[[RNode|Flash a board →]]'''

Then [[ScotMesh firmware]] for solar and hilltop relays, and [[Antennas and siting]] for making it reach.
</div>
</div>

== The backbone right now ==

Live from the node itself, the same feed as [https://rns.scotmesh.net rns.scotmesh.net], refreshed every two minutes. If the strip is blank or says unknown, treat the backbone as unconfirmed and check the node page directly.

<div id="sm-status" class="sm-status">Live backbone status: [https://rns.scotmesh.net/status.html rns.scotmesh.net/status]</div>

== Connect now ==

The backbone is a public Reticulum transport node in Dalgety Bay, Fife. Anyone may connect, there is nothing to register, and it costs nothing.

'''Out of the box:''' install [https://meshchatx.com MeshChatX] (Windows, macOS, Linux, Android), [https://github.com/markqvist/Sideband/releases Sideband] (Android, Windows, macOS, Linux) or an iPhone app, add a connection of type '''TCPClientInterface''' with host <code>rns.scotmesh.net</code> and port <code>4242</code>, and you are on. [[Connecting to ScotMesh#Out of the box: an app|Step by step]].

'''Full installation:''' add this to your Reticulum config:

<syntaxhighlight lang="text"> [[ScotMesh Backbone]]
type = TCPClientInterface
enabled = yes
target_host = rns.scotmesh.net
target_port = 4242</syntaxhighlight>

'''Behind CGNAT or a firewall you do not control?''' Use the I2P entry point instead; no port needs forwarding at either end. See [[Access over I2P]].

'''Got a LoRa radio?''' ScotMesh's first gateway is on air in Fife, on the ScotMesh profile below and linked to the backbone, and standalone [[ScotMesh firmware|solar nodes]] are going out. Coverage is small so far, so a radio built anywhere in Scotland will hear the others as they arrive. Every radio must match all five settings exactly: a board with a different spreading factor is not weakly connected, it is completely deaf, and nothing reports an error. The 868 profile moved from 867.5 to 869.4625 MHz on 11 September 2026 (Ofcom's 869.40–869.65 MHz sub-band), so retune any radio still on the old frequency. [https://rnode.scotmesh.net rnode.scotmesh.net] applies the profile in one click.

{| class="wikitable"
|-
!
! ScotMesh 868
|-
| Frequency
| 869.4625 MHz
|-
| Bandwidth
| 125 kHz
|-
| Spreading factor
| 9
|-
| Coding rate
| 4/5
|-
| TX power
| 22 dBm
|}

Whichever way in you chose: restart Reticulum, then check the interface shows '''Up''' (in <code>rnstatus</code>, or on the app's interfaces page). If it does not, [[Troubleshooting]] 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]]; [[Services and addresses]] has them all in one place.

{| class="wikitable"
|-
! Service
! Address
! Use it with
|-
| TCP entry point
| <code>rns.scotmesh.net:4242</code>
| Any Reticulum client
|-
| I2P entry point
| <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code>
| Any Reticulum client, via i2pd
|-
| [[The chat room|Chat hub]] (RRC), room <code>scotmesh</code>
| <code>004e5a15da221d9a236b0e8d74195f13</code>
| MeshChatX, <code>rrc</code> clients
|-
| [[Propagation node|LXMF propagation node]]
| <code>c283b754e0acc11ce48d2f5e29167e0c</code>
| Sideband, MeshChatX, Nomad Network
|-
| [[Nomad Network|Nomad Network node]]
| <code>10a839df2c50635bcb0c8a299b9ca0f8</code>
| Nomad Network, MeshChatX
|-
| Transport instance
| <code>20b962cd814444f7812e409e7c47f319</code>
| Shows up in <code>rnpath</code> and node maps
|}

The node peers outward to <code>rebelnet.uk</code>, <code>rns.cybercore.uk</code> and <code>rmap.world</code>, so a client connected here can reach the rest of the public Reticulum network. See [[Who we peer with]].

== Where the network is ==

Where things actually are, rather than where we would like them to be. Updated by hand as things land.

{| class="wikitable"
|-
!
! Milestone
! Notes
|-
| ✔
| '''Reticulum backbone online'''
| Public transport node at <code>rns.scotmesh.net:4242</code>, peered into the wider network.
|-
| ✔
| '''Reachable over I2P'''
| No port forwarding needed at either end.
|-
| ✔
| '''Chat hub running'''
| RRC hub with the <code>scotmesh</code> room.
|-
| ✔
| '''Propagation node running'''
| Offline message delivery for the region.
|-
| ✔
| '''Web flasher for RNodes and nodes'''
| [https://rnode.scotmesh.net rnode.scotmesh.net], with the ScotMesh profile built in.
|-
| ✔
| '''LoRa gateway on air'''
| First gateway in Fife, at The Pole, Cadham, linked to the backbone. It also carries Reticulum over [[Reticulum over MeshCore and Meshtastic|MeshCore and Meshtastic]].
|-
| ✔
| '''Standalone solar nodes'''
| [[ScotMesh firmware]]: managed and updated over the mesh. First units on the bench and going out.
|-
| ✘
| '''Coverage beyond Fife'''
| Needs gateways and relays elsewhere. [[Running your own transport node|Put one up]] and tell us.
|}

== Find your way ==

{| class="wikitable"
|-
| '''I have never used Reticulum'''
| Read in order: [[What Reticulum is|what Reticulum is]] → [[How it compares|how it compares]] to Meshtastic, MeshCore and LoRaWAN → [[Connecting to ScotMesh|connecting to ScotMesh]] → [[Choosing a client|choosing a client]] → [[First steps|first steps]].
|-
| '''I am connected. What can I do?'''
| Join [[The chat room|the chat room]], send messages that arrive even when the other person is offline via the [[Propagation node|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; [[ScotMesh firmware]] for a solar relay you can look after from home; [[Antennas and siting|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|known bugs and workarounds]].
|-
| '''What is ScotMesh building?'''
| The [[Project index|project index]]: the [[ScotMesh firmware]], the flasher, and [[Reticulum over MeshCore and Meshtastic|Reticulum over MeshCore and Meshtastic]].
|-
| '''I want to read and watch more'''
| [[Learning resources]]: the manual, talks, the community wiki, and where people talk.
|-
| '''What does that word mean?'''
| The [[Glossary|glossary]].
|}

== Say hello ==

ScotMesh is a community, not a company. Most of us are on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord], the quickest place to ask anything, Reticulum or not, and there is also the [https://scotmesh.uk forum at scotmesh.uk]; [[The chat room|the chat room]] is where to find us on the network itself; and [[About ScotMesh]] says who we are and what we run. If a page here is wrong or unclear, say so, or fix it: [[ScotMesh Wiki:About|anyone can ask for an editing account]].

Glossary

2026-09-17T12:36:36Z

ScotMesh: rrc-hub retired: the chat room is run by the ScotMesh chat hub

The vocabulary of Reticulum and of this wiki, a sentence or two each. [[How Reticulum works]] puts most of these together into one explanation.

; Announce
: A small signed packet a [[#Destination|destination]] sends to make itself known: its address, public key and optionally a little data such as a node's name. [[#Transport node|Transport nodes]] pass announces on and remember where they came from, which is how [[#Path|paths]] are built.

; Address
: See [[#Destination hash|destination hash]].

; Bearer
: Anything that can carry Reticulum traffic: LoRa, Wi-Fi, the internet, I2P, a serial cable, packet radio. See [[What Reticulum is]].

; Destination
: Something that can be reached on the network: your messaging inbox, a Nomad Network node, a chat hub. Each belongs to an [[#Identity|identity]] and has its own address.

; Destination hash
: A destination's address: 16 bytes, written as 32 hexadecimal characters, such as <code>10a839df2c50635bcb0c8a299b9ca0f8</code>. It is derived from the identity's public key, so nobody else can claim it.

; Gateway mode
: An [[#Interface mode|interface mode]] for a node that connects clients to a wider network. It answers path requests on its clients' behalf.

; Identity
: A pair of cryptographic keys, one for encryption and one for signing, created by your own software. Nobody issues or registers them. Being ''identified'' to a node means proving you hold a particular identity.

; Interface
: A configuration block that connects Reticulum to a [[#Bearer|bearer]]: a TCP connection, an I2P tunnel, an [[#RNode|RNode]]. In the config file each one starts with its name in double brackets, such as <code><nowiki>[[ScotMesh Backbone]]</nowiki></code>.

; Interface mode
: How a node treats announces and path requests on an interface: full, gateway, access point, roaming or boundary.

; Link
: An encrypted, verified connection between two parties, set up with fresh keys each time (forward secrecy). Browsing pages and transferring files use links.

; LXMF
: The message format Reticulum applications use for messaging. Sideband, MeshChatX and Nomad Network all speak it, so their users can message each other.

; Micron
: The lightweight markup [[Nomad Network]] pages are written in.

; microReticulum
: An implementation of Reticulum that runs on small microcontroller boards rather than computers. The [[ScotMesh firmware]] is built on it.

; MTU
: The largest packet a network carries. Reticulum's is 500 bytes, which is why pages for LoRa are kept small.

; Nomad Network
: Pages, files and messaging that live entirely inside Reticulum, with no DNS or hosting. See [[Nomad Network]].

; Path
: What a node knows about reaching a destination: which neighbour to send to, and how many hops away it is.

; Propagation node
: A node that holds [[#LXMF|LXMF]] messages for people who are offline and delivers them when they reappear. It stores them encrypted and cannot read them. See [[Propagation node]].

; RNode
: A LoRa radio running the RNode firmware, used by a computer or phone as a Reticulum interface. See [[RNode]].

; RRC
: The chat protocol used by ScotMesh's chat room, run by the [[ScotMesh chat hub]]. See [[The chat room]].

; rnsd, rnstatus, rnpath, rnprobe
: The Reticulum daemon, and the utilities that show its interfaces, look up a path, and test whether a destination answers.

; Transport node
: A Reticulum node that forwards traffic for others, because its owner set <code>enable_transport = Yes</code>. It only ever handles encrypted packets.

[[Category:Getting Started]]

Antennas and siting

2026-09-17T12:36:35Z

ScotMesh: Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

The antenna and where you put it make more difference to range than the radio does. A good antenna on a roof with a poor board will outperform the best board on a desk with the stub antenna it came with, every time. This page is the practical version for ScotMesh's two bands.

== The antenna must match the band ==

An antenna is tuned for a frequency range. An antenna made for another band on an 868 MHz board reflects most of the transmitter's power back into it: range collapses, and at 22 dBm the radio can be damaged. Check the band printed on the antenna, and '''never transmit with no antenna connected'''.

Cheap boards often ship with a generic stub that is not tuned for 868 MHz at all. Replacing it is the single best upgrade.

{| class="wikitable"
! Type !! Gain !! Good for
|-
| Stub or “rubber duck” || 0 to 2 dBi || Handhelds and testing on a desk
|-
| Quarter-wave whip (about 8.2 cm at 868 MHz) || about 2 dBi || Cheap, easy, works well with a ground plane (a metal box lid or a few radials)
|-
| Half-wave dipole || about 2 dBi || Needs no ground plane; a good indoor or window antenna
|-
| Collinear or fibreglass omni || 3 to 6 dBi || The usual choice for a fixed node on a mast; flat coverage all round
|-
| Yagi or panel || 6 to 12 dBi || Point-to-point links to one distant node; narrow beam, must be aimed
|}

Gain is not free. A high-gain omni squashes its coverage into a flat disc: on a hilltop node it can fire over the heads of everyone in the glen below. For a node looking down on its users, 3 dBi or a slight downward tilt is often better than 6.

== Height and line of sight ==

At these frequencies range is mostly about what is in the way. LoRa will go many kilometres with a clear line of sight and struggle to cross a village with none.

* '''Height beats power.''' Doubling transmit power adds a few hundred metres in the open; getting the antenna above the rooftops multiplies range.
* '''Trees matter''' more than people expect, and wet trees more than dry ones. Coverage measured in August is not coverage in January.
* '''Hills are walls''', but they are also the best sites: a node on a hill sees everything on both sides of it.
* '''Indoors is lossy.''' A window facing the direction you care about is far better than the middle of the house. Foil-backed insulation and metal-framed windows block almost everything.

Free tools such as [https://www.heywhatsthat.com HeyWhatsThat] and radio coverage planners will draw the horizon from a point; use them before buying a mast.

== Cable and connectors ==

Coaxial cable loses signal, more at higher frequencies, and thin cable loses most. Ten metres of RG174 at 868 MHz throws away roughly half the power; ten metres of LMR-400 loses almost nothing. Keep the run short, use decent cable (LMR-240 or better for anything over a few metres), and put the radio near the antenna if you can: a [[ScotMesh firmware|standalone node]] in a box at the top of the pole with a short tail to the antenna beats a long feeder to a radio indoors.

Connectors: most boards have a u.FL or IPEX socket; most antennas have an SMA plug. Check whether you need SMA or '''RP-SMA''' (reverse polarity; common on Wi-Fi kit); they look alike and do not mate. Every adapter is a small loss and a place for water to get in.

== Weather ==

Scotland's weather gets into everything. Seal connectors with self-amalgamating tape, make sure cable enters a box from below with a drip loop, use a fibreglass antenna outdoors rather than a bare whip, and expect to check it after the first winter.

== Solar nodes ==

A relay that has to survive a Scottish winter on a panel needs more panel and battery than a summer test suggests: December gives perhaps a tenth of June's energy, and a fortnight of cloud is normal. Face the panel south and tilt it steeply (60° or more) for winter. The [[ScotMesh firmware]] can lower transmit power or switch the radio off below a battery level you choose, which turns a dead node into a quiet one that comes back with the sun.

== Two power notes ==

* The licence-free bands limit both transmit power and how much of the time you may transmit. The ScotMesh profile is within those limits; adding a high-gain antenna raises your effective radiated power, so do not pair the 22 dBm profile with a high-gain directional antenna without checking the rules for the band.
* Transmit power is the least effective knob. If a link is marginal, raise the antenna, shorten the cable or move the node before raising the power.

== Share what you find ==

Real results from real sites in Scotland are worth more than any of the above. When you measure a link, note the two sites, antennas, heights and the RSSI and SNR reported by <code>rnstatus</code> or the node's page, and put them on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord] or add them here.

[[Category:Hardware]]

About ScotMesh

2026-09-17T10:48:08Z

ScotMesh: Link to Reticulum over MeshCore and Meshtastic, which replaces MeshCore as a Reticulum Interface

'''ScotMesh''' is a community building open, resilient mesh networks across Scotland: radio networks that keep working when the internet or the mobile networks do not, run by the people who use them. This wiki covers ScotMesh's '''Reticulum''' network. The community itself lives on [https://scotmesh.uk scotmesh.uk].

== Where to find us ==

{| class="wikitable"
! Site !! What it is for
|-
| [https://discord.gg/ytxfyuDmSt ScotMesh Discord] || Where most of the community talks, day to day: questions, help, and what people are building.
|-
| [https://scotmesh.uk scotmesh.uk] || The main ScotMesh website and forum: news, the community, and getting started with any of our networks.
|-
| [https://scotmesh.net scotmesh.net] || An index of the tools and services we run.
|-
| [https://rns.scotmesh.net rns.scotmesh.net] || The Reticulum backbone node: how to connect, and its live status.
|-
| [https://rnode.scotmesh.net rnode.scotmesh.net] || The ScotMesh Flasher: set up an RNode radio or a standalone node from your browser.
|-
| wiki.scotmesh.net || This wiki.
|}

== Three kinds of mesh ==

People in ScotMesh run three kinds of network, and many of us run more than one.

* '''MeshCore''' and '''Meshtastic''' are LoRa mesh systems: small radios that pass text messages between each other with no infrastructure. ScotMesh runs tools for them on [https://scotmesh.net scotmesh.net], such as a live map, packet analysis, coverage mapping and alerts.
* '''Reticulum''' is a networking stack rather than a radio system: it joins LoRa, the internet, I2P and anything else that can carry data into one encrypted network. See [[What Reticulum is]] and [[How Reticulum works]].

They are complementary rather than rivals, and some of our [[Projects|projects]] join them together, for example [[Reticulum over MeshCore and Meshtastic|carrying Reticulum over MeshCore and Meshtastic]].

== What ScotMesh runs for Reticulum ==

* '''The backbone:''' a public Reticulum transport node that anyone can connect to, with no account or registration. It carries traffic, hosts a chat room, a Nomad Network node and a propagation node for offline messages. See [[The ScotMesh Backbone]].
* '''The flasher:''' turns supported LoRa boards into RNode radios or standalone nodes. See [[RNode]] and [[ScotMesh firmware]].
* '''The firmware:''' our build of microReticulum for remote, solar-powered relays, with remote management and updates without a cable. See [[ScotMesh firmware]].
* '''This wiki.'''

== Getting involved ==

* '''Get connected:''' [[Connecting to ScotMesh]] takes you from nothing to on the network in about five minutes, with no hardware.
* '''Put up a node:''' a relay on a hill, a roof or a windowsill is how the network grows; start with [[Running your own transport node]] or a [[ScotMesh firmware]] solar node.
* '''Say hello:''' on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord], where most of us are, on the [https://scotmesh.uk forum], or in [[The chat room]] on the network itself.

[[Category:Getting Started]]

Projects

2026-09-17T10:48:07Z

ScotMesh: Link to Reticulum over MeshCore and Meshtastic, which replaces MeshCore as a Reticulum Interface

What ScotMesh is building on Reticulum: what each project is, what state it is in, and where to find it.

* [[Project index]]
* [[Reticulum over MeshCore and Meshtastic]]
* [[ScotMesh chat hub]]
* [[ScotMesh Mail]]

[[Category:Books]]

Project index

2026-09-17T10:48:07Z

ScotMesh: Link to Reticulum over MeshCore and Meshtastic, which replaces MeshCore as a Reticulum Interface

What ScotMesh is building on Reticulum, and where each piece has got to. Every project has a page with the same five things: what it is, its status, where to find it, who is working on it, and what comes next.

== Status words ==

{| class="wikitable"
! Status !! Meaning
|-
| '''Idea''' || Talked about; nothing written down beyond a page here.
|-
| '''Design''' || Specified in enough detail to build, no working code yet.
|-
| '''Prototype''' || Runs, for the people building it.
|-
| '''Live''' || In use on the network.
|-
| '''Paused''' || Not being worked on, but not abandoned.
|-
| '''Retired''' || Replaced or dropped; the page stays for the record.
|}

== Projects ==

{| class="wikitable"
! Project !! What it is !! Status !! Where
|-
| [[The ScotMesh node]] || The public transport node, chat hub, propagation node and Nomad Network node for Scotland || Live || [https://rns.scotmesh.net rns.scotmesh.net]
|-
| [[RNode|ScotMesh Flasher]] || Set up an RNode radio or a standalone node from a browser, with the ScotMesh radio profiles built in || Live || [https://rnode.scotmesh.net rnode.scotmesh.net]
|-
| [[ScotMesh firmware]] || Our build of microReticulum for solar and hilltop relays: remote management from the node's own page, telemetry, updates without a cable, the SenseCAP Solar Node P1 || Live (v1.86-scotmesh.4) || [https://github.com/A13xB0/microReticulum_Firmware GitHub]
|-
| LoRa gateways || ScotMesh radios on air, linking LoRa users to the backbone || Prototype: the first gateway is on air in Fife, carrying both profiles || [[RNode]]
|-
| [[Reticulum over MeshCore and Meshtastic]] || Carry Reticulum traffic over MeshCore and Meshtastic radios, so existing meshes become Reticulum bearers || Live: gateway at The Pole, Cadham || [https://github.com/ScotMesh/RNS_Over_Meshcore MeshCore], [https://github.com/ScotMesh/RNS_Over_Meshtastic Meshtastic]
|-
| [[ScotMesh chat hub]] || The chat room: one conversation reached over RRC, as an LXMF group or on a Nomad Network page, with one name per identity || Live (1.0.0-rc.4) || [[The chat room]]
|-
| [[ScotMesh Mail]] || Email over Reticulum: identity login, a MeshChatX plugin, Nomad Network webmail, a postmaster for Sideband, and <code>@mail.scotmesh.net</code> to the internet || Prototype || [[ScotMesh Mail#Where to find it|Addresses]]
|-
| This wiki || Documentation for all of the above || Live || You are reading it
|}

== Adding a project ==

Copy an existing project page, keep the five sections, and add a row here. A project with no page is not a project yet. Anything ScotMesh-built that lives in a repository should link to it, and say what licence it is under.

[[Category:Projects]]

Main Page

2026-09-17T10:48:06Z

ScotMesh: Link to Reticulum over MeshCore and Meshtastic, which replaces MeshCore as a Reticulum Interface

{{DISPLAYTITLE:ScotMesh Reticulum Wiki}}
<div class="sm-otherwiki"><span class="sm-ow-logos"><span class="sm-ow-logo sm-ow-mt" title="Meshtastic"></span><span class="sm-ow-logo sm-ow-mc" title="MeshCore"></span></span><span class="sm-ow-text">Looking for <b>MeshCore</b> or <b>Meshtastic</b>? They have their own wiki at [https://wiki.scotmesh.uk wiki.scotmesh.uk] →</span></div>
<div class="sm-hero">
<div class="sm-hero-title">A free, encrypted network for Scotland that anyone can join.</div>
<div class="sm-hero-sub">Reticulum carries messages, chat, files and pages over the internet and over LoRa radio, and keeps working when the things underneath it do not. Connecting takes about five minutes.</div>
<div class="sm-hero-actions"><span class="sm-btn sm-btn-primary">[[Connecting to ScotMesh|Connect in five minutes →]]</span><span class="sm-btn sm-btn-secondary">[[What Reticulum is|What is Reticulum?]]</span></div>
<div class="sm-hero-facts"><span>No sign-up</span><span>No hardware needed</span><span>Free, run by the community</span><span>Encrypted end to end</span></div>
</div>

<div class="sm-welcome">
'''Welcome.''' ScotMesh runs the Reticulum backbone for Scotland and writes this wiki; you are very welcome to use both, and to add to either. Whether you have never heard of Reticulum or you want to put a solar relay on a hill, there is a page here for you. Pick where you are:
</div>

<div class="sm-cards">
<div class="sm-card">
=== I just want to try it ===
Install one app, type in one address, and you are on the network with everyone else: messaging, chat, files and pages.

'''[[Connecting to ScotMesh|Connect in five minutes →]]'''

Then [[First steps]]: say hello in the chat room and send your first message.
</div>
<div class="sm-card">
=== I want to understand it first ===
No addresses to configure, no accounts, no company in the middle. Reticulum is unusual, and it is worth knowing why.

'''[[What Reticulum is|What Reticulum is →]]'''

Then [[How Reticulum works]], [[How it compares]] with Meshtastic and MeshCore, and the [[Glossary]].
</div>
<div class="sm-card">
=== I want to put a radio on air ===
A LoRa board becomes a Reticulum radio for your laptop or phone, or a self-contained relay you can look after from home.

'''[[RNode|Flash a board →]]'''

Then [[ScotMesh firmware]] for solar and hilltop relays, and [[Antennas and siting]] for making it reach.
</div>
</div>

== The backbone right now ==

Live from the node itself, the same feed as [https://rns.scotmesh.net rns.scotmesh.net], refreshed every two minutes. If the strip is blank or says unknown, treat the backbone as unconfirmed and check the node page directly.

<div id="sm-status" class="sm-status">Live backbone status: [https://rns.scotmesh.net/status.html rns.scotmesh.net/status]</div>

== Connect now ==

The backbone is a public Reticulum transport node in Dalgety Bay, Fife. Anyone may connect, there is nothing to register, and it costs nothing.

'''Out of the box:''' install [https://meshchatx.com MeshChatX] (Windows, macOS, Linux, Android), [https://github.com/markqvist/Sideband/releases Sideband] (Android, Windows, macOS, Linux) or an iPhone app, add a connection of type '''TCPClientInterface''' with host <code>rns.scotmesh.net</code> and port <code>4242</code>, and you are on. [[Connecting to ScotMesh#Out of the box: an app|Step by step]].

'''Full installation:''' add this to your Reticulum config:

<syntaxhighlight lang="text"> [[ScotMesh Backbone]]
type = TCPClientInterface
enabled = yes
target_host = rns.scotmesh.net
target_port = 4242</syntaxhighlight>

'''Behind CGNAT or a firewall you do not control?''' Use the I2P entry point instead; no port needs forwarding at either end. See [[Access over I2P]].

'''Got a LoRa radio?''' ScotMesh's first gateway is on air in Fife, carrying both profiles below and linked to the backbone, and standalone [[ScotMesh firmware|solar nodes]] are going out. Coverage is small so far, so a radio built anywhere in Scotland will hear the others as they arrive. Every radio must match all five settings exactly: a board with a different spreading factor is not weakly connected, it is completely deaf, and nothing reports an error. The 868 profile moved from 867.5 to 869.4625 MHz on 11 September 2026 (Ofcom's 869.40–869.65 MHz sub-band), so retune any radio still on the old frequency. [https://rnode.scotmesh.net rnode.scotmesh.net] applies either profile in one click.

{| class="wikitable"
|-
!
! ScotMesh 433
! ScotMesh 868
|-
| Frequency
| 433.775 MHz
| 869.4625 MHz
|-
| Bandwidth
| 125 kHz
| 125 kHz
|-
| Spreading factor
| 8
| 9
|-
| Coding rate
| 4/5
| 4/5
|-
| TX power
| 7 dBm
| 22 dBm
|}

Whichever way in you chose: restart Reticulum, then check the interface shows '''Up''' (in <code>rnstatus</code>, or on the app's interfaces page). If it does not, [[Troubleshooting]] 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]]; [[Services and addresses]] has them all in one place.

{| class="wikitable"
|-
! Service
! Address
! Use it with
|-
| TCP entry point
| <code>rns.scotmesh.net:4242</code>
| Any Reticulum client
|-
| I2P entry point
| <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code>
| Any Reticulum client, via i2pd
|-
| [[The chat room|Chat hub]] (RRC), room <code>scotmesh</code>
| <code>004e5a15da221d9a236b0e8d74195f13</code>
| MeshChatX, <code>rrc</code> clients
|-
| [[Propagation node|LXMF propagation node]]
| <code>c283b754e0acc11ce48d2f5e29167e0c</code>
| Sideband, MeshChatX, Nomad Network
|-
| [[Nomad Network|Nomad Network node]]
| <code>10a839df2c50635bcb0c8a299b9ca0f8</code>
| Nomad Network, MeshChatX
|-
| Transport instance
| <code>20b962cd814444f7812e409e7c47f319</code>
| Shows up in <code>rnpath</code> and node maps
|}

The node peers outward to <code>rebelnet.uk</code>, <code>rns.cybercore.uk</code> and <code>rmap.world</code>, so a client connected here can reach the rest of the public Reticulum network. See [[Who we peer with]].

== Where the network is ==

Where things actually are, rather than where we would like them to be. Updated by hand as things land.

{| class="wikitable"
|-
!
! Milestone
! Notes
|-
| ✔
| '''Reticulum backbone online'''
| Public transport node at <code>rns.scotmesh.net:4242</code>, peered into the wider network.
|-
| ✔
| '''Reachable over I2P'''
| No port forwarding needed at either end.
|-
| ✔
| '''Chat hub running'''
| RRC hub with the <code>scotmesh</code> room.
|-
| ✔
| '''Propagation node running'''
| Offline message delivery for the region.
|-
| ✔
| '''Web flasher for RNodes and nodes'''
| [https://rnode.scotmesh.net rnode.scotmesh.net], with both ScotMesh profiles built in.
|-
| ✔
| '''LoRa gateway on air'''
| First gateway in Fife, both profiles, linked to the backbone.
|-
| ✔
| '''Standalone solar nodes'''
| [[ScotMesh firmware]]: managed and updated over the mesh. First units on the bench and going out.
|-
| ✘
| '''Coverage beyond Fife'''
| Needs gateways and relays elsewhere. [[Running your own transport node|Put one up]] and tell us.
|}

== Find your way ==

{| class="wikitable"
|-
| '''I have never used Reticulum'''
| Read in order: [[What Reticulum is|what Reticulum is]] → [[How it compares|how it compares]] to Meshtastic, MeshCore and LoRaWAN → [[Connecting to ScotMesh|connecting to ScotMesh]] → [[Choosing a client|choosing a client]] → [[First steps|first steps]].
|-
| '''I am connected. What can I do?'''
| Join [[The chat room|the chat room]], send messages that arrive even when the other person is offline via the [[Propagation node|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; [[ScotMesh firmware]] for a solar relay you can look after from home; [[Antennas and siting|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|known bugs and workarounds]].
|-
| '''What is ScotMesh building?'''
| The [[Project index|project index]]: the [[ScotMesh firmware]], the flasher, and [[Reticulum over MeshCore and Meshtastic|Reticulum over MeshCore and Meshtastic]].
|-
| '''I want to read and watch more'''
| [[Learning resources]]: the manual, talks, the community wiki, and where people talk.
|-
| '''What does that word mean?'''
| The [[Glossary|glossary]].
|}

== Say hello ==

ScotMesh is a community, not a company. Most of us are on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord], the quickest place to ask anything, Reticulum or not, and there is also the [https://scotmesh.uk forum at scotmesh.uk]; [[The chat room|the chat room]] is where to find us on the network itself; and [[About ScotMesh]] says who we are and what we run. If a page here is wrong or unclear, say so, or fix it: [[ScotMesh Wiki:About|anyone can ask for an editing account]].

Reticulum over MeshCore and Meshtastic

2026-09-17T10:48:04Z

ScotMesh: New page: reaching Reticulum through a MeshCore or Meshtastic radio via the gateway at The Pole

This page is for people who already have a '''MeshCore''' or '''Meshtastic''' radio and want to use it to reach Reticulum, with no internet connection and no [[RNode]]. If you have never heard of Reticulum, start with [[What Reticulum is|what Reticulum is]] and come back.

== What you are actually doing ==

Reticulum runs on your computer as usual. Normally it reaches the network over the internet ([[Connecting to ScotMesh]]) or over an [[RNode]]. Here it uses '''your MeshCore or Meshtastic radio''' as its link instead.

Reticulum's traffic is cut into small pieces and sent on a separate, private channel on your radio. A ScotMesh gateway on the same channel puts the pieces back together and passes them on to [[The ScotMesh Backbone|the backbone]]. That gateway is at '''The Pole''' in Cadham, and it is listed on node maps as ''ScotMesh RNode Cadham''.

Your radio keeps working for its own network at the same time. MeshCore or Meshtastic users around you never see the tunnel, because it runs on its own channel with its own key.

== Is this for you? ==

{| class="wikitable"
! If you have… !! Use
|-
| An internet connection, even a slow one || [[Connecting to ScotMesh]]. It is faster and costs no airtime.
|-
| An RNode, or a board you could flash as one || [[RNode]]. Reticulum runs natively on it and is many times faster.
|-
| Only a MeshCore or Meshtastic radio, within reach of the gateway || '''This page.'''
|}

Expect it to be '''slow'''. It is fine for messages (LXMF), the [[The chat room|chat room]] and small [[Nomad Network]] pages. It is no good for files or voice.

== The two routes ==

{| class="wikitable"
! !! Over MeshCore !! Over Meshtastic
|-
| '''Status''' || '''Working''' — gateway live at The Pole || '''Working''' — gateway live at The Pole since 17 September 2026. New, so tell us how it goes.
|-
| '''Your radio''' || MeshCore '''companion''' firmware v1.17 or later, over USB, Bluetooth or WiFi || Any Meshtastic node, over USB, Bluetooth or WiFi
|-
| '''Radio settings''' || UK/EU Narrow: 869.618 MHz, 62.5 kHz, SF8, CR 4/8 || EU_868, LongFast
|-
| '''Region''' || <code>sco</code> || —
|-
| '''Software''' || <code>MeshCore_Raw_Interface.py</code> from [https://github.com/ScotMesh/RNS_Over_Meshcore ScotMesh/RNS_Over_Meshcore] || <code>Meshtastic_Interface.py</code> from [https://github.com/ScotMesh/RNS_Over_Meshtastic ScotMesh/RNS_Over_Meshtastic]
|-
| '''Speed''' || At best a few hundred bytes a second || Slower: one piece of up to 155 bytes every 8 seconds on LongFast
|}

== Before you start ==

* '''Reticulum installed''' on a computer ([[Installing Reticulum]]), or '''MeshChatX''' ([[Choosing a client]]).
* '''Your radio''', connected to that computer.
* '''A path to the gateway''': in range of The Pole, or reaching it through MeshCore repeaters that relay the <code>sco</code> region.
* '''The tunnel channel details''', in the table below.

== Tunnel details ==

These are shared on purpose, so anyone can join the tunnel. The channel key only keeps the tunnel's traffic separate from ordinary channels; it is not what keeps you private. Reticulum encrypts everything you send end to end, whatever it travels over.

{| class="wikitable"
! !! MeshCore !! Meshtastic
|-
| '''Channel name''' || <code>RNSTunnel</code> || <code>RNS</code>
|-
| '''Secret''' || <code>38a46b4349a14b05c70328f444932033</code> || in the link below
|-
| '''Add it with''' || Reticulum sets it on your radio for you (step 3) || [https://meshtastic.org/e/?add=true#CicSIKzMw9L_sPDY_S2bF9AB3mRvgeyDwAhw9K6HLEBEzbc9GgNSTlMSCAgBOANAA0gB this channel link] — opens in the Meshtastic app and adds the channel next to your own
|-
| '''Region''' || <code>sco</code> || —
|}

-----

== Over MeshCore ==

[[File:Reticulum over MeshCore.svg|center|frameless|upright=3.2|alt=Diagram: Reticulum on your computer talks to your MeshCore companion radio over USB, Bluetooth or WiFi. The radio carries the tunnel on the RNSTunnel channel, directly or through MeshCore repeaters in region sco, to The Pole at Cadham, where the openHop repeater hands it to the RNSBridge companion and rnsd, which connects to the ScotMesh backbone over TCP. Broadcasts go as flooded channel datagrams of up to 148 bytes; traffic to a known peer goes as raw packets of up to 140 bytes along the repeater path.|How Reticulum travels over MeshCore to the ScotMesh backbone]]

=== 1. Set up the radio ===

# Flash '''companion''' firmware, v1.17 or later. Earlier versions lack the two commands the tunnel uses. Repeater or room server firmware will not work.
# Set the radio to '''UK/EU Narrow''': 869.618 MHz, 62.5 kHz, SF8, coding rate 4/8.
# '''Pick a spare channel slot''' for the tunnel, such as 7. Reticulum writes its channel into that slot when it connects, so '''do not use 0''': on most radios that is your Public channel, and it would be replaced.

A companion radio talks to one app at a time. While Reticulum is using it, your phone's MeshCore app cannot connect, and the other way round.

=== 2. Get the interface ===

Download <code>Interface/MeshCore_Raw_Interface.py</code> from [https://github.com/ScotMesh/RNS_Over_Meshcore ScotMesh/RNS_Over_Meshcore] and put it in Reticulum's <code>interfaces</code> folder:

{| class="wikitable"
! System !! Folder
|-
| Linux, macOS || <code>~/.reticulum/interfaces/</code>
|-
| Windows || <code>C:\Users\<you>\.reticulum\interfaces\</code>
|}

Create the folder if it is not there. The interface needs nothing beyond Reticulum itself, plus one library for your connection:

<syntaxhighlight lang="text">pip install pyserial # USB
pip install bleak # Bluetooth</syntaxhighlight>
Use <code>~/reticulum/bin/pip</code> instead if you installed Reticulum in a virtual environment. WiFi (TCP) needs nothing extra.

=== 3. Add it to your config ===

Add this block under <code>[interfaces]</code> in your Reticulum config file (where to find it: [[Connecting to ScotMesh#3. Find the config file|Connecting to ScotMesh]]). Keep exactly one of the three connection blocks.

<syntaxhighlight lang="ini"> [[ScotMesh over MeshCore]]
type = MeshCore_Raw_Interface
interface_enabled = yes

# USB
transport = serial
port = /dev/ttyUSB0 # Windows: COM3 or similar
baudrate = 115200

# Bluetooth - instead of the USB lines
# transport = ble
# ble_name = MeshCore # part of the radio's Bluetooth name

# WiFi - instead of the USB lines
# transport = tcp
# host = 192.168.1.50 # the radio's address
# tcp_port = 5000

# The ScotMesh tunnel
channel_idx = 7 # a spare slot, never 0
channel_name = RNSTunnel
channel_secret = 38a46b4349a14b05c70328f444932033
flood_scope = sco

# You are an end user, not a relay
can_route = no</syntaxhighlight>
Leave <code>mode</code> out: the default is right for an end user.

=== 4. Start it and check ===

# Start Reticulum: <code>rnsd</code>, or restart it if it was already running.
# Run <code>rnstatus</code>. '''ScotMesh over MeshCore''' should be listed as '''Up'''.
# Look for the ScotMesh node. The first answer can take a minute or two over radio.

<syntaxhighlight lang="text">rnpath 10a839df2c50635bcb0c8a299b9ca0f8</syntaxhighlight>
A reply such as ''Path found … via … on MeshCore_Raw_Interface'' means you are through. From here everything in [[Services and addresses]] works, just slowly.

=== With MeshChatX instead ===

# Open '''Settings''', then '''Interfaces''', and install a custom interface module. Upload <code>MeshCore_Raw_Interface.py</code>.
# Add an interface of type <code>MeshCore_Raw_Interface</code> with the same settings as the block above.
# Restart when asked.

MeshChatX already includes the USB and Bluetooth libraries.

On an '''Android phone''', Sideband can only use the WiFi (TCP) connection. See the fork's README for its service plugin.

-----

== Over Meshtastic ==

[[File:Reticulum over Meshtastic.svg|center|frameless|upright=3.2|alt=Diagram: Reticulum on your computer talks to your Meshtastic node over USB, Bluetooth or WiFi. The node carries the tunnel on its RNS channel, on EU_868 LongFast, directly or through other Meshtastic nodes, to The Pole at Cadham, where RepeaterTastic's radio hands it to the hosted node RSN Bridge and rnsd, which connects to the ScotMesh backbone over TCP. Each Reticulum packet is cut into pieces of up to 155 bytes, sent one every 8 seconds, and missing pieces are asked for again.|How Reticulum travels over Meshtastic to the ScotMesh backbone]]

=== 1. Set up the radio ===

# Any Meshtastic node on '''EU_868''' with the '''LongFast''' preset, which is the default in the UK.
# Open the [https://meshtastic.org/e/?add=true#CicSIKzMw9L_sPDY_S2bF9AB3mRvgeyDwAhw9K6HLEBEzbc9GgNSTlMSCAgBOANAA0gB channel link] on the phone or computer your node is paired with. It adds a channel called <code>RNS</code> next to your own.
# In the Meshtastic app's channel list, '''note which slot <code>RNS</code> landed in'''. It is usually 1, the first slot after your primary channel.

Your normal channels keep working. The node can stay paired with your phone while Reticulum uses it over USB or WiFi.

=== 2. Get the Meshtastic interface ===

Download <code>Interface/Meshtastic_Interface.py</code> from [https://github.com/ScotMesh/RNS_Over_Meshtastic ScotMesh/RNS_Over_Meshtastic] into Reticulum's <code>interfaces</code> folder (the same folder as for [[#2. Get the interface|MeshCore]]). It needs the Meshtastic library:

<syntaxhighlight lang="text">pip install meshtastic</syntaxhighlight>
'''Use ScotMesh's copy, not the original.''' The original can only use your primary channel, and it sends pieces too big for the gateway.

=== 3. Add the Meshtastic block to your config ===

Keep exactly one of the three connection lines.

<syntaxhighlight lang="ini"> [[ScotMesh over Meshtastic]]
type = Meshtastic_Interface
enabled = yes

port = /dev/ttyUSB0 # USB (Windows: COM3 or similar)
# tcp_port = 192.168.1.60 # WiFi: the node's address
# ble_port = Meshtastic_1234 # Bluetooth: the node's name

data_speed = 0 # LongFast
channel_index = 1 # the slot RNS landed in
hop_limit = 3</syntaxhighlight>
Leave <code>mode</code> out, as for MeshCore.

=== 4. Start it and check it ===

As for MeshCore:
# Start <code>rnsd</code>.
# Check that '''ScotMesh over Meshtastic''' is '''Up''' in <code>rnstatus</code>.
# Run <code>rnpath 10a839df2c50635bcb0c8a299b9ca0f8</code>.

Allow a few minutes: Meshtastic sends only one piece every 8 seconds.

-----

== Keeping the air clear ==

The UK band these radios use allows each transmitter only '''10% of the time''', and everyone shares it.
* '''Do not set <code>mode = gateway</code>''' on your end. A gateway pushes every route it knows onto the radio and can flood the channel.
* '''Do not turn on <code>enable_transport</code>''' just for this. Your machine does not need to relay for others.
* '''Send messages, not files.''' A single photo can hold the channel for many minutes.
* '''Keep <code>can_route = no</code>''' unless ScotMesh has asked you to run a relay.

== If it does not work ==

{| class="wikitable"
! What you see !! Try
|-
| The interface is not listed in <code>rnstatus</code> || The file is not in the <code>interfaces</code> folder, or <code>type</code> is misspelt. Check the Reticulum log.
|-
| Listed, but '''Down''' || Wrong port or address, or another app (your phone) is connected to the radio.
|-
| ''unsupported command'' in the log || The radio's firmware is older than v1.17. Update the companion firmware.
|-
| Up, but <code>rnpath</code> never finds anything || Wrong channel secret, wrong radio settings, or no path to The Pole. Check the secret against [[#Tunnel details|Tunnel details]] first, then the radio settings, then ask in [[The chat room|the chat room]] whether anyone can hear you.
|-
| Your Public channel disappeared || <code>channel_idx</code> was 0. Pick a spare slot, then add the Public channel back in the MeshCore app.
|-
| Meshtastic: Up, but nothing arrives || <code>channel_index</code> doesn't match the slot the <code>RNS</code> channel is in, or the node isn't on EU_868 LongFast.
|}

== See also ==

* [https://github.com/ScotMesh/RNS_Over_Meshcore ScotMesh/RNS_Over_Meshcore] and [https://github.com/ScotMesh/RNS_Over_Meshtastic ScotMesh/RNS_Over_Meshtastic] — the interfaces' code
* [[RNode]] — the faster radio route
* [[Services and addresses]]

[[Category:Getting Started]]

File:Reticulum over MeshCore.svg

2026-09-17T10:48:03Z

ScotMesh: == Summary == Diagram for Reticulum over MeshCore and Meshtastic

== Summary ==
Diagram for Reticulum over MeshCore and Meshtastic

File:Reticulum over Meshtastic.svg

2026-09-17T10:48:03Z

ScotMesh: == Summary == Diagram for Reticulum over MeshCore and Meshtastic

== Summary ==
Diagram for Reticulum over MeshCore and Meshtastic

Projects

2026-09-13T11:17:34Z

ScotMesh: Add the chat hub and ScotMesh Mail

What ScotMesh is building on Reticulum: what each project is, what state it is in, and where to find it.

* [[Project index]]
* [[MeshCore as a Reticulum Interface]]
* [[ScotMesh chat hub]]
* [[ScotMesh Mail]]

[[Category:Books]]

Project index

2026-09-13T11:17:33Z

ScotMesh: Add the chat hub and ScotMesh Mail

What ScotMesh is building on Reticulum, and where each piece has got to. Every project has a page with the same five things: what it is, its status, where to find it, who is working on it, and what comes next.

== Status words ==

{| class="wikitable"
! Status !! Meaning
|-
| '''Idea''' || Talked about; nothing written down beyond a page here.
|-
| '''Design''' || Specified in enough detail to build, no working code yet.
|-
| '''Prototype''' || Runs, for the people building it.
|-
| '''Live''' || In use on the network.
|-
| '''Paused''' || Not being worked on, but not abandoned.
|-
| '''Retired''' || Replaced or dropped; the page stays for the record.
|}

== Projects ==

{| class="wikitable"
! Project !! What it is !! Status !! Where
|-
| [[The ScotMesh node]] || The public transport node, chat hub, propagation node and Nomad Network node for Scotland || Live || [https://rns.scotmesh.net rns.scotmesh.net]
|-
| [[RNode|ScotMesh Flasher]] || Set up an RNode radio or a standalone node from a browser, with the ScotMesh radio profiles built in || Live || [https://rnode.scotmesh.net rnode.scotmesh.net]
|-
| [[ScotMesh firmware]] || Our build of microReticulum for solar and hilltop relays: remote management from the node's own page, telemetry, updates without a cable, the SenseCAP Solar Node P1 || Live (v1.86-scotmesh.4) || [https://github.com/A13xB0/microReticulum_Firmware GitHub]
|-
| LoRa gateways || ScotMesh radios on air, linking LoRa users to the backbone || Prototype: the first gateway is on air in Fife, carrying both profiles || [[RNode]]
|-
| [[MeshCore as a Reticulum Interface]] || Carry Reticulum traffic over MeshCore radios, so an existing MeshCore mesh becomes a Reticulum bearer || Idea || [[MeshCore as a Reticulum Interface]]
|-
| [[ScotMesh chat hub]] || The chat room: one conversation reached over RRC, as an LXMF group or on a Nomad Network page, with one name per identity || Live (1.0.0-rc.4) || [[The chat room]]
|-
| [[ScotMesh Mail]] || Email over Reticulum: identity login, a MeshChatX plugin, Nomad Network webmail, a postmaster for Sideband, and <code>@mail.scotmesh.net</code> to the internet || Prototype || [[ScotMesh Mail#Where to find it|Addresses]]
|-
| This wiki || Documentation for all of the above || Live || You are reading it
|}

== Adding a project ==

Copy an existing project page, keep the five sections, and add a row here. A project with no page is not a project yet. Anything ScotMesh-built that lives in a repository should link to it, and say what licence it is under.

[[Category:Projects]]

ScotMesh chat hub

2026-09-13T11:17:31Z

ScotMesh: New project page: the ScotMesh chat hub

'''The ScotMesh chat hub''' runs ScotMesh's chat room: one conversation that people reach from an RRC chat client, as an LXMF group, or on a Nomad Network page, with everyone seeing the same messages under the same names. How to join is on [[The chat room]].

== What it is ==

One program that connects to [[The ScotMesh Backbone|the backbone]] over TCP, with no Reticulum daemon of its own, and serves three ways into the same room:

* '''The RRC room''' <code>#scotmesh</code>, for MeshChatX, NomadNet, rrc-tui and WeeChat.
* '''The LXMF group''', for Sideband, Columba, MeshChatX and NomadNet. Messages arrive as <code>Name: message</code>.
* '''The chat page''', read in NomadNet or MeshChatX, where you can post once you identify.

Each Reticulum identity holds one name everywhere, and lookalikes of a name that is taken are refused. When you come back you catch up on what you missed. LXMF delivery can be turned off or left automatic. Operators can moderate, and what they do is logged. Messages are kept for 7 days. The [[Propagation node|propagation node]] holds group messages for members who are away.

It replaced the earlier RRC hub and LXMF bridge.

== Status ==

'''Live''', version 1.0.0-rc.4 as of 13 September 2026, running on ScotMesh's own server.

== Where to find it ==

{| class="wikitable"
! Way in !! Address
|-
| RRC room || hub <code>004e5a15da221d9a236b0e8d74195f13</code>, room <code>scotmesh</code>
|-
| LXMF group || <code>625ad393ca4df62a1382f9d936322a0a</code>
|-
| Chat page || <code>c229a2c7d410e00b71f877375ae846bf:/page/index.mu</code>
|}

Commands are on [[Chat commands]]. The code is in a private repository, [https://github.com/A13xB0/scotmesh-chat A13xB0/scotmesh-chat], under the MIT licence.

== Who is working on it ==

Alex.

== Next ==

* Release 1.0.0 once the release candidate has settled on the network.

[[Category:Projects]]

ScotMesh Mail

2026-09-13T11:17:30Z

ScotMesh: New project page: ScotMesh Mail (rmail)

'''ScotMesh Mail''' is email over Reticulum. Your Reticulum identity is your login, so there are no passwords. Mail between people on the mesh never touches the internet, and a gateway links <code>@mail.scotmesh.net</code> to ordinary email.

== What it is ==

A mail server, '''rmail''', and the ways to use it:

* '''MeshChatX''': a plugin with folders, writing and replying, encrypted and signed mail, and your mail key.
* '''Nomad Network''': the server is also a node with webmail pages, readable in NomadNet or MeshChatX's page browser.
* '''Sideband''' and any other LXMF app: message the server's '''postmaster'''. It sends a notice when mail arrives, can forward whole messages, and takes commands such as <code>STATUS</code>, <code>INBOX</code>, <code>READ</code> and <code>REPLY</code>. Start a message with <code>to: someone@…</code> to send mail.

Several identities can share one mailbox, for example your phone and your laptop, or a group's shared address. Mail can be kept encrypted on the server with keys only the mailbox's members hold. Mail is text only and kept small, because it crosses radio links: attachments are refused.

Servers announce themselves like Nomad Network nodes, and anyone can run one. Addresses look like <code>name@<server address>.rns</code> on the mesh, and <code>name@mail.scotmesh.net</code> from the internet.

== Status ==

'''Prototype''', as of 13 September 2026. The ScotMesh server is running and joined to [[The ScotMesh Backbone|the backbone]], with the first mailbox. Sign-up is by invitation only. Mail from the internet is waiting on its firewall port being opened, and mail to the internet may land in spam folders for now, because the server's address can't be given a matching reverse DNS name.

== Where to find it ==

{| class="wikitable"
! What !! Address
|-
| Mail server || <code>45b45ffb1ce546993728cb31e9846b95</code>
|-
| Postmaster (LXMF) || <code>044b450f5f66efc790c25d703121d4a5</code>
|-
| Webmail (Nomad Network) || <code>65f06cd68ddedd8929471af0d82c1a7d:/page/index.mu</code>
|-
| Internet domain || <code>mail.scotmesh.net</code>
|}

It runs on ScotMesh's own server alongside the [[ScotMesh chat hub|chat hub]], and stores messages for mailboxes that are away through the [[Propagation node|propagation node]]. The code is in a private repository, [https://github.com/A13xB0/rmail A13xB0/rmail]; it has no licence yet.

== Who is working on it ==

Alex.

== Next ==

* Open the mail port so internet mail can arrive, and send a first message each way.
* Try the MeshChatX plugin with real users, and write a how-to page like [[The chat room]].
* Choose a licence and publish the code.
* Send out the first invitations.

[[Category:Projects]]

The chat room

2026-09-13T00:40:59Z

ScotMesh: Step-by-step joining from MeshChatX for the room, the group and the page

ScotMesh has one chat, the room '''<code>scotmesh</code>''', with three ways into it. Use whichever suits you: everyone sees the same messages, under the same names, whichever way they came in. It is the place to say hello, ask for help, and find out who else is on.

<pre>
MeshChatX, NomadNet, rrc-tui ──── RRC room #scotmesh ────┐
│
Sideband, Columba, MeshChatX ──── LXMF group ────────────┼──► ScotMesh chat hub ──► one conversation
│ (names, history, everyone sees
NomadNet, MeshChatX ───────────── chat page ─────────────┘ settings, 7 days) every message
</pre>

{| class="wikitable"
! Way in !! Address
|-
| RRC room || hub <code>004e5a15da221d9a236b0e8d74195f13</code>, room <code>scotmesh</code>
|-
| LXMF group || <code>625ad393ca4df62a1382f9d936322a0a</code>
|-
| Chat page || <code>c229a2c7d410e00b71f877375ae846bf:/page/index.mu</code>
|}

Every command is listed on [[Chat commands]].

== How it fits together ==

[[File:ScotMesh chat hub architecture.svg|center|frameless|upright=3.2|alt=Diagram: RRC clients, LXMF messengers and NomadNet browsers each reach their own front door in the ScotMesh chat hub. Each door checks the Reticulum identity and its name, then passes messages to the hub core, which works with names, moderation and the store. The hub connects to the Reticulum backbone, and the propagation node holds group messages for members who are away.|How the ScotMesh chat hub fits together]]

The hub is one program on ScotMesh's own server, connected to the backbone at rns.scotmesh.net.

* '''Three front doors.''' The RRC server, the LXMF group and the chat page each speak their own protocol, so every app works with the door it already knows.
* '''Identity first.''' Before a message goes any further, its door checks the Reticulum identity it came from and looks up the name that identity holds. That is why a name is the same everywhere and can't be borrowed, and why messages appear under the author's own name.
* '''One hub core''' puts messages in order, stores them once and sends them out through every door. It also handles catching up, who is here, LXMF settings and commands.
* '''Beside it''' are the names (one per identity, lookalikes refused), moderation (operators, bans and a log of what operators do) and the store, where messages are kept for 7 days.
* '''The propagation node''' holds group messages for LXMF members who are offline until they collect them.

== What it looks like ==

Here is the same conversation seen three ways in MeshChatX. The messages Alex sent from LXMF, RRC and the chat page all turn up in each view, under the same name.

; The RRC room
: The live chat, with who is here, joins and leaves, and room notices. Use it when you want to talk in real time.
[[File:ScotMesh chat RRC room in MeshChatX.png|center|frameless|upright=3.2|alt=MeshChatX showing the scotmesh RRC room: Alex's test messages sent from LXMF, RRC and Nomad, followed by join notices and the room topic.|The #scotmesh RRC room in MeshChatX]]

; The LXMF group
: The chat arrives as ordinary messages from ''ScotMesh Chat'', each one written as <code>Name: message</code>. What you send goes to everyone. It keeps working when you are offline, because missed messages wait on the propagation node.
[[File:ScotMesh chat LXMF group in MeshChatX.png|center|frameless|upright=3.2|alt=MeshChatX conversation with ScotMesh Chat: a message sent to the group, and a reply shown as "Alex: test new setting".|The LXMF group as a MeshChatX conversation]]

; The chat page
: A NomadNet page showing who you are, the recent messages, a box to post, and links to older messages and to your name and settings. When there's something you haven't seen yet, a line marks where it starts.
[[File:ScotMesh chat page in MeshChatX.png|center|frameless|upright=3.2|alt=The ScotMesh chat page open in MeshChatX's NomadNet browser, with the saltire banner, recent messages and a box to post.|The chat page in MeshChatX's page browser]]

== Out of the box ==

Once you are [[Connecting to ScotMesh|connected to ScotMesh]]:

; MeshChatX
: All three ways in work from MeshChatX, and it uses one identity for all of them, so your name is the same in each. See [[#Step by step in MeshChatX|step by step in MeshChatX]] below.
; Sideband, and Columba or Retichat on iPhone
: Start a conversation with <code>625ad393ca4df62a1382f9d936322a0a</code> and send <code>/join</code>. The chat then arrives like any other conversation, as <code>Name: message</code>, and what you send reaches everyone.
; NomadNet
: Open the chat page above to read along. To post, turn on "Identify when connecting" for that node and reload. NomadNet can also join the RRC room from its Channels screen.

== Step by step in MeshChatX ==

These steps match MeshChatX 4.8. Labels in '''bold''' are what the app shows.

=== Before you start: your name ===

The hub names you after the display name your app announces, so set that first.

# Click your account at the bottom of the left sidebar. Until you set a name it says '''My Identity'''.
# Type your name in '''Display Name''' and press Enter. It's also in '''Settings''' under '''Profile'''.
# Click '''Announce Now''' (the radio icon next to it) so the network hears the new name.

Names have no spaces on the hub, so <code>Ellen Smith</code> becomes <code>Ellen_Smith</code>. You can pick a different name later with <code>/nick YourName</code>.

=== The RRC room (live chat) ===

# In the left sidebar, under '''Communicate''', click '''Relay Chat'''. If you can't see it, turn on '''Relay Chat''' in '''Settings''' → '''General'''.
# On the '''Connect''' tab, click '''+ Add a hub'''.
# In '''Add a Relay Chat Hub''', paste <code>004e5a15da221d9a236b0e8d74195f13</code> into '''Hub Destination Hash'''. Type <code>ScotMesh</code> in '''Hub Name (optional)''' and click '''Add Hub'''. MeshChatX connects straight away.
#: ''Or'' open the '''Discover''' tab: the ScotMesh hub is listed once its announce has reached you, with an '''Add''' button.
# Under the hub, type <code>scotmesh</code> in the '''room name''' box and click '''+''' ('''Join Room'''). You can also open '''Available Rooms''' and click '''Join'''.
# Type in '''Write a message...''' and click '''Send'''.

* '''Show members''' in the room header lists who is here.
* Commands such as <code>/help</code> and <code>/whoami</code> go in the same message box. The answers appear in the room, visible only to you.
* The hub card's cog ('''Hub Settings''') has '''Nickname override''', if you want a name on RRC other than your display name.

=== The LXMF group (like a normal conversation) ===

# Click '''Messages''' in the left sidebar.
# Paste <code>625ad393ca4df62a1382f9d936322a0a</code> into '''Enter an LXMF address to start a conversation''' and press Enter.
# Send <code>/join</code>. The reply welcomes you by name and shows the last few messages.
# '''Add ScotMesh Chat to your contacts.''' The conversation shows a banner, ''This peer is not in your contacts'', with an '''Add to Contacts''' button. Click it.
#: MeshChatX's '''Block Attachments from Strangers''' setting (in '''Settings''' → '''Messages''' → '''Stranger Protection''', on by default) refuses any long message from someone who isn't a contact. The hub keeps its messages short so they get through anyway, but adding the group as a contact means nothing is ever held back.

From then on the chat arrives as <code>Name: message</code>, and whatever you send reaches everyone. <code>/lxmf off</code> pauses it without leaving; <code>/help</code> lists the rest.

=== The chat page (read along, post when you like) ===

# In the left sidebar, under '''Explore''', click '''Nomad Network'''.
# Click '''Open a Nomadnet URL''', or use the address bar at the top once a page is open. Enter <code>c229a2c7d410e00b71f877375ae846bf:/page/index.mu</code> and press Enter.
# Click the star ('''Add Favourite''') so it's one click away next time.
# '''To post''', click the fingerprint button in the page toolbar. Its tooltip reads '''Identify when connecting (off)'''. Confirm, and the page reloads with your identity, showing '''You are''' and your name.
# Type in '''Say''' and click '''Send'''. '''Reload''' fetches new messages; '''Your name & settings''' has your name and LXMF options.

The identify setting belongs to that favourite, so it stays on for the chat page next time. It isn't available in private tabs.

== Full installation ==

With Reticulum installed yourself, any RRC client works: '''Ratspeak''', '''rrc-tui''', '''rrc-gui''', '''WeeChat''' (with the RRC plugin) and '''Eridanus'''. Point the client at the hub address, then:

<syntaxhighlight lang="text">/join scotmesh</syntaxhighlight>

The hub announces itself every 30 minutes, so a client that lists hubs usually shows it without the address being typed.

== Your name ==

Your name belongs to your '''Reticulum identity''' and is the same in the RRC room, the LXMF group and on the page.

<pre>
your identity 178c1f39… ──holds──► "Alex"
│
┌────────────────────────────┼────────────────────────────┐
▼ ▼ ▼
RRC room: Alex LXMF group: "Alex: hi" chat page: Alex
</pre>

* '''Claiming one.''' The first name you use becomes yours. That can be your RRC nickname, the display name your LXMF app announces (spaces become <code>_</code>), a name given with <code>/join Name</code>, or <code>/nick Name</code>. On the page, use "Your name & settings".
* '''Nobody else can take it''', or anything that looks like it: <code>A1ex</code>, <code>Al.ex</code> and <code>ALEX</code> all count as <code>Alex</code>. If your name is taken you are told, and shown as <code>guest-</code> plus four characters of your identity until you choose a free one.
* '''The rules.''' 2 to 24 characters, starting with a letter. Letters (accents are fine), digits, <code>-</code>, <code>_</code> and <code>.</code>, with no spaces. A few words such as ''admin'' and ''scotmesh'' are reserved.
* '''Giving it up.''' <code>/leave</code> frees your name and takes you out of the LXMF group. Messages you already sent keep the name they were sent under.
* '''One identity, one name.''' Each app normally makes its own identity, so a phone and a laptop are two identities and need two names, unless you restore the same identity on both.

== Catching up ==

When you come back to the room over RRC, you get exactly what was said since you last left, with the times it was said:

<pre>
18:02 you disconnect
│ Rab: anyone near Stirling?
│ Ellen: got it, 2 hops
│ … 10 more …
19:30 you reconnect ──► "— 12 messages since you were here (Sat 18:02) —"
the 12 messages, in order
"— end of history —"
</pre>

* Nothing you have already seen is sent again. If nothing was said while you were away, there is no replay.
* The first time you visit, you get the last 10 messages.
* If more than 50 were said, you get the latest 50 and a note to use <code>/history</code> for the rest.
* The chat page marks "new since your last visit" in the same way.
* Messages are kept for 7 days.

== The LXMF group ==

Messages arrive as <code>Name: message</code>, and <code>/me waves</code> arrives as <code>* Name waves</code>. You never get your own messages back from the app you sent them with.

<pre>
hub ──direct──► your messenger (normally within seconds)
│
└─ no answer twice? ──► you're marked away for 10 minutes
│
▼
ScotMesh propagation node ──► your messenger collects it
c283b754… when it next syncs
</pre>

Your LXMF settings, from any way in (see [[Chat commands]]):

* <code>/lxmf on</code> gets every message. This is the default.
* <code>/lxmf off</code> stops group messages but keeps your name and membership.
* <code>/lxmf auto</code> pauses group messages while you are in the room over RRC with the same identity, and starts them again when you leave.
* <code>/lxmf mine on</code> also sends you your own messages from RRC and the page, so your messenger shows the whole conversation.
* When delivery starts again after a pause, you get one note saying how many messages you missed.

<pre>
/lxmf auto: RRC connected ───────────── LXMF paused
RRC disconnected ─────────► LXMF resumes + "12 messages were said while it was paused"
</pre>

== The chat page ==

* It shows the last 30 messages, with "Older" to page back and your own name in green.
* To post, identify to the node first, then use the Say box. <code>/me waves</code> works there. Other commands don't work from the page; use its '''Your name & settings''' page instead.
* '''Your name & settings''' lets you claim or change your name, set LXMF delivery (on, auto or off), choose whether your own messages come to you by LXMF, and leave.
* '''How to join''' lists the three ways in with their addresses.

== Rooms and operators ==

* <code>scotmesh</code> is the main room and always exists. Anyone on RRC can make another room with <code>/join newname</code>. A room exists while someone is in it, unless its founder keeps it with <code>/register</code>.
* Room operators can set the topic, set modes and remove people. Hub operators can ban people from the whole hub and free a name someone is squatting on.
* If you would like to help look after <code>scotmesh</code>, ask in the room or on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord].

== What the hub keeps ==

* '''Messages''' for 7 days, then they are deleted. Nightly backups are kept for 7 days.
* '''For each identity it has seen''': the identity and public key, when it was first and last seen, the name it holds, its settings, and how far it has read in each room. That is what makes names and catching up work.
* '''Bans''', and a log of operator actions.
* It is all on ScotMesh's own server. Nothing is shared with anyone else.

== When something doesn't work ==

; The hub or the group isn't in my app
: Wait up to 30 minutes for the announce, or add the address by hand. Check you are [[Connecting to ScotMesh|connected to ScotMesh]].
; NomadNet's RRC screen says "Unknown command"
: NomadNet handles most slash commands itself and only passes a few to the hub; see [[Chat commands#NomadNet]]. For the others, message the LXMF group or use the chat page's settings.
; I'm shown as <code>guest-…</code>
: Your name was taken, or you haven't claimed one. Send <code>/nick YourName</code>.
; I stopped getting group messages
: Send <code>/whoami</code> to the group to check your settings. <code>/lxmf on</code> turns delivery back on.
; It's quiet
: Scotland is not a big place for Reticulum yet. Leave it open, or ask on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord].

== The wider community ==

The Reticulum community runs its own RRC hub at <code>28c7c1a68c735693aa8e6b8193ed44b2</code>. See [[Learning resources]] for that and the other places people talk.

[[Category:The ScotMesh Backbone]]

The chat room

2026-09-13T00:17:06Z

ScotMesh: Add screenshots of the three ways into the chat

ScotMesh has one chat, the room '''<code>scotmesh</code>''', with three ways into it. Use whichever suits you: everyone sees the same messages, under the same names, whichever way they came in. It is the place to say hello, ask for help, and find out who else is on.

<pre>
MeshChatX, NomadNet, rrc-tui ──── RRC room #scotmesh ────┐
│
Sideband, Columba, MeshChatX ──── LXMF group ────────────┼──► ScotMesh chat hub ──► one conversation
│ (names, history, everyone sees
NomadNet, MeshChatX ───────────── chat page ─────────────┘ settings, 7 days) every message
</pre>

{| class="wikitable"
! Way in !! Address
|-
| RRC room || hub <code>004e5a15da221d9a236b0e8d74195f13</code>, room <code>scotmesh</code>
|-
| LXMF group || <code>625ad393ca4df62a1382f9d936322a0a</code>
|-
| Chat page || <code>c229a2c7d410e00b71f877375ae846bf:/page/index.mu</code>
|}

Every command is listed on [[Chat commands]].

== How it fits together ==

[[File:ScotMesh chat hub architecture.svg|center|frameless|upright=3.2|alt=Diagram: RRC clients, LXMF messengers and NomadNet browsers each reach their own front door in the ScotMesh chat hub. Each door checks the Reticulum identity and its name, then passes messages to the hub core, which works with names, moderation and the store. The hub connects to the Reticulum backbone, and the propagation node holds group messages for members who are away.|How the ScotMesh chat hub fits together]]

The hub is one program on ScotMesh's own server, connected to the backbone at rns.scotmesh.net.

* '''Three front doors.''' The RRC server, the LXMF group and the chat page each speak their own protocol, so every app works with the door it already knows.
* '''Identity first.''' Before a message goes any further, its door checks the Reticulum identity it came from and looks up the name that identity holds. That is why a name is the same everywhere and can't be borrowed, and why messages appear under the author's own name.
* '''One hub core''' puts messages in order, stores them once and sends them out through every door. It also handles catching up, who is here, LXMF settings and commands.
* '''Beside it''' are the names (one per identity, lookalikes refused), moderation (operators, bans and a log of what operators do) and the store, where messages are kept for 7 days.
* '''The propagation node''' holds group messages for LXMF members who are offline until they collect them.

== What it looks like ==

Here is the same conversation seen three ways in MeshChatX. The messages Alex sent from LXMF, RRC and the chat page all turn up in each view, under the same name.

; The RRC room
: The live chat, with who is here, joins and leaves, and room notices. Use it when you want to talk in real time.
[[File:ScotMesh chat RRC room in MeshChatX.png|center|frameless|upright=3.2|alt=MeshChatX showing the scotmesh RRC room: Alex's test messages sent from LXMF, RRC and Nomad, followed by join notices and the room topic.|The #scotmesh RRC room in MeshChatX]]

; The LXMF group
: The chat arrives as ordinary messages from ''ScotMesh Chat'', each one written as <code>Name: message</code>. What you send goes to everyone. It keeps working when you are offline, because missed messages wait on the propagation node.
[[File:ScotMesh chat LXMF group in MeshChatX.png|center|frameless|upright=3.2|alt=MeshChatX conversation with ScotMesh Chat: a message sent to the group, and a reply shown as "Alex: test new setting".|The LXMF group as a MeshChatX conversation]]

; The chat page
: A NomadNet page showing who you are, the recent messages, a box to post, and links to older messages and to your name and settings. When there's something you haven't seen yet, a line marks where it starts.
[[File:ScotMesh chat page in MeshChatX.png|center|frameless|upright=3.2|alt=The ScotMesh chat page open in MeshChatX's NomadNet browser, with the saltire banner, recent messages and a box to post.|The chat page in MeshChatX's page browser]]

== Out of the box ==

Once you are [[Connecting to ScotMesh|connected to ScotMesh]]:

; MeshChatX
: Open the chat section, pick the ScotMesh hub (or add it by the hub address above) and join <code>scotmesh</code>. You can also message the LXMF group. MeshChatX uses one identity for both, so your name is the same in each.
; Sideband, and Columba or Retichat on iPhone
: Start a conversation with <code>625ad393ca4df62a1382f9d936322a0a</code> and send <code>/join</code>. The chat then arrives like any other conversation, as <code>Name: message</code>, and what you send reaches everyone.
; NomadNet
: Open the chat page above to read along. To post, turn on "Identify when connecting" for that node and reload. NomadNet can also join the RRC room from its Channels screen.

== Full installation ==

With Reticulum installed yourself, any RRC client works: '''Ratspeak''', '''rrc-tui''', '''rrc-gui''', '''WeeChat''' (with the RRC plugin) and '''Eridanus'''. Point the client at the hub address, then:

<syntaxhighlight lang="text">/join scotmesh</syntaxhighlight>

The hub announces itself every 30 minutes, so a client that lists hubs usually shows it without the address being typed.

== Your name ==

Your name belongs to your '''Reticulum identity''' and is the same in the RRC room, the LXMF group and on the page.

<pre>
your identity 178c1f39… ──holds──► "Alex"
│
┌────────────────────────────┼────────────────────────────┐
▼ ▼ ▼
RRC room: Alex LXMF group: "Alex: hi" chat page: Alex
</pre>

* '''Claiming one.''' The first name you use becomes yours. That can be your RRC nickname, the display name your LXMF app announces (spaces become <code>_</code>), a name given with <code>/join Name</code>, or <code>/nick Name</code>. On the page, use "Your name & settings".
* '''Nobody else can take it''', or anything that looks like it: <code>A1ex</code>, <code>Al.ex</code> and <code>ALEX</code> all count as <code>Alex</code>. If your name is taken you are told, and shown as <code>guest-</code> plus four characters of your identity until you choose a free one.
* '''The rules.''' 2 to 24 characters, starting with a letter. Letters (accents are fine), digits, <code>-</code>, <code>_</code> and <code>.</code>, with no spaces. A few words such as ''admin'' and ''scotmesh'' are reserved.
* '''Giving it up.''' <code>/leave</code> frees your name and takes you out of the LXMF group. Messages you already sent keep the name they were sent under.
* '''One identity, one name.''' Each app normally makes its own identity, so a phone and a laptop are two identities and need two names, unless you restore the same identity on both.

== Catching up ==

When you come back to the room over RRC, you get exactly what was said since you last left, with the times it was said:

<pre>
18:02 you disconnect
│ Rab: anyone near Stirling?
│ Ellen: got it, 2 hops
│ … 10 more …
19:30 you reconnect ──► "— 12 messages since you were here (Sat 18:02) —"
the 12 messages, in order
"— end of history —"
</pre>

* Nothing you have already seen is sent again. If nothing was said while you were away, there is no replay.
* The first time you visit, you get the last 10 messages.
* If more than 50 were said, you get the latest 50 and a note to use <code>/history</code> for the rest.
* The chat page marks "new since your last visit" in the same way.
* Messages are kept for 7 days.

== The LXMF group ==

Messages arrive as <code>Name: message</code>, and <code>/me waves</code> arrives as <code>* Name waves</code>. You never get your own messages back from the app you sent them with.

<pre>
hub ──direct──► your messenger (normally within seconds)
│
└─ no answer twice? ──► you're marked away for 10 minutes
│
▼
ScotMesh propagation node ──► your messenger collects it
c283b754… when it next syncs
</pre>

Your LXMF settings, from any way in (see [[Chat commands]]):

* <code>/lxmf on</code> gets every message. This is the default.
* <code>/lxmf off</code> stops group messages but keeps your name and membership.
* <code>/lxmf auto</code> pauses group messages while you are in the room over RRC with the same identity, and starts them again when you leave.
* <code>/lxmf mine on</code> also sends you your own messages from RRC and the page, so your messenger shows the whole conversation.
* When delivery starts again after a pause, you get one note saying how many messages you missed.

<pre>
/lxmf auto: RRC connected ───────────── LXMF paused
RRC disconnected ─────────► LXMF resumes + "12 messages were said while it was paused"
</pre>

== The chat page ==

* It shows the last 30 messages, with "Older" to page back and your own name in green.
* To post, identify to the node first, then use the Say box. <code>/me waves</code> works there. Other commands don't work from the page; use its '''Your name & settings''' page instead.
* '''Your name & settings''' lets you claim or change your name, set LXMF delivery (on, auto or off), choose whether your own messages come to you by LXMF, and leave.
* '''How to join''' lists the three ways in with their addresses.

== Rooms and operators ==

* <code>scotmesh</code> is the main room and always exists. Anyone on RRC can make another room with <code>/join newname</code>. A room exists while someone is in it, unless its founder keeps it with <code>/register</code>.
* Room operators can set the topic, set modes and remove people. Hub operators can ban people from the whole hub and free a name someone is squatting on.
* If you would like to help look after <code>scotmesh</code>, ask in the room or on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord].

== What the hub keeps ==

* '''Messages''' for 7 days, then they are deleted. Nightly backups are kept for 7 days.
* '''For each identity it has seen''': the identity and public key, when it was first and last seen, the name it holds, its settings, and how far it has read in each room. That is what makes names and catching up work.
* '''Bans''', and a log of operator actions.
* It is all on ScotMesh's own server. Nothing is shared with anyone else.

== When something doesn't work ==

; The hub or the group isn't in my app
: Wait up to 30 minutes for the announce, or add the address by hand. Check you are [[Connecting to ScotMesh|connected to ScotMesh]].
; NomadNet's RRC screen says "Unknown command"
: NomadNet handles most slash commands itself and only passes a few to the hub; see [[Chat commands#NomadNet]]. For the others, message the LXMF group or use the chat page's settings.
; I'm shown as <code>guest-…</code>
: Your name was taken, or you haven't claimed one. Send <code>/nick YourName</code>.
; I stopped getting group messages
: Send <code>/whoami</code> to the group to check your settings. <code>/lxmf on</code> turns delivery back on.
; It's quiet
: Scotland is not a big place for Reticulum yet. Leave it open, or ask on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord].

== The wider community ==

The Reticulum community runs its own RRC hub at <code>28c7c1a68c735693aa8e6b8193ed44b2</code>. See [[Learning resources]] for that and the other places people talk.

[[Category:The ScotMesh Backbone]]

File:ScotMesh chat RRC room in MeshChatX.png

2026-09-13T00:17:05Z

ScotMesh: == Summary == Screenshots of the chat in MeshChatX

== Summary ==
Screenshots of the chat in MeshChatX

File:ScotMesh chat LXMF group in MeshChatX.png

2026-09-13T00:17:05Z

ScotMesh: == Summary == Screenshots of the chat in MeshChatX

== Summary ==
Screenshots of the chat in MeshChatX

File:ScotMesh chat page in MeshChatX.png

2026-09-13T00:17:05Z

ScotMesh: == Summary == Screenshots of the chat in MeshChatX

== Summary ==
Screenshots of the chat in MeshChatX

The chat room

2026-09-13T00:08:50Z

ScotMesh: Add the architecture diagram: how the chat hub fits together

File:ScotMesh chat hub architecture.svg

2026-09-13T00:08:04Z

ScotMesh: == Summary == How the ScotMesh chat hub fits together: three ways in, the hub core, names, moderation and the store

== Summary ==
How the ScotMesh chat hub fits together: three ways in, the hub core, names, moderation and the store

The chat room

2026-09-13T00:04:22Z

ScotMesh: Link to Chat commands

Chat commands

2026-09-13T00:03:27Z

ScotMesh: Every chat command, for RRC, LXMF, operators and NomadNet

The commands for the [[The chat room|ScotMesh chat]]. Send them in the RRC room or as a message to the LXMF group (<code>625ad393ca4df62a1382f9d936322a0a</code>). The reply goes only to you: over RRC it arrives as a notice, and over LXMF as a message from the group.

<code>/help</code> lists the commands where you are, and <code>/help nick</code> explains one.

== Everyone ==

{| class="wikitable"
! Command !! What it does
|-
| <code>/help [command]</code> || Lists the commands, or explains one.
|-
| <code>/whoami</code> || Shows your name, identity and settings, and where you are connected.
|-
| <code>/nick Name</code> || Takes a name. Your old one is freed.
|-
| <code>/leave</code> || Frees your name and leaves the LXMF group.
|-
| <code>/who</code> || Shows who is here, on RRC and in the LXMF group.
|-
| <code>/history 20</code> || Shows earlier messages, up to 100, at most one request every 15 seconds.
|-
| <code>/topic</code> || Shows the room topic.
|}

== LXMF group ==

{| class="wikitable"
! Command !! What it does
|-
| <code>/join [Name]</code> || Joins the group, optionally with a name. With no name it uses the display name your app announces. You get the last 10 messages to start with.
|-
| <code>/lxmf on</code> || Gets every message. This is the default.
|-
| <code>/lxmf off</code> || Stops group messages. You keep your name and your place in the group.
|-
| <code>/lxmf auto</code> || Pauses group messages while you are in the room over RRC, and starts them again when you leave.
|-
| <code>/lxmf mine on</code> or <code>off</code> || Chooses whether you also get your own messages sent from RRC or the page.
|-
| <code>/pause</code>, <code>/resume</code> || The same as <code>/lxmf off</code> and <code>/lxmf on</code>.
|-
| <code>/me waves</code> || Sends an action: <code>* Name waves</code>.
|}

The <code>/lxmf</code> settings also work from the RRC room. On the chat page they are under '''Your name & settings'''.

== RRC rooms ==

Your RRC client sends joining and leaving itself. These are the hub's own room commands; <code><room></code> is the room name, such as <code>scotmesh</code>.

{| class="wikitable"
! Command !! What it does
|-
| <code>/join newroom</code> || Joins a room, or creates it if nobody is in it. You become its founder.
|-
| <code>/list</code> || Lists registered rooms and their topics.
|-
| <code>/who [room]</code> || Shows who is in a room.
|-
| <code>/topic <room> [text]</code> || Shows the topic, or sets it (only operators can if the room is <code>+t</code>).
|-
| <code>/register <room></code> || The founder keeps the room even when it is empty. It also sets <code>+n</code> and <code>+t</code>.
|-
| <code>/unregister <room></code> || The founder undoes <code>/register</code>.
|}

== Room operators ==

The founder of a room and anyone they make an operator.

{| class="wikitable"
! Command !! What it does
|-
| <code>/op <room> Name</code>, <code>/deop</code> || Makes someone an operator, or removes it.
|-
| <code>/voice <room> Name</code>, <code>/devoice</code> || Lets someone speak in a moderated (<code>+m</code>) room, or removes it.
|-
| <code>/kick <room> Name</code> || Removes someone from the room. They can come back.
|-
| <code>/ban <room> add Name</code> || Bans someone from the room. <code>del</code> lifts it and <code>list</code> shows the bans.
|-
| <code>/invite <room> add Name</code> || Invites someone to an invite-only or keyed room for 15 minutes.
|-
| <code>/mode <room> +m</code> || Sets a room mode. See below.
|}

Over LXMF the room is always <code>scotmesh</code>, so leave it out: <code>/kick Name</code>, <code>/ban add Name</code>.

{| class="wikitable"
! Mode !! Meaning
|-
| <code>+i</code> || Invite only.
|-
| <code>+k key</code> || A key is needed to join; <code>-k</code> removes it.
|-
| <code>+m</code> || Moderated: only operators and voiced people can speak.
|-
| <code>+n</code> || No messages from people not in the room.
|-
| <code>+p</code> || Private: left out of <code>/list</code>, and <code>/who</code> is refused.
|-
| <code>+t</code> || Only operators can change the topic.
|}

== Hub operators ==

{| class="wikitable"
! Command !! What it does
|-
| <code>/kline add Name [reason]</code> || Bans an identity from the whole hub and disconnects it everywhere. <code>del</code> lifts it and <code>list</code> shows the bans.
|-
| <code>/release Name</code> || Frees a name someone holds. They are told.
|-
| <code>/stats</code> || Shows the hub's counters.
|}

== Naming someone ==

Where a command takes a name, you can give:
* their name (lookalikes match, so <code>rab</code> finds <code>Rab</code>);
* their guest name, such as <code>guest-2af3</code>;
* six or more characters of their identity hash;
* the whole 32-character hash.

If several people match, the hub lists them and asks for a longer hash.

== NomadNet ==

NomadNet's RRC screen handles slash commands itself. <code>/help</code> there shows NomadNet's own list, and <code>/nick</code> sets the name NomadNet sends. It passes only these to the hub:

<code>/who /names /topic /mode /kick /ban /invite /op /deop /voice /devoice /register /unregister /kline /stats</code>

For anything else (<code>/whoami</code>, <code>/lxmf</code>, <code>/history</code>, <code>/leave</code> to free your name), message the LXMF group, or use '''Your name & settings''' on the chat page. In NomadNet, <code>/leave</code> on the RRC screen leaves the room; it doesn't free your name.

MeshChatX passes every command to the hub.

[[Category:The ScotMesh Backbone]]

The chat room

2026-09-13T00:03:26Z

ScotMesh: Full guide to the chat: names, catching up, LXMF delivery, page, what is kept, troubleshooting, with diagrams

The chat room

2026-09-12T23:36:48Z

ScotMesh: The chat is now one hub with three ways in: RRC, LXMF group and chat page

ScotMesh has one chat, the room '''<code>scotmesh</code>''', with three ways into it. Use whichever suits you; everyone sees the same messages. It is the place to say hello, ask for help, and find out who else is on.

{| class="wikitable"
! Way in !! Address !! Use it from
|-
| RRC room || hub <code>004e5a15da221d9a236b0e8d74195f13</code>, room <code>scotmesh</code> || MeshChatX, NomadNet, Ratspeak, rrc-tui, WeeChat
|-
| LXMF group || <code>625ad393ca4df62a1382f9d936322a0a</code> (send <code>/join</code>) || Sideband, MeshChatX, NomadNet, Columba
|-
| Chat page || <code>c229a2c7d410e00b71f877375ae846bf:/page/index.mu</code> || NomadNet, MeshChatX
|}

== Out of the box ==

Once you are [[Connecting to ScotMesh|connected to ScotMesh]]:

* '''MeshChatX:''' open the chat section, pick the ScotMesh hub (or add it by the address above) and join <code>scotmesh</code>. Or message the LXMF group.
* '''Sideband''' and the '''iPhone apps (Columba, Retichat):''' start a conversation with <code>625ad393ca4df62a1382f9d936322a0a</code> and send <code>/join</code>. From then on the chat arrives like any other conversation, as <code>Name: message</code>, and anything you send reaches everyone.
* '''NomadNet:''' open the chat page above to read. To post, turn on "Identify when connecting" for that node.

== Full installation ==

With Reticulum installed yourself, any RRC client works: '''Ratspeak''', '''rrc-tui''', '''rrc-gui''', '''WeeChat''' (with the RRC plugin) and '''Eridanus'''. Point the client at the hub address, then:

<syntaxhighlight lang="text">/join scotmesh</syntaxhighlight>

The hub announces itself every 30 minutes, so a client that lists hubs will usually show it without the address being typed.

== What to expect ==

* '''Catching up.''' When you come back to the room over RRC you get exactly what was said since you last left, with the times it was said, and nothing you have already seen. The first time you visit you get the last 10 messages. <code>/history 50</code> shows more. The chat page marks what is new since your last visit. Messages are kept for 7 days.
* '''Your name is yours everywhere.''' The first name you use (your nickname, your LXMF display name, or <code>/nick YourName</code>) belongs to your Reticulum identity on all three ways in, and nobody else can take it or something that looks like it (<code>A1ex</code> counts as <code>Alex</code>). Until you have one you show as <code>guest-</code> and four characters of your identity. <code>/leave</code> gives your name up.
* '''One identity, one name.''' Each app or device normally has its own identity. MeshChatX uses the same identity for RRC and LXMF, so one name covers both there; a phone and a laptop with different identities need different names (or restore the same identity on both).
* '''LXMF when you are on RRC.''' <code>/lxmf off</code> stops group messages without leaving; <code>/lxmf auto</code> pauses them while you are in the room over RRC and starts them again when you leave; <code>/lxmf on</code> is the default. When they start again you get one note saying how many you missed.
* '''Away from the network.''' If your messenger is offline, group messages wait on our [[Propagation node|propagation node]] until you collect them.
* '''It can be quiet.''' Scotland is not a big place for Reticulum yet. If nobody answers, leave it open, or ask on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord].

== Commands ==

Send these in the room, to the group, or use the "Your name & settings" page on the chat page.

{| class="wikitable"
! Command !! What it does
|-
| <code>/help</code> || lists the commands where you are
|-
| <code>/whoami</code> || your name, identity and settings
|-
| <code>/nick YourName</code> || take a name (your old one is freed)
|-
| <code>/who</code> || who is here, on RRC and in the group
|-
| <code>/history 20</code> || earlier messages
|-
| <code>/lxmf on</code>, <code>off</code>, <code>auto</code> || LXMF group delivery
|-
| <code>/leave</code> || give up your name and leave the group
|}

== Operators ==

Room operators can set the topic and, if it ever comes to it, remove someone. Ask in the room or on the ScotMesh Discord if you would like to help look after the <code>scotmesh</code> room.

== Your own rooms ==

Anyone on RRC can create a room on the hub with <code>/join</code> followed by a new name. Rooms exist while someone is in them, unless their founder registers them with <code>/register</code>.

== The wider community ==

The Reticulum community runs its own RRC hub at <code>28c7c1a68c735693aa8e6b8193ed44b2</code>; see [[Learning resources]] for that and the other places people talk.

[[Category:The ScotMesh Backbone]]

Services and addresses

2026-09-11T19:28:05Z

ScotMesh: ScotMesh 868 moves to 869.4625 MHz (Ofcom 869.40-869.65 MHz sub-band)

Every address for the ScotMesh node in one place. This is the page to copy from; each service is explained on its own page.

== Entry points ==

{| class="wikitable"
! Way in !! Address !! Notes
|-
| TCP || <code>rns.scotmesh.net</code>, port <code>4242</code> || The normal route. Interface type <code>TCPClientInterface</code>. See [[Connecting to ScotMesh]].
|-
| I2P || <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code> || For networks that block outbound connections. Interface type <code>I2PInterface</code>. See [[Access over I2P]].
|-
| LoRa || ScotMesh 433 or ScotMesh 868 radio profile || Within range of a gateway only. See [[RNode]].
|}

== Services ==

{| class="wikitable"
! Service !! Address !! Reached from
|-
| Chat hub (RRC), room <code>scotmesh</code> || <code>004e5a15da221d9a236b0e8d74195f13</code> || MeshChatX, Ratspeak, rrc-tui, rrc-gui, WeeChat, Eridanus. See [[The chat room]].
|-
| LXMF propagation node || <code>c283b754e0acc11ce48d2f5e29167e0c</code> || Sideband, MeshChatX, Nomad Network, usually picked automatically. See [[Propagation node]].
|-
| Nomad Network node || <code>10a839df2c50635bcb0c8a299b9ca0f8</code> || Nomad Network, MeshChatX. Entry page <code>10a839df2c50635bcb0c8a299b9ca0f8:/page/index.mu</code>. See [[Nomad Network]].
|-
| Transport instance || <code>20b962cd814444f7812e409e7c47f319</code> || Not something you connect to: it is the node's own identity, and what appears in <code>rnpath</code> output and on node maps. Announced as “ScotMesh Backbone”.
|}

== Radio profiles ==

Every radio on the network must use exactly these settings; see [[RNode]] for why.

{| class="wikitable"
! !! ScotMesh 433 !! ScotMesh 868
|-
| Frequency || 433.775 MHz || 869.4625 MHz
|-
| Bandwidth || 125 kHz || 125 kHz
|-
| Spreading factor || 8 || 9
|-
| Coding rate || 4/5 || 4/5
|-
| TX power || 7 dBm || 22 dBm
|}

== Which addresses could change ==

* The '''hostname and port''' are stable.
* The '''destination addresses''' (chat hub, propagation node, Nomad Network node, transport instance) are derived from identity keys the node keeps backed up. They would only change if a key were lost or deliberately replaced, and we would say so here and on [https://rns.scotmesh.net rns.scotmesh.net].
* The '''I2P address''' is derived from a random key. It is backed up too, but of all the addresses it is the one most likely to change one day, so check here if it stops working.

[[Category:The ScotMesh Backbone]]

ScotMesh microReticulum

2026-09-11T19:28:05Z

ScotMesh: ScotMesh 868 moves to 869.4625 MHz (Ofcom 869.40-869.65 MHz sub-band)

'''ScotMesh microReticulum''' is our build of [https://github.com/attermann/microReticulum_Firmware attermann's microReticulum firmware]. It turns a LoRa board into its own Reticulum transport node, so a board on a hill or a roof can relay for the mesh with no Raspberry Pi. On top of upstream it adds:

* the SenseCAP Solar Node P1;
* battery reporting;
* a NomadNet page you can manage the node from over the mesh;
* a small telemetry API;
* a position on [https://rmap.world rmap.world].

Source: [https://github.com/A13xB0/microReticulum_Firmware github.com/A13xB0/microReticulum_Firmware]. Firmware: [https://rnode.scotmesh.net rnode.scotmesh.net] (choose ''Standalone node'').

== Boards ==

{| class="wikitable"
|-
! Board
! Node pages & API
! Firmware update over the air
|-
| Seeed SenseCAP Solar Node P1 🏴󠁧󠁢󠁳󠁣󠁴󠁿 built by ScotMesh
| Yes
| Bluetooth update window, or USB bootloader
|-
| Heltec V2/V3/V4, Heltec Wireless Tracker V2, XIAO ESP32S3, T-Beam Supreme, T-Deck
| Yes
| WiFi update window
|-
| T-Beam, T3S3, LoRa32 v1/v2/v2.1, RNode NG 2.0/2.1, Feather ESP32, generic ESP32
| Yes
| USB only (one firmware slot)
|-
| RAK4631, RAK3401, T-Echo
| Original microReticulum pages (the new ones don't fit their flash yet)
| USB
|}

== Setting a node up ==

# Open [https://rnode.scotmesh.net rnode.scotmesh.net] in Chrome or Edge on a computer. Choose '''Standalone node''', pick your board, and flash.
# On the configure step:
#* pick '''ScotMesh 868''' (or 433);
#* give the node a name;
#* choose its role (normally ''Fixed relay'');
#* paste your identity hash under ''Remote management''. That makes you its admin.
# The node restarts in transport mode and announces its NomadNet page. You can do everything else from that page over the mesh.

== Using the node's page ==

Open the node's NomadNet address in Nomad Network or MeshChatX. You'll find the address:

* at the end of the flasher;
* on the node's ''About'' page;
* in the node's announce.

Every page is small enough to arrive in '''one LoRa packet''', so it loads first time even on weak links. Most are 150–300 bytes, and the limit is 409.

''The screenshots below are the real pages, fetched over LoRa from our bench P1 (3 hops, through rns.scotmesh.net and a gateway). What you see in your browser depends on its colours.''

=== Home page ===

[[File:home.png|frameless|upright=2.2|The node's home page as a visitor sees it]]

The home page shows:

* the node's name;
* its battery, as a bar (green / amber / red) with % and voltage, plus <span style="color:#22cc55;">▲</span> while charging or <span style="color:#dd9933;">▼</span> while discharging;
* uptime and the number of known routes.

An admin can also show the radio settings, airtime and an operator line. The footer always shows the firmware version and the board. ''Not identified'' means your browser hasn't identified to the node. That's fine for visitors.

=== Routes and neighbours ===

[[File:routes.png|frameless|upright=2.2|Routes page with short addresses]]

'''Routes''' lists the node's path table: destination, hops and when it was last heard. '''Neighbours''' lists the transport nodes it hears directly, with their names where they announce one. To change the view:

* tick ''Short'' for 8-character addresses (or leave it off for full ones);
* set ''Rows'' and press ''Apply'';
* use ''next'' and ''back'' to page through.

An admin can hide both pages from visitors.

=== Becoming an admin ===

You are an admin if your identity is on the node's remote-management list (the same list <code>rnstatus -R</code> checks). In your browser, choose '''Identify''' for the node (NomadNet: the ''Identify'' option on the page; MeshChatX: ''identify to this node'') and reload. The page then shows 🛡️ ''Verified identity'' and an '''Admin''' link. There is no password to log in with: being identified is being logged in.

[[File:home-admin.png|frameless|upright=2.2|Home page seen by an admin]]

Admins see every row. A <code>*</code> marks rows that visitors don't see.

If an admin has switched on '''password registration''', a visitor who has identified sees ''Register''. Entering the password adds their identity as an admin, or puts them in a queue for an existing admin to approve.

=== The admin pages ===

[[File:admin-hub.png|frameless|upright=2.2|Admin hub]]

The hub shows battery and uptime, and warns you when a radio trial needs confirming or someone is waiting for approval. It links to three sections.

{| class="wikitable"
|-
! Section
! Pages
|-
| Settings
| '''Name & announce''': renaming announces straight away. Announce every 30 min, 1 h, 3 h, 6 h or 12 h.<br />
'''Home page''': what visitors see, telemetry API on or off, and a visitor preview.<br />
'''Map''': rmap.world position.<br />
'''Radio''', '''Role''', '''Power'''
|-
| Access
| '''Admins''': add by identity hash; remove with confirmation.<br />
'''Password''' registration.<br />
'''Change log''': every admin change, with time and who made it.
|-
| Device
| '''Health''': free RAM and flash, starts and last reset reason, noise floor, last RSSI/SNR, airtime, packets, table sizes.<br />
'''Lights & Bluetooth''', '''Logs''' (last five log lines), '''Maintenance''', '''Restart & update''', '''About'''
|}

[[File:settings.png|frameless|upright=2.2|Settings section]]

[[File:device.png|frameless|upright=2.2|Device section]]

==== Name & announce ====

[[File:name.png|frameless|upright=2.2|Name and announce page]]

Change the name, set an optional operator line (e.g. a callsign) and set how often the node announces its page. Longer intervals save airtime on a busy channel. Renaming announces at once.

==== Home page layout ====

[[File:home-layout.png|frameless|upright=2.2|Home page layout settings]]

Tick what visitors may see. ''Preview'' shows the page as a visitor would see it. ''Telemetry API'' turns the <code>/api</code> endpoints on or off.

==== Radio and role ====

[[File:radio.png|frameless|upright=2.2|Radio page]]

'''Radio changes are a trial.''' Enter new settings (or pick ''ScotMesh 868'' / ''433'') and press ''Try these''. The node uses them for five minutes. Reconnect on the new settings and press ''Keep''. If you don't, the node goes back to the old settings by itself, so a mistake can't strand a remote node.

[[File:role.png|frameless|upright=2.2|Role page]]

'''Role''':

* ''Fixed relay'': forwards for everyone. Use it for hilltop and roof nodes.
* ''Access point'': for a node that serves nearby clients.
* ''Mobile'': for a node that moves.
* ''End device'': never forwards.

A role change applies after a restart.

==== Power ====

[[File:power.png|frameless|upright=2.2|Power page]]

Below a chosen battery level, the node can lower its TX power to 10 dBm or turn its radio off until it has charged. It can also keep its radio off below 3.3 V to protect the cell.

==== Admins and password registration ====

[[File:admins.png|frameless|upright=2.2|Admins page]]

[[File:password.png|frameless|upright=2.2|Password registration page]]

* '''Admins''' (up to 8): paste a 32-character identity hash and press ''Add''. Tap an identity to remove it; you're asked to confirm. The node won't remove its last admin.
* '''Password registration''' is off by default. An admin sets a password. Someone who knows it can identify to the node and register their own identity as an admin.
** Three wrong tries lock that identity for 15 minutes.
** Ten wrong tries in an hour pause registration.
** With ''Needs approval'' ticked, new registrations wait for an existing admin.

==== Health, lights and Bluetooth ====

[[File:health.png|frameless|upright=2.2|Health page]]

[[File:lights.png|frameless|upright=2.2|Lights and Bluetooth page]]

'''Lights''':

* the activity LEDs can be on, off, or on only for the first 10 minutes after a start;
* ''Blink 30 s'' helps you find a node on a mast;
* error patterns always show.

'''Bluetooth''' can be turned off to save power on a sealed box. ''Unpair all'' forgets paired phones.

==== Maintenance ====

[[File:maintenance.png|frameless|upright=2.2|Maintenance page]]

From here you can:

* announce now;
* restart automatically every day or every week;
* clear stored routes and data;
* factory reset. This keeps the node's identity and its admins.
* full reset. The node forgets its identity too: new addresses, no admins, no settings. Use it to hand a node on, or before re-flashing it as a different node. Afterwards it needs USB to make it yours again (the flasher's ''Reconfigure'' path).

Anything disruptive asks you to confirm, with a link that works once, for two minutes.

=== Restart and firmware updates without a cable ===

[[File:update.png|frameless|upright=2.2|Restart and update page]]

Updates are started from the node's page over the mesh, but the firmware itself is too big to send over LoRa, so someone has to be near the node with a phone or laptop for the transfer. The node accepts the new image's hash by itself afterwards; you don't need <code>rnodeconf</code> or the flasher.

'''WiFi update''' (ESP32 boards with two firmware slots: Heltec V2/V3/V4, Tracker V2, XIAO ESP32S3, T-Beam Supreme, T-Deck):

# ''Device → Restart & update → WiFi update → Yes, start''. The page shows a one-time WiFi password. Write it down; it is shown once.
# The node restarts as a WiFi access point called '''ScotMesh-Update''', off the mesh, for '''20 minutes'''.
# Within WiFi range, join that network with the password and open '''<nowiki><nowiki>http://192.168.4.1</nowiki></nowiki>'''.
# Choose the <code>.bin</code> from inside the board's release zip (for example <code>rnode_firmware_heltec32v3.bin</code>) and press ''Update''. The node verifies it and restarts into the new firmware.

A WiFi update leaves the node running from its second firmware slot. That's fine for the flasher (it always resets the slot choice), but if you later update by hand with <code>esptool</code> or <code>rnodeconf</code>, write <code>boot_app0.bin</code> at <code>0xE000</code> as well as the firmware, or the board keeps booting the old slot and refuses to start transport ("device init failed").

If nothing is uploaded in 20 minutes, or the upload fails, the node restarts unchanged. The 4 MB boards (T-Beam, T3S3, LoRa32, RNode NG, Feather, generic ESP32) have one firmware slot and can only be updated over USB.

'''Bluetooth update''' (SenseCAP P1):

# This restarts the node with a Bluetooth firmware-update service for '''20 minutes'''. It advertises as <code>SenseCAP P1 DFU</code>.
# Within Bluetooth range, open '''nRF Device Firmware Update''' or '''nRF Connect''' on a phone.
# Send the node's <code>rnode_firmware_seeed_solar_node_p1.zip</code> from the [https://github.com/A13xB0/microReticulum_Firmware/releases releases].

If nothing connects, the node restarts normally when the window closes.

'''USB bootloader''' is for someone on site with a laptop. The node waits in its bootloader until it is flashed (for example from rnode.scotmesh.net) or reset.

None of these start below 30 % battery unless the node is charging.

=== Starting a node from scratch ===

The flasher keeps a node's identity, settings and routes across a reflash, which is what you want for an update. To wipe a node and start again (a second-hand board, or one you want new addresses for), tick '''Start from scratch: erase everything first''' on the flasher's Flash step. On ESP32 boards that erases the whole flash; on the P1 and other nRF52 boards it asks the firmware for a full reset and wipes the EEPROM. Either way the node comes back with a new identity and the flasher provisions and configures it again.

== Showing the node on rmap.world ==

[[File:map.png|frameless|upright=2.2|Map page after saving a position]]

# On ''Settings → Map'', paste the node's position straight from Google Maps. Right-click the spot and click the coordinates, e.g. <code>56.19858019391934, -3.1666195614405708</code>. Degrees-minutes-seconds works too.
# Set its height in metres.
# Choose ''Exact'' or ''~1 km''.
# Tick ''Publish'' and save.

The node then sends the standard Reticulum interface-discovery announce on the announce interval. It's the same announce a PC node sends with <code>discoverable = yes</code>. rns.scotmesh.net peers with rmap.world, so the announce reaches the map through the backbone.

The position is public once published. Use ''~1 km'' if that matters.

== Telemetry API ==

For trackers and dashboards, the node answers plain JSON requests on the same NomadNet address.

* '''No identity is needed.'''
* An admin can switch the API off under ''Home page''.
* Each reply fits in one packet.
* List endpoints page with <code>o</code> (offset) and <code>n</code> (rows), and add <code>"more": true</code> when there are more rows.

{| class="wikitable"
|-
! Path
! Request data
! Reply (real examples from the bench P1)
|-
| <code>/api</code>
| —
| <code>{"v":1,"api":["bat","up","radio","net","sys","health","pos","paths","nbrs","all"]}</code>
|-
| <code>/api/bat</code>
| —
| <code>{"percent":96,"voltage":4.11,"charging":true}</code>
|-
| <code>/api/up</code>
| —
| <code>{"uptime":134,"reset":"soft-reset"}</code>: seconds since start, and why it last started
|-
| <code>/api/radio</code>
| —
| <code>{"freq":869462500,"bw":125000,"sf":9,"cr":5,"txp":22,"airtime":4.4,"noise":-105,"rssi":-59,"snr":10}</code>
|-
| <code>/api/net</code>
| —
| <code>{"routes":159,"neighbours":1,"rx":20,"tx":18,"links":1}</code>
|-
| <code>/api/sys</code>
| —
| <code>{"fw":"v1.86-scotmesh.3","board":"SenseCAP P1","name":"…","free_ram":33472,"free_flash":1822720}</code>
|-
| <code>/api/health</code>
| —
| <code>{"free_ram":33472,"free_flash":1822720,"reboots":7,"reset":"soft-reset","paths":159,"paths_max":500,"announces":0,"neighbours":1}</code>
|-
| <code>/api/pos</code>
| —
| <code>{"lat":56.19858,"lon":-3.16662,"height":310}</code>, or <code>{"error":"not published"}</code>
|-
| <code>/api/all</code>
| —
| battery + uptime + network + airtime in one reply
|-
| <code>/api/paths</code>
| <code>{"o":0,"n":5,"s":0}</code>
| <code><nowiki>{"total":159,"o":0,"cols":["dest","hops","age_s","via"],"rows":[[…],…],"more":true}</nowiki></code>
|-
| <code>/api/nbrs</code>
| <code>{"o":0,"n":5,"s":1}</code>
| <code>{"total":1,"o":0,"cols":["dest","age_s","name"],"rows":[…]}</code>
|}

<code>s=1</code> gives 8-character addresses. Unknown paths answer <code>{"error":"unknown endpoint","see":"/api"}</code>. If the node is short of memory, it answers <code>{"error":"busy"}</code>.

Here's a tracker in Python. It needs Reticulum installed and connected to the mesh, e.g. with a TCP interface to <code>rns.scotmesh.net</code> port 4242:

<syntaxhighlight lang="text">import RNS, json, time
RNS.Reticulum()
node = bytes.fromhex("cb37c17f7280d61d66b5278a02313d25") # the node's NomadNet address
if not RNS.Transport.has_path(node):
RNS.Transport.request_path(node)
while not RNS.Transport.has_path(node): time.sleep(0.5)
dest = RNS.Destination(RNS.Identity.recall(node), RNS.Destination.OUT,
RNS.Destination.SINGLE, "nomadnetwork", "node")
link = RNS.Link(dest) # no identify() needed
while link.status != RNS.Link.ACTIVE: time.sleep(0.2)
link.request("/api/all", response_callback=lambda r: print(json.loads(r.response)))
link.request("/api/paths", data={"o": 0, "n": 5},
response_callback=lambda r: print(json.loads(r.response)))</syntaxhighlight>
Keep one link open and poll every few minutes. Each request and reply is a single small packet (typically 3–5 s round trip over three hops).

== Good to know ==

<ul>
<li>The node keeps its settings in its own flash. Its identity and admin list survive firmware updates and a factory reset.</li>
<li>One exception: RNode NG 2.0/2.1 and LoRa32 v2.1 nodes flashed with v1.86-scotmesh.2 or earlier get a new identity when updated to .4 or later, because those boards moved to a larger app slot (2.25 MB) to fit the pages. Add the node's new identity to your admin list again afterwards. Updates after that keep the identity.</li>
<li>Memory is watched:
<ul>
<li>pages and the API never copy the route table;</li>
<li>the change log is a fixed 1.3 KB file;</li>
<li>below about 8 KB of free RAM, the node answers "busy" rather than risk running out.</li></ul>

''Health'' and <code>/api/health</code> show free RAM, so a slow leak shows up as a trend.</li>
<li>The LEDs on the P1:
<ul>
<li>white flash: packet received;</li>
<li>blue flash: packet sent;</li>
<li>blue and white alternating fast: the radio failed to start (the node restarts itself after a few seconds).</li></ul></li>
<li>Full debug logging stays in the firmware. Connect over USB and open a serial console at 115200 to see it.</li>
<li>Upstream differences and the full change history are in the repository's README.</li></ul>

[[Category:Hardware]]

RNode

2026-09-11T19:28:03Z

ScotMesh: ScotMesh 868 moves to 869.4625 MHz (Ofcom 869.40-869.65 MHz sub-band)

An '''RNode''' is a LoRa board running RNode firmware. It is not a Meshtastic or MeshCore radio, though much of the same hardware can be reflashed into one. It is the standard way to put Reticulum on the air.

== ScotMesh radio settings ==

Every radio on the network must use '''identical''' settings. This is not a tolerance thing: a board with a different spreading factor is completely deaf to the others, and nothing reports an error. If two of your radios cannot hear each other, check these before anything else.

{| class="wikitable"
|-
!
! ScotMesh 433
! ScotMesh 868
|-
| '''Frequency'''
| 433.775 MHz
| 869.4625 MHz
|-
| '''Bandwidth'''
| 125 kHz
| 125 kHz
|-
| '''Spreading factor'''
| 8
| 9
|-
| '''Coding rate'''
| 4/5
| 4/5
|-
| '''TX power'''
| 7 dBm
| 22 dBm
|}

'''ScotMesh 868 moved from 867.5 MHz to 869.4625 MHz on 11 September 2026''' to keep within Ofcom's rules. It now sits in the UK's 869.40–869.65 MHz sub-band, which allows up to 500 mW ERP with a 10% duty cycle; the old frequency's sub-band allows only 25 mW. A radio still on 867.5 MHz cannot hear the network, so retune it: the flasher's Configure step, the node's Radio page, or <code>rnodeconf -T</code> below.

As Reticulum config values, those are:

<syntaxhighlight lang="text"> # ScotMesh 868
[[ScotMesh RNode]]
type = RNodeInterface
enabled = yes
port = /dev/ttyUSB0
frequency = 869462500
bandwidth = 125000
txpower = 22
spreadingfactor = 9
codingrate = 5

# ScotMesh 433
[[ScotMesh RNode]]
type = RNodeInterface
enabled = yes
port = /dev/ttyUSB0
frequency = 433775000
bandwidth = 125000
txpower = 7
spreadingfactor = 8
codingrate = 5</syntaxhighlight>
== Flashing a board ==

The easiest way is [https://rnode.scotmesh.net rnode.scotmesh.net], the '''ScotMesh Flasher'''. It flashes the board from your browser over USB — nothing to install. Open it in Chrome or Edge on a desktop (Firefox and Safari do not implement WebSerial, and it will not work on a phone), plug the board in, and follow the steps:

# '''What are you building?''' — an ''RNode radio'' (for a computer or phone running Sideband, MeshChatX or NomadNet) or a ''standalone node'' (a self-contained microReticulum transport node — see below).
# '''Your hardware''' — pick the board and its band.
# '''Firmware''' — the latest release is fetched for you from the site's own mirror and its checksum verified.
# '''Connect''' and '''Flash''' — pick the port from the browser prompt; nRF52 boards are put into their bootloader automatically (press reset twice if that fails).
# '''Provision''' — the board's identity block and firmware hash are written and verified, the same as <code>rnodeconf --autoinstall</code>.
# '''Configure''' — for an RNode radio only Bluetooth; the radio profile is set by the app you connect it to, so the ScotMesh values are shown for you to enter there. For a standalone node: the ScotMesh 433 or 868 profile, a name, its role and the identities allowed to manage it.

If the board does not appear in the port list, hold its BOOT button while plugging it in, and check you are using a data USB cable rather than a charge-only one.

=== Standalone node (microReticulum) ===

The same boards can run [https://github.com/A13xB0/microReticulum_Firmware microReticulum], the RNode firmware with a Reticulum transport stack built in. The board then ''is'' the node: it has its own identity, routes for others, serves a NomadNet page and can be managed over the mesh with <code>rnstatus -R</code> — no Raspberry Pi or computer attached. That is what ScotMesh uses for solar and hilltop relays; [[ScotMesh firmware]] explains what our build adds. Choose '''Standalone node''' in the flasher; the '''Seeed SenseCAP Solar Node P1''' (solar charger and battery built in) is the reference board and is built by ScotMesh — it does not exist in the upstream firmware. ''Reconfigure an existing node'' on the flasher's first screen connects over USB or Bluetooth to change settings later.

The command-line route does the same job and works on any platform:

<syntaxhighlight lang="text">pip install rns
rnodeconf --autoinstall
rnodeconf -T --freq 869462500 --bw 125000 --sf 9 --cr 5 --txp 22 /dev/ttyUSB0
rnodeconf -i /dev/ttyUSB0</syntaxhighlight>
<code>--autoinstall</code> is interactive: it detects the board, confirms the model with you, and installs the correct signed firmware. The second command writes the ScotMesh defaults into the device. The third prints them back so you can check.

== Supported boards ==

* Heltec LoRa32 v2, v3, v4
* Heltec Mesh Node T114
* LilyGO LoRa32 v1.0, v2.0, v2.1
* LilyGO LoRa32 T3S3
* LilyGO T-Beam, T-Beam Supreme
* LilyGO T-Deck
* LilyGO T-Echo
* RAK4631
* Seeed XIAO ESP32S3 with Wio-SX1262 (433 and 868)
* Homebrew RNode

'''Buy the board for the band you want.''' An 868 MHz board cannot be moved to 433 MHz by changing settings — the radio and the antenna are physically different parts.

== Serial or Bluetooth ==

Over USB there is nothing to configure: the board appears as a serial port and Reticulum talks to it. That is the right choice for a node that stays in one place.

For a phone, or a board you would rather not tether, use the Bluetooth buttons on [https://rnode.scotmesh.net rnode.scotmesh.net], or from the command line:

<syntaxhighlight lang="text">rnodeconf -b /dev/ttyUSB0 # Bluetooth on
rnodeconf -p /dev/ttyUSB0 # pairing mode
rnodeconf -B /dev/ttyUSB0 # Bluetooth off</syntaxhighlight>
Not every supported board has Bluetooth. An Android phone with Sideband and an RNode paired over Bluetooth is a complete off-grid messenger with no phone network involved.

== Legal ==

Transmit power and transmit time are both regulated, and the limits differ by band and sub-band. The figures above are what ScotMesh uses; confirm what applies to your situation before transmitting.

If you are operating under an amateur licence, set <code>id_callsign</code> and <code>id_interval</code> on the interface so it identifies periodically. Set <code>airtime_limit_short</code> and <code>airtime_limit_long</code> to keep within duty-cycle limits — they are easy to exceed on a busy link.

[[Category:Hardware]]

Main Page

2026-09-11T19:28:02Z

ScotMesh: ScotMesh 868 moves to 869.4625 MHz (Ofcom 869.40-869.65 MHz sub-band)

{{DISPLAYTITLE:ScotMesh Reticulum Wiki}}
<div class="sm-otherwiki"><span class="sm-ow-logos"><span class="sm-ow-logo sm-ow-mt" title="Meshtastic"></span><span class="sm-ow-logo sm-ow-mc" title="MeshCore"></span></span><span class="sm-ow-text">Looking for <b>MeshCore</b> or <b>Meshtastic</b>? They have their own wiki at [https://wiki.scotmesh.uk wiki.scotmesh.uk] →</span></div>
<div class="sm-hero">
<div class="sm-hero-title">A free, encrypted network for Scotland that anyone can join.</div>
<div class="sm-hero-sub">Reticulum carries messages, chat, files and pages over the internet and over LoRa radio, and keeps working when the things underneath it do not. Connecting takes about five minutes.</div>
<div class="sm-hero-actions"><span class="sm-btn sm-btn-primary">[[Connecting to ScotMesh|Connect in five minutes →]]</span><span class="sm-btn sm-btn-secondary">[[What Reticulum is|What is Reticulum?]]</span></div>
<div class="sm-hero-facts"><span>No sign-up</span><span>No hardware needed</span><span>Free, run by the community</span><span>Encrypted end to end</span></div>
</div>

<div class="sm-welcome">
'''Welcome.''' ScotMesh runs the Reticulum backbone for Scotland and writes this wiki; you are very welcome to use both, and to add to either. Whether you have never heard of Reticulum or you want to put a solar relay on a hill, there is a page here for you. Pick where you are:
</div>

<div class="sm-cards">
<div class="sm-card">
=== I just want to try it ===
Install one app, type in one address, and you are on the network with everyone else: messaging, chat, files and pages.

'''[[Connecting to ScotMesh|Connect in five minutes →]]'''

Then [[First steps]]: say hello in the chat room and send your first message.
</div>
<div class="sm-card">
=== I want to understand it first ===
No addresses to configure, no accounts, no company in the middle. Reticulum is unusual, and it is worth knowing why.

'''[[What Reticulum is|What Reticulum is →]]'''

Then [[How Reticulum works]], [[How it compares]] with Meshtastic and MeshCore, and the [[Glossary]].
</div>
<div class="sm-card">
=== I want to put a radio on air ===
A LoRa board becomes a Reticulum radio for your laptop or phone, or a self-contained relay you can look after from home.

'''[[RNode|Flash a board →]]'''

Then [[ScotMesh firmware]] for solar and hilltop relays, and [[Antennas and siting]] for making it reach.
</div>
</div>

== The backbone right now ==

Live from the node itself, the same feed as [https://rns.scotmesh.net rns.scotmesh.net], refreshed every two minutes. If the strip is blank or says unknown, treat the backbone as unconfirmed and check the node page directly.

<div id="sm-status" class="sm-status">Live backbone status: [https://rns.scotmesh.net/status.html rns.scotmesh.net/status]</div>

== Connect now ==

The backbone is a public Reticulum transport node in Dalgety Bay, Fife. Anyone may connect, there is nothing to register, and it costs nothing.

'''Out of the box:''' install [https://meshchatx.com MeshChatX] (Windows, macOS, Linux, Android), [https://github.com/markqvist/Sideband/releases Sideband] (Android, Windows, macOS, Linux) or an iPhone app, add a connection of type '''TCPClientInterface''' with host <code>rns.scotmesh.net</code> and port <code>4242</code>, and you are on. [[Connecting to ScotMesh#Out of the box: an app|Step by step]].

'''Full installation:''' add this to your Reticulum config:

<syntaxhighlight lang="text"> [[ScotMesh Backbone]]
type = TCPClientInterface
enabled = yes
target_host = rns.scotmesh.net
target_port = 4242</syntaxhighlight>

'''Behind CGNAT or a firewall you do not control?''' Use the I2P entry point instead; no port needs forwarding at either end. See [[Access over I2P]].

'''Got a LoRa radio?''' ScotMesh's first gateway is on air in Fife, carrying both profiles below and linked to the backbone, and standalone [[ScotMesh firmware|solar nodes]] are going out. Coverage is small so far, so a radio built anywhere in Scotland will hear the others as they arrive. Every radio must match all five settings exactly: a board with a different spreading factor is not weakly connected, it is completely deaf, and nothing reports an error. The 868 profile moved from 867.5 to 869.4625 MHz on 11 September 2026 (Ofcom's 869.40–869.65 MHz sub-band), so retune any radio still on the old frequency. [https://rnode.scotmesh.net rnode.scotmesh.net] applies either profile in one click.

{| class="wikitable"
|-
!
! ScotMesh 433
! ScotMesh 868
|-
| Frequency
| 433.775 MHz
| 869.4625 MHz
|-
| Bandwidth
| 125 kHz
| 125 kHz
|-
| Spreading factor
| 8
| 9
|-
| Coding rate
| 4/5
| 4/5
|-
| TX power
| 7 dBm
| 22 dBm
|}

Whichever way in you chose: restart Reticulum, then check the interface shows '''Up''' (in <code>rnstatus</code>, or on the app's interfaces page). If it does not, [[Troubleshooting]] 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]]; [[Services and addresses]] has them all in one place.

{| class="wikitable"
|-
! Service
! Address
! Use it with
|-
| TCP entry point
| <code>rns.scotmesh.net:4242</code>
| Any Reticulum client
|-
| I2P entry point
| <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code>
| Any Reticulum client, via i2pd
|-
| [[The chat room|Chat hub]] (RRC), room <code>scotmesh</code>
| <code>004e5a15da221d9a236b0e8d74195f13</code>
| MeshChatX, <code>rrc</code> clients
|-
| [[Propagation node|LXMF propagation node]]
| <code>c283b754e0acc11ce48d2f5e29167e0c</code>
| Sideband, MeshChatX, Nomad Network
|-
| [[Nomad Network|Nomad Network node]]
| <code>10a839df2c50635bcb0c8a299b9ca0f8</code>
| Nomad Network, MeshChatX
|-
| Transport instance
| <code>20b962cd814444f7812e409e7c47f319</code>
| Shows up in <code>rnpath</code> and node maps
|}

The node peers outward to <code>rebelnet.uk</code>, <code>rns.cybercore.uk</code> and <code>rmap.world</code>, so a client connected here can reach the rest of the public Reticulum network. See [[Who we peer with]].

== Where the network is ==

Where things actually are, rather than where we would like them to be. Updated by hand as things land.

{| class="wikitable"
|-
!
! Milestone
! Notes
|-
| ✔
| '''Reticulum backbone online'''
| Public transport node at <code>rns.scotmesh.net:4242</code>, peered into the wider network.
|-
| ✔
| '''Reachable over I2P'''
| No port forwarding needed at either end.
|-
| ✔
| '''Chat hub running'''
| RRC hub with the <code>scotmesh</code> room.
|-
| ✔
| '''Propagation node running'''
| Offline message delivery for the region.
|-
| ✔
| '''Web flasher for RNodes and nodes'''
| [https://rnode.scotmesh.net rnode.scotmesh.net], with both ScotMesh profiles built in.
|-
| ✔
| '''LoRa gateway on air'''
| First gateway in Fife, both profiles, linked to the backbone.
|-
| ✔
| '''Standalone solar nodes'''
| [[ScotMesh firmware]]: managed and updated over the mesh. First units on the bench and going out.
|-
| ✘
| '''Coverage beyond Fife'''
| Needs gateways and relays elsewhere. [[Running your own transport node|Put one up]] and tell us.
|}

== Find your way ==

{| class="wikitable"
|-
| '''I have never used Reticulum'''
| Read in order: [[What Reticulum is|what Reticulum is]] → [[How it compares|how it compares]] to Meshtastic, MeshCore and LoRaWAN → [[Connecting to ScotMesh|connecting to ScotMesh]] → [[Choosing a client|choosing a client]] → [[First steps|first steps]].
|-
| '''I am connected. What can I do?'''
| Join [[The chat room|the chat room]], send messages that arrive even when the other person is offline via the [[Propagation node|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; [[ScotMesh firmware]] for a solar relay you can look after from home; [[Antennas and siting|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|known bugs and workarounds]].
|-
| '''What is ScotMesh building?'''
| The [[Project index|project index]]: the [[ScotMesh firmware]], the flasher, and [[MeshCore as a Reticulum Interface|MeshCore as a Reticulum interface]].
|-
| '''I want to read and watch more'''
| [[Learning resources]]: the manual, talks, the community wiki, and where people talk.
|-
| '''What does that word mean?'''
| The [[Glossary|glossary]].
|}

== Say hello ==

ScotMesh is a community, not a company. Most of us are on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord], the quickest place to ask anything, Reticulum or not, and there is also the [https://scotmesh.uk forum at scotmesh.uk]; [[The chat room|the chat room]] is where to find us on the network itself; and [[About ScotMesh]] says who we are and what we run. If a page here is wrong or unclear, say so, or fix it: [[ScotMesh Wiki:About|anyone can ask for an editing account]].

Connecting to ScotMesh

2026-09-11T19:27:58Z

ScotMesh: ScotMesh 868 moves to 869.4625 MHz (Ofcom 869.40-869.65 MHz sub-band)

This page assumes you know nothing. If you have never heard of Reticulum, start with [[What Reticulum is|what Reticulum is]] and come back.

== What you need ==

* '''A computer or a phone.''' Windows, macOS, Linux or Android all work.
* '''An internet connection''' — home broadband, wifi or mobile data. Any of them.
* '''No radio, no hardware, no money.''' You do not need a LoRa device to join. That comes later if you want it.
* '''No account.''' There is nothing to sign up for, nobody to ask, and no approval step. This is not politeness — the network has no mechanism for registration.

== What you are actually doing ==

Reticulum is a piece of software that runs on your machine. On its own it can only talk to things on your local network, which is probably nothing.

ScotMesh runs a machine that is permanently online and connected onward to the wider Reticulum network. '''Connecting means telling your Reticulum where to find ours''' — one small block of configuration giving it a hostname and a port. After that your machine can reach everything our machine can reach.

The thing you add is called an '''interface'''. An interface is simply a way of reaching other Reticulum machines: over the internet, over a radio, over a cable. You can have several at once, and Reticulum will use whichever is working.

== Two ways to do this ==

{| class="wikitable"
|-
!
! Use this if
|-
| '''[[#Out of the box: an app|Out of the box: an app]]'''
| You want it working in five minutes and never want to see a config file. Recommended.
|-
| '''[[#Full installation: Reticulum yourself|Full installation]]'''
| You want to run it on a server, a Raspberry Pi, or anything without a screen; or you simply prefer to understand what you are running.
|}

Both end up in the same place. The app does the same thing as the full installation, with the config file hidden from you.

-----

== Out of the box: an app ==

These apps have Reticulum built in. You install one like any other program, tell it where ScotMesh is, and you are connected; there is no config file to see. Pick by what you have:

{| class="wikitable"
! App !! Runs on !! Get it
|-
| '''MeshChatX''' || Windows, macOS, Linux, Android || [https://meshchatx.com meshchatx.com]
|-
| '''Sideband''' || Android, Windows, macOS, Linux || [https://github.com/markqvist/Sideband/releases GitHub releases]
|-
| '''Retichat''' or '''Columba''' || iPhone || [https://apps.apple.com/us/app/retichat/id6762225314 App Store], [https://github.com/torlando-tech/Columba-iOS GitHub]
|}

=== MeshChatX (recommended) ===

[https://meshchatx.com MeshChatX] does messaging, files, voice calls, chat rooms and Nomad Network pages, and runs on everything but iPhone. If in doubt, use this.

==== 1. Download it ====

Go to the [https://github.com/Quad4-Software/MeshChatX/releases releases page] and pick the file for your system:

{| class="wikitable"
|-
! System
! File to download
|-
| Windows
| the <code>win-installer.exe</code>
|-
| macOS, Apple Silicon (M1 and later)
| the <code>mac-arm64.dmg</code>
|-
| macOS, Intel
| the <code>mac-x64.dmg</code>
|-
| Linux
| the <code>.deb</code> on Debian or Ubuntu, otherwise the <code>.AppImage</code>
|-
| Android
| the <code>android-universal.apk</code>
|}

==== 2. Install and open it ====

Normal installation. On Android you will need to allow installing from outside the Play Store. On macOS you may need to right-click the app and choose Open the first time, because it is not from the App Store.

==== 3. Add ScotMesh ====

# Open the '''Interfaces''' page.
# Click '''Add Interface'''.
# For the type, choose '''TCPClientInterface'''. (“TCP client” just means it reaches out over the internet to a machine that is listening.)
# '''Target Host''': <code>rns.scotmesh.net</code>
# '''Target Port''': <code>4242</code>
# Save. Restart the app when it asks.

Within a few seconds the interface should show as connected. Skip to [[#Did it work?|did it work]].

=== Sideband ===

[https://github.com/markqvist/Sideband Sideband] is a messaging client by Reticulum's author; best on Android, especially with an [[RNode]] paired over Bluetooth.

# Install it from the [https://github.com/markqvist/Sideband/releases releases page] (an <code>.apk</code> for Android; packages for Windows, macOS and Linux).
# Open '''Settings''', then '''Connectivity'''.
# Turn on '''Connect via TCP''' and enter host <code>rns.scotmesh.net</code>, port <code>4242</code>.
# Go back; Sideband reconnects by itself. Your address and an announce button are on the main screen.

=== iPhone ===

Reticulum on iPhone is newer than on the other platforms. [https://apps.apple.com/us/app/retichat/id6762225314 Retichat] is on the App Store and [https://github.com/torlando-tech/Columba-iOS Columba] is on GitHub; both are messaging clients. In either, add a connection of type TCP with host <code>rns.scotmesh.net</code> and port <code>4242</code>. We have not used them ourselves yet; if you do, tell us how it went.

-----

== Full installation: Reticulum yourself ==

=== 1. Install it ===

Reticulum is a Python program. If you have Python and <code>pip</code>, this is one command in a terminal:

<syntaxhighlight lang="text">pip install rns</syntaxhighlight>
'''On Ubuntu 24.04 and other recent Linux systems''' that command will refuse, with a message about an “externally managed environment”. This is deliberate on their part, not an error you caused. Use a virtual environment instead:

<syntaxhighlight lang="text">sudo apt install python3-venv
python3 -m venv ~/reticulum
~/reticulum/bin/pip install rns</syntaxhighlight>
Your commands then become <code>~/reticulum/bin/rnsd</code> and <code>~/reticulum/bin/rnstatus</code> instead of plain <code>rnsd</code> and <code>rnstatus</code>.

'''On Android or iPhone''', do not do this — install one of the apps above instead. Running Reticulum by hand on Android needs Termux and is a lot of work for no gain.

=== 2. Run it once, to create the config file ===

'''The config file does not exist yet.''' This trips people up: guides tell you to edit it, and you go looking, and there is nothing there. Reticulum writes it the first time it starts.

<syntaxhighlight lang="text">rnsd</syntaxhighlight>
It will print a few lines and keep running. Leave it a few seconds, then stop it with '''Ctrl+C'''. It has now created a config file and a couple of folders.

=== 3. Find the config file ===

{| class="wikitable"
|-
! System
! Where it is
|-
| Linux, macOS
| <code>~/.reticulum/config</code>
|-
| Windows
| <code>C:\Users\<you>\.reticulum\config</code>
|}

The folder starts with a dot, which means it is hidden. On Linux and macOS use <code>ls -a</code> to see it, or just open the path directly. On Windows, paste the path into Explorer's address bar.

It is a plain text file with no extension. Open it with any text editor — <code>nano ~/.reticulum/config</code> on Linux, TextEdit on macOS, Notepad on Windows.

=== 4. Look at what is already there ===

Near the bottom you will find a section that looks like this:

<syntaxhighlight lang="text">[interfaces]

[[Default Interface]]
type = AutoInterface
enabled = Yes</syntaxhighlight>
That is one interface already configured. <code>AutoInterface</code> finds other Reticulum machines on your own local network, which is useful but probably finds nothing today.

'''Note the indentation.''' <code>[interfaces]</code> is at the left margin, <code><nowiki>[[Default Interface]]</nowiki></code> is indented two spaces, and its settings are indented four. This matters — the file will not load correctly if you get it wrong, and Reticulum will silently ignore the interface.

=== 5. Add ScotMesh ===

Underneath the existing interface, still inside <code>[interfaces]</code>, add:

<syntaxhighlight lang="text"> [[ScotMesh Backbone]]
type = TCPClientInterface
enabled = yes
target_host = rns.scotmesh.net
target_port = 4242</syntaxhighlight>
So the whole section now reads:

<syntaxhighlight lang="text">[interfaces]

[[Default Interface]]
type = AutoInterface
enabled = Yes

[[ScotMesh Backbone]]
type = TCPClientInterface
enabled = yes
target_host = rns.scotmesh.net
target_port = 4242</syntaxhighlight>
The name in double brackets is yours to choose — it is only a label. Save the file.

=== 6. Start it again ===

<syntaxhighlight lang="text">rnsd</syntaxhighlight>
Leave this running. Reticulum only works while it is running — close the terminal and you are off the network. See [[#Keeping it running|keeping it running]] for how to make it start by itself.

-----

== Did it work? ==

Open a ''second'' terminal, leaving <code>rnsd</code> running in the first, and run:

<syntaxhighlight lang="text">rnstatus</syntaxhighlight>
You are looking for something like:

<syntaxhighlight lang="text">TCPInterface[ScotMesh Backbone/rns.scotmesh.net:4242]
Status : Up
Traffic : ↑1.2 KB ↓14.8 KB</syntaxhighlight>
'''Status: Up''' means connected. Traffic counters climbing means the network is talking to you. If it says Down, see below.

To confirm you can actually reach something, ask for a path to our chat hub:

<syntaxhighlight lang="text">rnpath -t 004e5a15da221d9a236b0e8d74195f13</syntaxhighlight>
A reply mentioning a number of hops means you are properly on the network. That long string is a '''destination hash''' — Reticulum's equivalent of an address, except it is derived from a cryptographic key rather than handed out by anybody.

== Now what? ==

Being connected is not obviously exciting on its own. Things you can now do:

* '''Join the chat room.''' Our hub hosts a room called <code>scotmesh</code>. See [[The chat room|the chat room]].
* '''Message people.''' Install a client and you have an address others can reach. See [[Choosing a client|choosing a client]].
* '''Browse pages hosted inside the network.''' See [[Nomad Network]].
* '''Send and receive messages while offline''', via our [[Propagation node|propagation node]].

Give it a few minutes before judging it. Other nodes announce themselves periodically, so your view of the network fills in gradually rather than instantly.

== Keeping it running ==

On Linux, run it as a service so it survives a reboot:

<syntaxhighlight lang="text">sudo tee /etc/systemd/system/rnsd.service >/dev/null <<'EOF'
[Unit]
Description=Reticulum Network Stack Daemon
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=YOUR_USERNAME
ExecStart=/usr/local/bin/rnsd
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target
EOF

sudo systemctl daemon-reload
sudo systemctl enable --now rnsd</syntaxhighlight>
Replace <code>YOUR_USERNAME</code> with your own, and check the <code>ExecStart</code> path matches where <code>rnsd</code> actually is — <code>which rnsd</code> will tell you, and it will be different if you used a virtual environment.

On Windows and macOS, or if you used MeshChatX, just leave the application running.

-----

== Other ways in ==

Only read these if the ordinary route above does not suit you.

=== Behind CGNAT, or a firewall you do not control ===

Mobile networks, student halls and workplace wifi usually still allow outbound TCP, so try the normal route first. If it is blocked, I2P will almost certainly get through, because it needs no inbound connections at either end.

Install an I2P router first:

<syntaxhighlight lang="text">sudo apt install i2pd
sudo systemctl enable --now i2pd</syntaxhighlight>
Then add, alongside your other interfaces:

<syntaxhighlight lang="text"> [[ScotMesh I2P]]
type = I2PInterface
enabled = yes
peers = a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</syntaxhighlight>
'''Be patient.''' I2P builds tunnels before it can carry anything, which takes five to ten minutes on a fresh install. The interface showing Down for that long is expected, not broken. It is slower than TCP; that is the trade for getting through.

=== Over LoRa radio ===

ScotMesh's first LoRa gateway is on air in Fife; if you are within range of it, or of another ScotMesh relay, a radio with the right settings reaches the whole network with no internet at all. Coverage is small so far, so this section also covers using LoRa between your own machines.

You need an [[RNode]]: a supported LoRa board flashed with RNode firmware. It is not a Meshtastic or MeshCore radio, though a lot of the same hardware can be reflashed into one.

<syntaxhighlight lang="text"> [[RNode LoRa]]
type = RNodeInterface
enabled = yes
port = /dev/ttyUSB0
frequency = 869462500
bandwidth = 125000
txpower = 22
spreadingfactor = 9
codingrate = 5</syntaxhighlight>
Two things that catch everyone:

* '''Every radio must match exactly''' on frequency, bandwidth, spreading factor and coding rate. These are not negotiated. A radio with different settings is not “weakly connected” — it is completely deaf to you, with no error to tell you so. If two of your own radios cannot hear each other, check these four lines before anything else.
* '''Transmit time is legally limited''' in the licence-free bands, and it is easy to exceed. Set <code>airtime_limit_short</code> and <code>airtime_limit_long</code>. If you are a licensed amateur operating under your callsign, set <code>id_callsign</code> and <code>id_interval</code> too.

Higher spreading factors reach further and are dramatically slower — SF12 may carry a few hundred bits per second. Do not reach for it by default.

=== Another machine on your network already has Reticulum ===

Then you need no configuration at all. The <code>Default Interface</code> already in your config finds it automatically. This is the tidy way to share one radio: put the LoRa hardware on a Raspberry Pi, and everything else in the house reaches the mesh through it.

-----

== When it does not work ==

{| class="wikitable"
|-
! What you see
! What it usually means
|-
| No config file to edit
| You have not run <code>rnsd</code> yet. It creates the file on first start.
|-
| <code>rnsd: command not found</code>
| Installed into a virtual environment — use the full path, e.g. <code>~/reticulum/bin/rnsd</code>.
|-
| <code>error: externally-managed-environment</code>
| Expected on modern Linux. Use the virtual environment method above.
|-
| Interface missing from <code>rnstatus</code>
| Indentation is wrong, or it is outside the <code>[interfaces]</code> section.
|-
| Status: Down on the TCP interface
| No route out, or a typo in the hostname. Check with <code>ping rns.scotmesh.net</code>.
|-
| Status: Down on I2P, for ages
| Normal for the first five to ten minutes.
|-
| Up, but no traffic at all
| Fine for the first minute or two. Longer than that, something upstream is filtering.
|-
| No path to a destination
| Wait a couple of minutes. Nodes announce periodically and you cannot reach what has not announced.
|-
| A client hangs on “securing link”
| See [[Known bugs and workarounds|known bugs]] — this one has bitten us.
|-
| Two LoRa radios cannot hear each other
| Mismatched frequency, bandwidth, spreading factor or coding rate.
|}

== Going further: carry traffic for other people ==

Everything above makes you a '''client''': you use the network, but nothing routes through you. A '''transport node''' also relays other people's traffic and announces the paths it knows.

This is how the network stops depending on any one machine — including ours. If your computer is always on and has a decent connection, it is worth doing.

The switch itself is one line, in the <code>[reticulum]</code> section at the top of the config:

<syntaxhighlight lang="text">[reticulum]
enable_transport = Yes</syntaxhighlight>
Two things matter beyond that. Others must be able to '''reach''' you, which means either opening a port with a <code>TCPServerInterface</code> or using I2P if you cannot. And you must '''announce often enough to be found''' — the default is six hours, which in practice means nobody discovers you at all.

The full walkthrough is in [[Running your own transport node|running your own transport node]]. If you set one up, tell us and we will peer with you.

[[Category:Getting Started]]

The ScotMesh node

2026-09-11T15:55:30Z

ScotMesh: Chat hub now keeps 7 days of history

The '''ScotMesh node''' is a public Reticulum [[Glossary#Transport node|transport node]] for Scotland, reachable as <code>rns.scotmesh.net</code>. 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 <code>enable_transport</code> on, so anything connected to it can reach anything it can reach: other ScotMesh users, and through [[Who we peer with|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 <code>scotmesh</code> 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|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 (<code>rnsd</code>) shared by the chat hub (<code>[https://github.com/thatSFguy/reticulum-relay-chat rrc-hub]</code>), the propagation node (<code>lxmd</code>), the Nomad Network node and an I2P router (<code>i2pd</code>) for the [[Access over I2P|I2P entry point]].

Its live status, updated every two minutes from the daemon itself, is on [https://rns.scotmesh.net rns.scotmesh.net] and at the top of this wiki's [[Main Page|home page]].

== Ways in ==

{| class="wikitable"
! Way in !! Use it when !! Details
|-
| TCP, <code>rns.scotmesh.net</code> port 4242 || You have an ordinary internet connection || [[Connecting to ScotMesh]]
|-
| I2P || You are behind CGNAT or a firewall you do not control || [[Access over I2P]]
|-
| LoRa radio || You are within range of a ScotMesh gateway || [[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|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 [https://discord.gg/ytxfyuDmSt ScotMesh Discord] 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.

[[Category:The ScotMesh Backbone]]

The chat room

2026-09-11T15:55:29Z

ScotMesh: Chat hub now keeps 7 days of history and sends @mention notifications

ScotMesh runs a chat room called '''<code>scotmesh</code>''' on an '''RRC hub''' (Reticulum Relay Chat): rooms, nicknames, topics and operators, carried entirely over Reticulum. It is the place to say hello, ask for help, and find out who else is on.

{| class="wikitable"
! !! Value
|-
| Hub address || <code>004e5a15da221d9a236b0e8d74195f13</code>
|-
| Room || <code>scotmesh</code>
|}

== Out of the box ==

'''MeshChatX''' has chat built in. Once you are [[Connecting to ScotMesh|connected to ScotMesh]]:

# Open the chat section.
# The ScotMesh hub appears in the list of hubs once its hourly announce has reached you. If it is not there yet, add it by the address above.
# Join the room <code>scotmesh</code>.

Sideband and the iPhone apps are messaging clients and do not do rooms; use MeshChatX for chat, or one of the clients below.

== Full installation ==

With Reticulum installed yourself, any RRC client works: '''Ratspeak''', '''rrc-tui''', '''rrc-gui''', '''WeeChat''' (with the RRC plugin) and '''Eridanus'''. Point the client at the hub address, then:

<syntaxhighlight lang="text">/join scotmesh</syntaxhighlight>

The hub announces itself every hour, so a client that lists hubs will usually show it without the address being typed.

== What to expect ==

* '''Catching up.''' When you join you see the latest 25 messages, and <code>/history</code> shows up to 100 more. The hub keeps the room's messages for 7 days and then deletes them.
* '''@mentions reach you when you are away.''' Write <code>@nick</code> in the room and, if that person is offline, the hub sends them a short LXMF message (through our [[Propagation node|propagation node]] if need be) so they know to come and look. To do this it keeps a list of the identities it has met: public key, last nickname and when it last saw them.
* '''Nicknames''' are yours to choose, and once you have used one it belongs to your Reticulum identity, even while you are offline, so nobody else can take it and @mentions reach one person. If you ask for a name someone already has, you get it with a number on the end (<code>Alex1</code>). Each app or device has its own identity, so a phone and a laptop need different names.
* '''It can be quiet.''' Scotland is not a big place for Reticulum yet. If nobody answers, leave the window open, or ask on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord] instead.

== Operators ==

Room operators can set the topic and, if it ever comes to it, remove someone. Ask in the room or on the ScotMesh Discord if you would like operator rights for the <code>scotmesh</code> room; we are glad of the help.

== Your own rooms ==

Anyone connected can create a room on the hub with <code>/join</code> followed by a new name. Rooms exist while someone is in them.

== The wider community ==

The Reticulum community runs its own RRC hub at <code>28c7c1a68c735693aa8e6b8193ed44b2</code>; see [[Learning resources]] for that and the other places people talk.

[[Category:The ScotMesh Backbone]]

MediaWiki:Common.css

2026-09-11T15:39:20Z

ScotMesh: MeshCore emblem instead of wordmark

/* ScotMesh: status strip and wide screenshots */
.sm-status { margin: 0.5em 0 1em; }
.mw-parser-output .wikitable { font-size: 0.95em; }

/* Front page */
.sm-welcome { font-size: 1.08em; max-width: 72ch; margin-bottom: 1em; }
.sm-cards { display: flex; flex-wrap: wrap; gap: 1em; margin: 1em 0 1.5em; }
.sm-card { flex: 1 1 240px; padding: 0.2em 1.1em 0.6em; border: 1px solid var(--border-color-base, rgba(128,128,128,0.35)); border-radius: var(--border-radius-large, 10px); background: var(--color-surface-2, rgba(128,128,128,0.06)); }
.sm-card h3 { margin-top: 0.8em; border: 0; }
.sm-card .mw-headline { font-size: 1.05em; }

/* Front-page banner */
.sm-hero { position: relative; overflow: hidden; margin: 0.4em 0 1.4em; padding: 2.2em 2.2em 2em; border-radius: 16px;
background: linear-gradient(135deg, #0b2447 0%, #0a3a7a 55%, #005EB8 100%); color: #fff; }
.sm-hero::after { content: ""; position: absolute; inset: 0 0 0 38%; background: url("data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 viewBox=%220 0 520 300%22%3E%3Cline x1=%22375%22 y1=%2291%22 x2=%22448%22 y2=%2298%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22284%22 y1=%2228%22 x2=%22237%22 y2=%2294%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2272%22 y1=%2273%22 x2=%2240%22 y2=%2268%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22329%22 y1=%22114%22 x2=%22375%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2239%22 y1=%22152%22 x2=%2229%22 y2=%22131%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22350%22 y1=%22130%22 x2=%22392%22 y2=%22170%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2245%22 y1=%2235%22 x2=%2272%22 y2=%2273%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22407%22 y1=%22206%22 x2=%22358%22 y2=%22176%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22100%22 y1=%22173%22 x2=%22167%22 y2=%22174%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22100%22 y1=%22173%22 x2=%22132%22 y2=%22171%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2239%22 y1=%22152%22 x2=%2230%22 y2=%22197%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22100%22 y1=%22173%22 x2=%2230%22 y2=%22197%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2229%22 y1=%22131%22 x2=%2286%22 y2=%22147%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22299%22 y1=%22121%22 x2=%22237%22 y2=%2294%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22498%22 y1=%2223%22 x2=%22500%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22172%22 y1=%2252%22 x2=%22237%22 y2=%2294%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22335%22 y1=%2230%22 x2=%22329%22 y2=%22114%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22324%22 y1=%22275%22 x2=%22430%22 y2=%22275%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22299%22 y1=%22121%22 x2=%22300%22 y2=%22138%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22278%22 y1=%22112%22 x2=%22237%22 y2=%2294%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22498%22 y1=%2223%22 x2=%22448%22 y2=%2298%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22335%22 y1=%2230%22 x2=%22375%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22164%22 y1=%22239%22 x2=%22219%22 y2=%22222%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22222%22 y1=%22242%22 x2=%22273%22 y2=%22255%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22278%22 y1=%22112%22 x2=%22300%22 y2=%22138%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22329%22 y1=%22114%22 x2=%22300%22 y2=%22138%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22222%22 y1=%22242%22 x2=%22219%22 y2=%22222%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22350%22 y1=%22130%22 x2=%22358%22 y2=%22176%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22392%22 y1=%22170%22 x2=%22358%22 y2=%22176%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2229%22 y1=%22131%22 x2=%2240%22 y2=%2268%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22407%22 y1=%22206%22 x2=%22430%22 y2=%22275%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2245%22 y1=%2235%22 x2=%2282%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22172%22 y1=%2252%22 x2=%2272%22 y2=%2273%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22439%22 y1=%2291%22 x2=%22448%22 y2=%2298%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22498%22 y1=%2223%22 x2=%22439%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2239%22 y1=%22152%22 x2=%2286%22 y2=%22147%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22100%22 y1=%22173%22 x2=%2286%22 y2=%22147%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22324%22 y1=%22275%22 x2=%22273%22 y2=%22255%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22278%22 y1=%22112%22 x2=%22284%22 y2=%2228%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22164%22 y1=%22239%22 x2=%22167%22 y2=%22174%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22222%22 y1=%22242%22 x2=%22164%22 y2=%22239%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22439%22 y1=%2291%22 x2=%22500%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2272%22 y1=%2273%22 x2=%2282%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22500%22 y1=%2243%22 x2=%22448%22 y2=%2298%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22350%22 y1=%22130%22 x2=%22375%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2282%22 y1=%2243%22 x2=%2240%22 y2=%2268%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2239%22 y1=%22152%22 x2=%22100%22 y2=%22173%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22392%22 y1=%22170%22 x2=%22430%22 y2=%22275%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22132%22 y1=%22171%22 x2=%2286%22 y2=%22147%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22407%22 y1=%22206%22 x2=%22392%22 y2=%22170%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22273%22 y1=%22255%22 x2=%22219%22 y2=%22222%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2229%22 y1=%22131%22 x2=%2230%22 y2=%22197%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2245%22 y1=%2235%22 x2=%2240%22 y2=%2268%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22299%22 y1=%22121%22 x2=%22329%22 y2=%22114%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22172%22 y1=%2252%22 x2=%2282%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22278%22 y1=%22112%22 x2=%22299%22 y2=%22121%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22167%22 y1=%22174%22 x2=%22132%22 y2=%22171%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22335%22 y1=%2230%22 x2=%22284%22 y2=%2228%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22439%22 y1=%2291%22 x2=%22375%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22324%22 y1=%22275%22 x2=%22358%22 y2=%22176%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22329%22 y1=%22114%22 x2=%22350%22 y2=%22130%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Ccircle cx=%22172%22 cy=%2252%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22335%22 cy=%2230%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22278%22 cy=%22112%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%2239%22 cy=%22152%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%2229%22 cy=%22131%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%2245%22 cy=%2235%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22222%22 cy=%22242%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%2272%22 cy=%2273%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22324%22 cy=%22275%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22299%22 cy=%22121%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22498%22 cy=%2223%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22439%22 cy=%2291%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%2282%22 cy=%2243%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22164%22 cy=%22239%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22100%22 cy=%22173%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22329%22 cy=%22114%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22284%22 cy=%2228%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%2240%22 cy=%2268%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22350%22 cy=%22130%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22167%22 cy=%22174%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22237%22 cy=%2294%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22407%22 cy=%22206%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22132%22 cy=%22171%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22273%22 cy=%22255%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22375%22 cy=%2291%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22500%22 cy=%2243%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22219%22 cy=%22222%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%2286%22 cy=%22147%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%2230%22 cy=%22197%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22392%22 cy=%22170%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22448%22 cy=%2298%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22358%22 cy=%22176%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22300%22 cy=%22138%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22430%22 cy=%22275%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3C/svg%3E") right center / cover no-repeat; pointer-events: none; }
.sm-hero > * { position: relative; z-index: 1; }
.sm-hero-eyebrow { display: flex; align-items: center; gap: 0.55em; font-size: 0.8em; font-weight: 600; letter-spacing: 0.12em; text-transform: uppercase; color: #cfe3ff; }
.sm-hero-eyebrow .sm-saltire { display: inline-block; width: 1.9em; height: 1.15em; border-radius: 3px;
background: #005EB8 url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 60 36'%3E%3Cpath d='M0 0L60 36M60 0L0 36' stroke='%23fff' stroke-width='7'/%3E%3C/svg%3E") center / 100% 100%;
box-shadow: 0 0 0 1px rgba(255,255,255,.35); }
.sm-hero-title { font-size: 2.3em; font-weight: 750; line-height: 1.12; margin: 0.35em 0 0.3em; max-width: 16em; text-wrap: balance; color: #fff; }
.sm-hero-sub { font-size: 1.12em; line-height: 1.5; max-width: 34em; color: #e3ecfa; }
.sm-hero-actions { display: flex; flex-wrap: wrap; gap: 0.7em; margin-top: 1.4em; }
.sm-btn a { display: inline-block; padding: 0.62em 1.15em; border-radius: 999px; font-weight: 650; text-decoration: none !important; }
.sm-btn-primary a { background: #fff; color: #0a3a7a !important; }
.sm-btn-primary a:hover { background: #e6f0ff; }
.sm-btn-secondary a { color: #fff !important; box-shadow: inset 0 0 0 1.5px rgba(255,255,255,.7); }
.sm-btn-secondary a:hover { background: rgba(255,255,255,.12); }
.sm-btn a:focus-visible { outline: 2px solid #fff; outline-offset: 2px; }
.sm-hero-facts { display: flex; flex-wrap: wrap; gap: 0.4em 1.4em; margin-top: 1.5em; font-size: 0.9em; color: #cfe3ff; }
.sm-hero-facts span::before { content: "✓ "; color: #8fd19e; font-weight: 700; }
@media (max-width: 640px) {
.sm-hero { padding: 1.5em 1.3em 1.4em; }
.sm-hero::after { inset: 45% 0 0 0; opacity: .6; }
.sm-hero-title { font-size: 1.75em; }
}

/* Site header on every page: the Saltire and the wiki's name, as on scotmesh.net */
#siteNotice { background: none !important; border: 0 !important; padding: 0 !important; margin: 0 0 0.6em !important; text-align: left !important; font-size: 1rem !important; }
.sm-header { display: flex; align-items: center; gap: 1rem; padding: 0.9rem 32px 0.9rem; }
.sm-header a { text-decoration: none !important; }
.sm-flag { display: block; width: 80px; height: 48px; border-radius: 5px; flex: none; background: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 60 36'%3E%3Crect width='60' height='36' fill='%230065bd'/%3E%3Cpath d='M0 0L60 36M60 0L0 36' stroke='white' stroke-width='6'/%3E%3C/svg%3E") center / 100% 100% no-repeat; box-shadow: 0 1px 3px rgba(0,0,0,.35); }
.sm-header-title { font-size: 1.75em; font-weight: 750; line-height: 1.15; }
.sm-header-title a { color: var(--color-emphasized, inherit) !important; }
.sm-header-sub { color: var(--color-subtle, #9ca3af); font-size: 0.98em; margin-top: 0.15em; }
@media (max-width: 640px) { .sm-header { padding: 0.8rem 16px; gap: 0.75rem; } .sm-flag { width: 60px; height: 36px; } .sm-header-title { font-size: 1.35em; } .sm-header-sub { font-size: 0.88em; } }
/* Pointer to the MeshCore / Meshtastic wiki (Main Page, above the hero) */
.sm-otherwiki { margin: 0.2em 0 1em; padding: 0.6em 1em; border: 1px solid #166534; border-radius: 10px; background: #15803d; color: #fff; font-size: 0.95em; display: flex; align-items: center; gap: 0.5em 0.85em; flex-wrap: wrap; line-height: 1.45; overflow-wrap: anywhere; box-shadow: 0 1px 2px rgba(0,0,0,.15); }
.sm-otherwiki b { color: #fff; }
.sm-otherwiki a, .sm-otherwiki a.external, .sm-otherwiki a:visited { color: #fff !important; font-weight: 700; white-space: nowrap; text-decoration: underline; text-underline-offset: 2px; background-image: none; padding-right: 0; }
.sm-otherwiki a:hover, .sm-otherwiki a:focus-visible { color: #dcfce7 !important; }
.sm-ow-logos { display: inline-flex; align-items: center; gap: 0.6em; flex: none; padding: 0.3em 0.65em; border-radius: 7px; background: #166534; }
.sm-ow-logo { display: block; background: center / contain no-repeat; }
.sm-ow-mt { width: 26px; height: 14px; background-image: url("data:image/svg+xml,%3Csvg viewBox=%220 0 100 55%22 xmlns=%22http://www.w3.org/2000/svg%22 style=%22fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;%22%3E%3Cg transform=%22matrix(0.802386,0,0,0.460028,-421.748,-122.127)%22%3E%3Cg transform=%22matrix(0.579082,0,0,1.01004,460.975,-39.6867)%22%3E%3Cpath d=%22M250.908,330.267L193.126,415.005L180.938,406.694L244.802,313.037C246.174,311.024 248.453,309.819 250.889,309.816C253.326,309.814 255.606,311.015 256.982,313.026L320.994,406.536L308.821,414.869L250.908,330.267Z%22 style=%22fill:white;%22/%3E%3C/g%3E%3Cg transform=%22matrix(0.582378,0,0,1.01579,485.019,-211.182)%22%3E%3Cpath d=%22M87.642,581.398L154.757,482.977L142.638,474.713L75.523,573.134L87.642,581.398Z%22 style=%22fill:white;%22/%3E%3C/g%3E%3C/g%3E%3C/svg%3E"); }
.sm-ow-mc { width: 19px; height: 16px; background-image: url("data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 viewBox=%22-250 -205 500 410%22%3E%3Ccircle r=%2250%22 fill=%22white%22/%3E%3Cpath d=%22M63.6 -101.8A120 120 0 0 1 63.6 101.8M-63.6 -101.8A120 120 0 0 0 -63.6 101.8%22 fill=%22none%22 stroke=%22white%22 stroke-width=%2244%22/%3E%3Cpath d=%22M136.7 -174.9A222 222 0 0 1 136.7 174.9M-136.7 -174.9A222 222 0 0 0 -136.7 174.9%22 fill=%22none%22 stroke=%22white%22 stroke-width=%2252%22/%3E%3C/svg%3E"); }
.sm-ow-text { flex: 1 1 16em; min-width: 0; }
.sm-otherwiki + .sm-hero { margin-top: 0; }
@media (max-width: 640px) { .sm-otherwiki { font-size: 0.9em; padding: 0.5em 0.8em; } }

Main Page

2026-09-11T15:34:34Z

ScotMesh: MeshCore and Meshtastic logos on the other-wiki line

{{DISPLAYTITLE:ScotMesh Reticulum Wiki}}
<div class="sm-otherwiki"><span class="sm-ow-logos"><span class="sm-ow-logo sm-ow-mt" title="Meshtastic"></span><span class="sm-ow-logo sm-ow-mc" title="MeshCore"></span></span><span class="sm-ow-text">Looking for <b>MeshCore</b> or <b>Meshtastic</b>? They have their own wiki at [https://wiki.scotmesh.uk wiki.scotmesh.uk] →</span></div>
<div class="sm-hero">
<div class="sm-hero-title">A free, encrypted network for Scotland that anyone can join.</div>
<div class="sm-hero-sub">Reticulum carries messages, chat, files and pages over the internet and over LoRa radio, and keeps working when the things underneath it do not. Connecting takes about five minutes.</div>
<div class="sm-hero-actions"><span class="sm-btn sm-btn-primary">[[Connecting to ScotMesh|Connect in five minutes →]]</span><span class="sm-btn sm-btn-secondary">[[What Reticulum is|What is Reticulum?]]</span></div>
<div class="sm-hero-facts"><span>No sign-up</span><span>No hardware needed</span><span>Free, run by the community</span><span>Encrypted end to end</span></div>
</div>

<div class="sm-welcome">
'''Welcome.''' ScotMesh runs the Reticulum backbone for Scotland and writes this wiki; you are very welcome to use both, and to add to either. Whether you have never heard of Reticulum or you want to put a solar relay on a hill, there is a page here for you. Pick where you are:
</div>

<div class="sm-cards">
<div class="sm-card">
=== I just want to try it ===
Install one app, type in one address, and you are on the network with everyone else: messaging, chat, files and pages.

'''[[Connecting to ScotMesh|Connect in five minutes →]]'''

Then [[First steps]]: say hello in the chat room and send your first message.
</div>
<div class="sm-card">
=== I want to understand it first ===
No addresses to configure, no accounts, no company in the middle. Reticulum is unusual, and it is worth knowing why.

'''[[What Reticulum is|What Reticulum is →]]'''

Then [[How Reticulum works]], [[How it compares]] with Meshtastic and MeshCore, and the [[Glossary]].
</div>
<div class="sm-card">
=== I want to put a radio on air ===
A LoRa board becomes a Reticulum radio for your laptop or phone, or a self-contained relay you can look after from home.

'''[[RNode|Flash a board →]]'''

Then [[ScotMesh firmware]] for solar and hilltop relays, and [[Antennas and siting]] for making it reach.
</div>
</div>

== The backbone right now ==

Live from the node itself, the same feed as [https://rns.scotmesh.net rns.scotmesh.net], refreshed every two minutes. If the strip is blank or says unknown, treat the backbone as unconfirmed and check the node page directly.

<div id="sm-status" class="sm-status">Live backbone status: [https://rns.scotmesh.net/status.html rns.scotmesh.net/status]</div>

== Connect now ==

The backbone is a public Reticulum transport node in Dalgety Bay, Fife. Anyone may connect, there is nothing to register, and it costs nothing.

'''Out of the box:''' install [https://meshchatx.com MeshChatX] (Windows, macOS, Linux, Android), [https://github.com/markqvist/Sideband/releases Sideband] (Android, Windows, macOS, Linux) or an iPhone app, add a connection of type '''TCPClientInterface''' with host <code>rns.scotmesh.net</code> and port <code>4242</code>, and you are on. [[Connecting to ScotMesh#Out of the box: an app|Step by step]].

'''Full installation:''' add this to your Reticulum config:

<syntaxhighlight lang="text"> [[ScotMesh Backbone]]
type = TCPClientInterface
enabled = yes
target_host = rns.scotmesh.net
target_port = 4242</syntaxhighlight>

'''Behind CGNAT or a firewall you do not control?''' Use the I2P entry point instead; no port needs forwarding at either end. See [[Access over I2P]].

'''Got a LoRa radio?''' ScotMesh's first gateway is on air in Fife, carrying both profiles below and linked to the backbone, and standalone [[ScotMesh firmware|solar nodes]] are going out. Coverage is small so far, so a radio built anywhere in Scotland will hear the others as they arrive. Every radio must match all five settings exactly: a board with a different spreading factor is not weakly connected, it is completely deaf, and nothing reports an error. [https://rnode.scotmesh.net rnode.scotmesh.net] applies either profile in one click.

{| class="wikitable"
|-
!
! 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
|}

Whichever way in you chose: restart Reticulum, then check the interface shows '''Up''' (in <code>rnstatus</code>, or on the app's interfaces page). If it does not, [[Troubleshooting]] 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]]; [[Services and addresses]] has them all in one place.

{| class="wikitable"
|-
! Service
! Address
! Use it with
|-
| TCP entry point
| <code>rns.scotmesh.net:4242</code>
| Any Reticulum client
|-
| I2P entry point
| <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code>
| Any Reticulum client, via i2pd
|-
| [[The chat room|Chat hub]] (RRC), room <code>scotmesh</code>
| <code>004e5a15da221d9a236b0e8d74195f13</code>
| MeshChatX, <code>rrc</code> clients
|-
| [[Propagation node|LXMF propagation node]]
| <code>c283b754e0acc11ce48d2f5e29167e0c</code>
| Sideband, MeshChatX, Nomad Network
|-
| [[Nomad Network|Nomad Network node]]
| <code>10a839df2c50635bcb0c8a299b9ca0f8</code>
| Nomad Network, MeshChatX
|-
| Transport instance
| <code>20b962cd814444f7812e409e7c47f319</code>
| Shows up in <code>rnpath</code> and node maps
|}

The node peers outward to <code>rebelnet.uk</code>, <code>rns.cybercore.uk</code> and <code>rmap.world</code>, so a client connected here can reach the rest of the public Reticulum network. See [[Who we peer with]].

== Where the network is ==

Where things actually are, rather than where we would like them to be. Updated by hand as things land.

{| class="wikitable"
|-
!
! Milestone
! Notes
|-
| ✔
| '''Reticulum backbone online'''
| Public transport node at <code>rns.scotmesh.net:4242</code>, peered into the wider network.
|-
| ✔
| '''Reachable over I2P'''
| No port forwarding needed at either end.
|-
| ✔
| '''Chat hub running'''
| RRC hub with the <code>scotmesh</code> room.
|-
| ✔
| '''Propagation node running'''
| Offline message delivery for the region.
|-
| ✔
| '''Web flasher for RNodes and nodes'''
| [https://rnode.scotmesh.net rnode.scotmesh.net], with both ScotMesh profiles built in.
|-
| ✔
| '''LoRa gateway on air'''
| First gateway in Fife, both profiles, linked to the backbone.
|-
| ✔
| '''Standalone solar nodes'''
| [[ScotMesh firmware]]: managed and updated over the mesh. First units on the bench and going out.
|-
| ✘
| '''Coverage beyond Fife'''
| Needs gateways and relays elsewhere. [[Running your own transport node|Put one up]] and tell us.
|}

== Find your way ==

{| class="wikitable"
|-
| '''I have never used Reticulum'''
| Read in order: [[What Reticulum is|what Reticulum is]] → [[How it compares|how it compares]] to Meshtastic, MeshCore and LoRaWAN → [[Connecting to ScotMesh|connecting to ScotMesh]] → [[Choosing a client|choosing a client]] → [[First steps|first steps]].
|-
| '''I am connected. What can I do?'''
| Join [[The chat room|the chat room]], send messages that arrive even when the other person is offline via the [[Propagation node|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; [[ScotMesh firmware]] for a solar relay you can look after from home; [[Antennas and siting|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|known bugs and workarounds]].
|-
| '''What is ScotMesh building?'''
| The [[Project index|project index]]: the [[ScotMesh firmware]], the flasher, and [[MeshCore as a Reticulum Interface|MeshCore as a Reticulum interface]].
|-
| '''I want to read and watch more'''
| [[Learning resources]]: the manual, talks, the community wiki, and where people talk.
|-
| '''What does that word mean?'''
| The [[Glossary|glossary]].
|}

== Say hello ==

ScotMesh is a community, not a company. Most of us are on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord], the quickest place to ask anything, Reticulum or not, and there is also the [https://scotmesh.uk forum at scotmesh.uk]; [[The chat room|the chat room]] is where to find us on the network itself; and [[About ScotMesh]] says who we are and what we run. If a page here is wrong or unclear, say so, or fix it: [[ScotMesh Wiki:About|anyone can ask for an editing account]].

MediaWiki:Common.css

2026-09-11T15:34:33Z

ScotMesh: Other-wiki line: MeshCore and Meshtastic logos

/* ScotMesh: status strip and wide screenshots */
.sm-status { margin: 0.5em 0 1em; }
.mw-parser-output .wikitable { font-size: 0.95em; }

/* Front page */
.sm-welcome { font-size: 1.08em; max-width: 72ch; margin-bottom: 1em; }
.sm-cards { display: flex; flex-wrap: wrap; gap: 1em; margin: 1em 0 1.5em; }
.sm-card { flex: 1 1 240px; padding: 0.2em 1.1em 0.6em; border: 1px solid var(--border-color-base, rgba(128,128,128,0.35)); border-radius: var(--border-radius-large, 10px); background: var(--color-surface-2, rgba(128,128,128,0.06)); }
.sm-card h3 { margin-top: 0.8em; border: 0; }
.sm-card .mw-headline { font-size: 1.05em; }

/* Front-page banner */
.sm-hero { position: relative; overflow: hidden; margin: 0.4em 0 1.4em; padding: 2.2em 2.2em 2em; border-radius: 16px;
background: linear-gradient(135deg, #0b2447 0%, #0a3a7a 55%, #005EB8 100%); color: #fff; }
.sm-hero::after { content: ""; position: absolute; inset: 0 0 0 38%; background: url("data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 viewBox=%220 0 520 300%22%3E%3Cline x1=%22375%22 y1=%2291%22 x2=%22448%22 y2=%2298%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22284%22 y1=%2228%22 x2=%22237%22 y2=%2294%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2272%22 y1=%2273%22 x2=%2240%22 y2=%2268%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22329%22 y1=%22114%22 x2=%22375%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2239%22 y1=%22152%22 x2=%2229%22 y2=%22131%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22350%22 y1=%22130%22 x2=%22392%22 y2=%22170%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2245%22 y1=%2235%22 x2=%2272%22 y2=%2273%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22407%22 y1=%22206%22 x2=%22358%22 y2=%22176%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22100%22 y1=%22173%22 x2=%22167%22 y2=%22174%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22100%22 y1=%22173%22 x2=%22132%22 y2=%22171%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2239%22 y1=%22152%22 x2=%2230%22 y2=%22197%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22100%22 y1=%22173%22 x2=%2230%22 y2=%22197%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2229%22 y1=%22131%22 x2=%2286%22 y2=%22147%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22299%22 y1=%22121%22 x2=%22237%22 y2=%2294%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22498%22 y1=%2223%22 x2=%22500%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22172%22 y1=%2252%22 x2=%22237%22 y2=%2294%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22335%22 y1=%2230%22 x2=%22329%22 y2=%22114%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22324%22 y1=%22275%22 x2=%22430%22 y2=%22275%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22299%22 y1=%22121%22 x2=%22300%22 y2=%22138%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22278%22 y1=%22112%22 x2=%22237%22 y2=%2294%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22498%22 y1=%2223%22 x2=%22448%22 y2=%2298%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22335%22 y1=%2230%22 x2=%22375%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22164%22 y1=%22239%22 x2=%22219%22 y2=%22222%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22222%22 y1=%22242%22 x2=%22273%22 y2=%22255%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22278%22 y1=%22112%22 x2=%22300%22 y2=%22138%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22329%22 y1=%22114%22 x2=%22300%22 y2=%22138%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22222%22 y1=%22242%22 x2=%22219%22 y2=%22222%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22350%22 y1=%22130%22 x2=%22358%22 y2=%22176%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22392%22 y1=%22170%22 x2=%22358%22 y2=%22176%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2229%22 y1=%22131%22 x2=%2240%22 y2=%2268%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22407%22 y1=%22206%22 x2=%22430%22 y2=%22275%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2245%22 y1=%2235%22 x2=%2282%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22172%22 y1=%2252%22 x2=%2272%22 y2=%2273%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22439%22 y1=%2291%22 x2=%22448%22 y2=%2298%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22498%22 y1=%2223%22 x2=%22439%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2239%22 y1=%22152%22 x2=%2286%22 y2=%22147%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22100%22 y1=%22173%22 x2=%2286%22 y2=%22147%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22324%22 y1=%22275%22 x2=%22273%22 y2=%22255%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22278%22 y1=%22112%22 x2=%22284%22 y2=%2228%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22164%22 y1=%22239%22 x2=%22167%22 y2=%22174%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22222%22 y1=%22242%22 x2=%22164%22 y2=%22239%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22439%22 y1=%2291%22 x2=%22500%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2272%22 y1=%2273%22 x2=%2282%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22500%22 y1=%2243%22 x2=%22448%22 y2=%2298%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22350%22 y1=%22130%22 x2=%22375%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2282%22 y1=%2243%22 x2=%2240%22 y2=%2268%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2239%22 y1=%22152%22 x2=%22100%22 y2=%22173%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22392%22 y1=%22170%22 x2=%22430%22 y2=%22275%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22132%22 y1=%22171%22 x2=%2286%22 y2=%22147%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22407%22 y1=%22206%22 x2=%22392%22 y2=%22170%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22273%22 y1=%22255%22 x2=%22219%22 y2=%22222%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2229%22 y1=%22131%22 x2=%2230%22 y2=%22197%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%2245%22 y1=%2235%22 x2=%2240%22 y2=%2268%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22299%22 y1=%22121%22 x2=%22329%22 y2=%22114%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22172%22 y1=%2252%22 x2=%2282%22 y2=%2243%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22278%22 y1=%22112%22 x2=%22299%22 y2=%22121%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22167%22 y1=%22174%22 x2=%22132%22 y2=%22171%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22335%22 y1=%2230%22 x2=%22284%22 y2=%2228%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22439%22 y1=%2291%22 x2=%22375%22 y2=%2291%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22324%22 y1=%22275%22 x2=%22358%22 y2=%22176%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Cline x1=%22329%22 y1=%22114%22 x2=%22350%22 y2=%22130%22 stroke=%22white%22 stroke-opacity=%22.16%22 stroke-width=%221.2%22/%3E%3Ccircle cx=%22172%22 cy=%2252%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22335%22 cy=%2230%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22278%22 cy=%22112%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%2239%22 cy=%22152%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%2229%22 cy=%22131%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%2245%22 cy=%2235%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22222%22 cy=%22242%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%2272%22 cy=%2273%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22324%22 cy=%22275%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22299%22 cy=%22121%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22498%22 cy=%2223%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22439%22 cy=%2291%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%2282%22 cy=%2243%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22164%22 cy=%22239%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22100%22 cy=%22173%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22329%22 cy=%22114%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22284%22 cy=%2228%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%2240%22 cy=%2268%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22350%22 cy=%22130%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22167%22 cy=%22174%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22237%22 cy=%2294%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22407%22 cy=%22206%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22132%22 cy=%22171%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22273%22 cy=%22255%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22375%22 cy=%2291%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22500%22 cy=%2243%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22219%22 cy=%22222%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%2286%22 cy=%22147%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%2230%22 cy=%22197%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22392%22 cy=%22170%22 r=%223.6%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22448%22 cy=%2298%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.5%22/%3E%3Ccircle cx=%22358%22 cy=%22176%22 r=%222.2%22 fill=%22white%22 fill-opacity=%220.35%22/%3E%3Ccircle cx=%22300%22 cy=%22138%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3Ccircle cx=%22430%22 cy=%22275%22 r=%222.8%22 fill=%22white%22 fill-opacity=%220.7%22/%3E%3C/svg%3E") right center / cover no-repeat; pointer-events: none; }
.sm-hero > * { position: relative; z-index: 1; }
.sm-hero-eyebrow { display: flex; align-items: center; gap: 0.55em; font-size: 0.8em; font-weight: 600; letter-spacing: 0.12em; text-transform: uppercase; color: #cfe3ff; }
.sm-hero-eyebrow .sm-saltire { display: inline-block; width: 1.9em; height: 1.15em; border-radius: 3px;
background: #005EB8 url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 60 36'%3E%3Cpath d='M0 0L60 36M60 0L0 36' stroke='%23fff' stroke-width='7'/%3E%3C/svg%3E") center / 100% 100%;
box-shadow: 0 0 0 1px rgba(255,255,255,.35); }
.sm-hero-title { font-size: 2.3em; font-weight: 750; line-height: 1.12; margin: 0.35em 0 0.3em; max-width: 16em; text-wrap: balance; color: #fff; }
.sm-hero-sub { font-size: 1.12em; line-height: 1.5; max-width: 34em; color: #e3ecfa; }
.sm-hero-actions { display: flex; flex-wrap: wrap; gap: 0.7em; margin-top: 1.4em; }
.sm-btn a { display: inline-block; padding: 0.62em 1.15em; border-radius: 999px; font-weight: 650; text-decoration: none !important; }
.sm-btn-primary a { background: #fff; color: #0a3a7a !important; }
.sm-btn-primary a:hover { background: #e6f0ff; }
.sm-btn-secondary a { color: #fff !important; box-shadow: inset 0 0 0 1.5px rgba(255,255,255,.7); }
.sm-btn-secondary a:hover { background: rgba(255,255,255,.12); }
.sm-btn a:focus-visible { outline: 2px solid #fff; outline-offset: 2px; }
.sm-hero-facts { display: flex; flex-wrap: wrap; gap: 0.4em 1.4em; margin-top: 1.5em; font-size: 0.9em; color: #cfe3ff; }
.sm-hero-facts span::before { content: "✓ "; color: #8fd19e; font-weight: 700; }
@media (max-width: 640px) {
.sm-hero { padding: 1.5em 1.3em 1.4em; }
.sm-hero::after { inset: 45% 0 0 0; opacity: .6; }
.sm-hero-title { font-size: 1.75em; }
}

/* Site header on every page: the Saltire and the wiki's name, as on scotmesh.net */
#siteNotice { background: none !important; border: 0 !important; padding: 0 !important; margin: 0 0 0.6em !important; text-align: left !important; font-size: 1rem !important; }
.sm-header { display: flex; align-items: center; gap: 1rem; padding: 0.9rem 32px 0.9rem; }
.sm-header a { text-decoration: none !important; }
.sm-flag { display: block; width: 80px; height: 48px; border-radius: 5px; flex: none; background: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 60 36'%3E%3Crect width='60' height='36' fill='%230065bd'/%3E%3Cpath d='M0 0L60 36M60 0L0 36' stroke='white' stroke-width='6'/%3E%3C/svg%3E") center / 100% 100% no-repeat; box-shadow: 0 1px 3px rgba(0,0,0,.35); }
.sm-header-title { font-size: 1.75em; font-weight: 750; line-height: 1.15; }
.sm-header-title a { color: var(--color-emphasized, inherit) !important; }
.sm-header-sub { color: var(--color-subtle, #9ca3af); font-size: 0.98em; margin-top: 0.15em; }
@media (max-width: 640px) { .sm-header { padding: 0.8rem 16px; gap: 0.75rem; } .sm-flag { width: 60px; height: 36px; } .sm-header-title { font-size: 1.35em; } .sm-header-sub { font-size: 0.88em; } }
/* Pointer to the MeshCore / Meshtastic wiki (Main Page, above the hero) */
.sm-otherwiki { margin: 0.2em 0 1em; padding: 0.6em 1em; border: 1px solid #166534; border-radius: 10px; background: #15803d; color: #fff; font-size: 0.95em; display: flex; align-items: center; gap: 0.5em 0.85em; flex-wrap: wrap; line-height: 1.45; overflow-wrap: anywhere; box-shadow: 0 1px 2px rgba(0,0,0,.15); }
.sm-otherwiki b { color: #fff; }
.sm-otherwiki a, .sm-otherwiki a.external, .sm-otherwiki a:visited { color: #fff !important; font-weight: 700; white-space: nowrap; text-decoration: underline; text-underline-offset: 2px; background-image: none; padding-right: 0; }
.sm-otherwiki a:hover, .sm-otherwiki a:focus-visible { color: #dcfce7 !important; }
.sm-ow-logos { display: inline-flex; align-items: center; gap: 0.6em; flex: none; padding: 0.3em 0.65em; border-radius: 7px; background: #166534; }
.sm-ow-logo { display: block; background: center / contain no-repeat; }
.sm-ow-mt { width: 26px; height: 14px; background-image: url("data:image/svg+xml,%3Csvg viewBox=%220 0 100 55%22 xmlns=%22http://www.w3.org/2000/svg%22 style=%22fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;%22%3E%3Cg transform=%22matrix(0.802386,0,0,0.460028,-421.748,-122.127)%22%3E%3Cg transform=%22matrix(0.579082,0,0,1.01004,460.975,-39.6867)%22%3E%3Cpath d=%22M250.908,330.267L193.126,415.005L180.938,406.694L244.802,313.037C246.174,311.024 248.453,309.819 250.889,309.816C253.326,309.814 255.606,311.015 256.982,313.026L320.994,406.536L308.821,414.869L250.908,330.267Z%22 style=%22fill:white;%22/%3E%3C/g%3E%3Cg transform=%22matrix(0.582378,0,0,1.01579,485.019,-211.182)%22%3E%3Cpath d=%22M87.642,581.398L154.757,482.977L142.638,474.713L75.523,573.134L87.642,581.398Z%22 style=%22fill:white;%22/%3E%3C/g%3E%3C/g%3E%3C/svg%3E"); }
.sm-ow-mc { width: 90px; height: 10px; background-image: url("data:image/svg+xml,%3Csvg viewBox=%220 0 134 15%22 xmlns=%22http://www.w3.org/2000/svg%22 style=%22fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;%22%3E%3Cpath d=%22M3.277,0.053C2.829,0.053 2.401,0.41 2.321,0.851L0.013,13.623C-0.067,14.064 0.232,14.421 0.681,14.421L3.13,14.421C3.578,14.421 4.006,14.064 4.086,13.623L5.004,8.54L6.684,13.957C6.766,14.239 7.02,14.421 7.337,14.421L10.58,14.421C10.897,14.421 11.217,14.239 11.401,13.957L15.043,8.513L14.119,13.623C14.038,14.064 14.338,14.421 14.787,14.421L17.236,14.421C17.684,14.421 18.112,14.064 18.192,13.623L20.5,0.851C20.582,0.41 20.283,0.053 19.834,0.053L16.69,0.053C16.373,0.053 16.053,0.235 15.87,0.517L9.897,9.473C9.803,9.616 9.578,9.578 9.528,9.41L7.074,0.517C6.992,0.235 6.738,0.053 6.421,0.053L3.277,0.053Z%22 style=%22fill:white;fill-rule:nonzero;%22/%3E%3Cpath d=%22M21.146,14.421C21.146,14.421 33.257,14.421 33.257,14.421C33.526,14.421 33.784,14.205 33.831,13.942L34.337,11.128C34.385,10.863 34.206,10.649 33.936,10.649L25.519,10.649C25.429,10.649 25.37,10.576 25.385,10.488L25.635,9.105C25.65,9.017 25.736,8.944 25.826,8.944L32.596,8.944C32.865,8.944 33.123,8.728 33.171,8.465L33.621,5.974C33.669,5.709 33.49,5.495 33.221,5.495L26.45,5.495C26.361,5.495 26.301,5.423 26.317,5.335L26.584,3.852C26.599,3.764 26.685,3.691 26.775,3.691L35.192,3.691C35.462,3.691 35.719,3.476 35.767,3.21L36.258,0.498C36.306,0.235 36.126,0.019 35.857,0.019L23.746,0.019C23.297,0.019 22.867,0.378 22.788,0.819L20.474,13.621C20.396,14.062 20.695,14.421 21.146,14.421Z%22 style=%22fill:white;fill-rule:nonzero;%22/%3E%3Cpath d=%22M45.926,14.419L45.926,14.421L46.346,14.421C48.453,14.421 50.465,12.742 50.839,10.67L51.081,9.327C51.456,7.256 50.05,5.576 47.943,5.576L41.455,5.576C41.186,5.576 41.007,5.363 41.054,5.097L41.218,4.192C41.266,3.927 41.524,3.713 41.793,3.713L50.569,3.713C51.018,3.713 51.446,3.356 51.526,2.915L51.9,0.85C51.98,0.407 51.68,0.05 51.232,0.05L41.638,0.05C39.531,0.05 37.519,1.73 37.145,3.801L36.88,5.267C36.505,7.339 37.91,9.018 40.018,9.018L46.506,9.018C46.775,9.018 46.954,9.231 46.907,9.497L46.785,10.176C46.737,10.441 46.479,10.655 46.21,10.655L37.189,10.655C36.741,10.655 36.313,11.012 36.233,11.453L35.841,13.621C35.761,14.062 36.061,14.419 36.51,14.419L45.926,14.419Z%22 style=%22fill:white;fill-rule:nonzero;%22/%3E%3Cpath d=%22M68.008,0.046C68.008,0.046 65.296,0.046 65.296,0.046C64.847,0.046 64.42,0.403 64.34,0.844L63.532,5.31C63.517,5.398 63.431,5.469 63.341,5.469L58.085,5.469C57.995,5.469 57.936,5.398 57.951,5.31L58.758,0.844C58.837,0.403 58.539,0.046 58.09,0.046L55.378,0.046C54.93,0.046 54.502,0.403 54.422,0.844L52.112,13.623C52.032,14.064 52.331,14.421 52.78,14.421L55.492,14.421C55.941,14.421 56.369,14.064 56.449,13.623L57.272,9.074C57.287,8.986 57.373,8.914 57.462,8.914L62.719,8.914C62.809,8.914 62.868,8.985 62.853,9.074L62.032,13.623C61.952,14.064 62.252,14.421 62.7,14.421L65.413,14.421C65.861,14.421 66.289,14.064 66.369,13.623L68.678,0.844C68.755,0.403 68.457,0.046 68.008,0.046Z%22 style=%22fill:white;fill-rule:nonzero;%22/%3E%3Cpath d=%22M72.099,14.421C72.099,14.421 80.066,14.421 80.066,14.421C80.515,14.421 80.943,14.064 81.022,13.623L81.414,11.453C81.494,11.012 81.194,10.655 80.746,10.655L73.828,10.655C73.559,10.655 73.38,10.441 73.427,10.176L74.51,4.215C74.558,3.951 74.815,3.736 75.082,3.736L82,3.736C82.448,3.736 82.876,3.379 82.956,2.938L83.34,0.817C83.42,0.376 83.12,0.019 82.672,0.019L74.724,0.019C72.622,0.019 70.614,1.691 70.236,3.757L68.965,10.665C68.587,12.738 69.99,14.421 72.099,14.421Z%22 style=%22fill:white;fill-rule:nonzero;%22/%3E%3Cpath d=%22M97.176,-0C97.176,0 88.882,0 88.882,0C86.775,0 84.763,1.68 84.389,3.751L83.139,10.67C82.765,12.741 84.169,14.421 86.277,14.421L94.571,14.421C96.678,14.421 98.69,12.741 99.064,10.67L100.314,3.751C100.689,1.68 99.284,-0 97.176,-0ZM94.798,10.178C94.75,10.443 94.492,10.657 94.223,10.657L87.978,10.657C87.709,10.657 87.529,10.443 87.577,10.178L88.659,4.192C88.707,3.927 88.964,3.713 89.234,3.713L95.477,3.713C95.747,3.713 95.926,3.927 95.878,4.192L94.798,10.178Z%22 style=%22fill:white;fill-rule:nonzero;%22/%3E%3Cpath d=%22M101.284,14.421L103.995,14.421C104.443,14.421 104.871,14.065 104.951,13.624L105.43,10.97C105.446,10.882 105.531,10.81 105.621,10.81L108.902,10.806C109.064,10.806 109.2,10.886 109.267,11.018L110.813,14.035C110.992,14.392 111.319,14.434 112.303,14.419C112.88,14.426 113.756,14.382 115.169,14.382C115.623,14.382 115.902,13.907 115.678,13.51L113.989,10.569C113.945,10.491 113.993,10.386 114.086,10.34C115.39,9.707 116.423,8.477 116.681,7.055L117.27,3.785C117.646,1.713 116.242,0.033 114.134,0.033L103.884,0.033C103.436,0.033 103.008,0.39 102.928,0.831L100.616,13.623C100.536,14.064 100.836,14.421 101.284,14.421L101.284,14.421ZM106.73,3.791C106.745,3.703 106.831,3.631 106.921,3.631L112.225,3.631C112.626,3.631 112.891,3.949 112.821,4.343L112.431,6.494C112.359,6.885 111.979,7.204 111.58,7.204L106.276,7.204C106.186,7.204 106.127,7.133 106.142,7.043L106.73,3.791Z%22 style=%22fill:white;fill-rule:nonzero;%22/%3E%3Cpath d=%22M118.277,14.421C118.277,14.421 130.388,14.421 130.388,14.421C130.657,14.421 130.915,14.205 130.963,13.942L131.468,11.128C131.516,10.863 131.337,10.649 131.068,10.649L122.65,10.649C122.56,10.649 122.501,10.576 122.516,10.488L122.766,9.105C122.781,9.017 122.867,8.944 122.957,8.944L129.728,8.944C129.997,8.944 130.254,8.728 130.302,8.465L130.753,5.974C130.801,5.709 130.621,5.495 130.352,5.495L123.581,5.495C123.492,5.495 123.432,5.423 123.448,5.335L123.715,3.852C123.73,3.764 123.816,3.691 123.906,3.691L132.324,3.691C132.593,3.691 132.851,3.476 132.898,3.21L133.389,0.498C133.437,0.235 133.257,0.019 132.988,0.019L120.877,0.019C120.428,0.019 119.999,0.378 119.919,0.819L117.605,13.621C117.527,14.062 117.827,14.421 118.277,14.421Z%22 style=%22fill:white;fill-rule:nonzero;%22/%3E%3C/svg%3E"); }
.sm-ow-text { flex: 1 1 16em; min-width: 0; }
.sm-otherwiki + .sm-hero { margin-top: 0; }
@media (max-width: 640px) { .sm-otherwiki { font-size: 0.9em; padding: 0.5em 0.8em; } }

MediaWiki:Common.css

2026-09-11T15:32:53Z

ScotMesh: Other-wiki line: green so it stands out

Main Page

2026-09-11T15:22:34Z

ScotMesh: Point MeshCore/Meshtastic readers to wiki.scotmesh.uk

{{DISPLAYTITLE:ScotMesh Reticulum Wiki}}
<div class="sm-otherwiki">Looking for <b>MeshCore</b> or <b>Meshtastic</b>? They have their own wiki at [https://wiki.scotmesh.uk wiki.scotmesh.uk] →</div>
<div class="sm-hero">
<div class="sm-hero-title">A free, encrypted network for Scotland that anyone can join.</div>
<div class="sm-hero-sub">Reticulum carries messages, chat, files and pages over the internet and over LoRa radio, and keeps working when the things underneath it do not. Connecting takes about five minutes.</div>
<div class="sm-hero-actions"><span class="sm-btn sm-btn-primary">[[Connecting to ScotMesh|Connect in five minutes →]]</span><span class="sm-btn sm-btn-secondary">[[What Reticulum is|What is Reticulum?]]</span></div>
<div class="sm-hero-facts"><span>No sign-up</span><span>No hardware needed</span><span>Free, run by the community</span><span>Encrypted end to end</span></div>
</div>

<div class="sm-welcome">
'''Welcome.''' ScotMesh runs the Reticulum backbone for Scotland and writes this wiki; you are very welcome to use both, and to add to either. Whether you have never heard of Reticulum or you want to put a solar relay on a hill, there is a page here for you. Pick where you are:
</div>

<div class="sm-cards">
<div class="sm-card">
=== I just want to try it ===
Install one app, type in one address, and you are on the network with everyone else: messaging, chat, files and pages.

'''[[Connecting to ScotMesh|Connect in five minutes →]]'''

Then [[First steps]]: say hello in the chat room and send your first message.
</div>
<div class="sm-card">
=== I want to understand it first ===
No addresses to configure, no accounts, no company in the middle. Reticulum is unusual, and it is worth knowing why.

'''[[What Reticulum is|What Reticulum is →]]'''

Then [[How Reticulum works]], [[How it compares]] with Meshtastic and MeshCore, and the [[Glossary]].
</div>
<div class="sm-card">
=== I want to put a radio on air ===
A LoRa board becomes a Reticulum radio for your laptop or phone, or a self-contained relay you can look after from home.

'''[[RNode|Flash a board →]]'''

Then [[ScotMesh firmware]] for solar and hilltop relays, and [[Antennas and siting]] for making it reach.
</div>
</div>

== The backbone right now ==

Live from the node itself, the same feed as [https://rns.scotmesh.net rns.scotmesh.net], refreshed every two minutes. If the strip is blank or says unknown, treat the backbone as unconfirmed and check the node page directly.

<div id="sm-status" class="sm-status">Live backbone status: [https://rns.scotmesh.net/status.html rns.scotmesh.net/status]</div>

== Connect now ==

The backbone is a public Reticulum transport node in Dalgety Bay, Fife. Anyone may connect, there is nothing to register, and it costs nothing.

'''Out of the box:''' install [https://meshchatx.com MeshChatX] (Windows, macOS, Linux, Android), [https://github.com/markqvist/Sideband/releases Sideband] (Android, Windows, macOS, Linux) or an iPhone app, add a connection of type '''TCPClientInterface''' with host <code>rns.scotmesh.net</code> and port <code>4242</code>, and you are on. [[Connecting to ScotMesh#Out of the box: an app|Step by step]].

'''Full installation:''' add this to your Reticulum config:

<syntaxhighlight lang="text"> [[ScotMesh Backbone]]
type = TCPClientInterface
enabled = yes
target_host = rns.scotmesh.net
target_port = 4242</syntaxhighlight>

'''Behind CGNAT or a firewall you do not control?''' Use the I2P entry point instead; no port needs forwarding at either end. See [[Access over I2P]].

'''Got a LoRa radio?''' ScotMesh's first gateway is on air in Fife, carrying both profiles below and linked to the backbone, and standalone [[ScotMesh firmware|solar nodes]] are going out. Coverage is small so far, so a radio built anywhere in Scotland will hear the others as they arrive. Every radio must match all five settings exactly: a board with a different spreading factor is not weakly connected, it is completely deaf, and nothing reports an error. [https://rnode.scotmesh.net rnode.scotmesh.net] applies either profile in one click.

{| class="wikitable"
|-
!
! 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
|}

Whichever way in you chose: restart Reticulum, then check the interface shows '''Up''' (in <code>rnstatus</code>, or on the app's interfaces page). If it does not, [[Troubleshooting]] 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]]; [[Services and addresses]] has them all in one place.

{| class="wikitable"
|-
! Service
! Address
! Use it with
|-
| TCP entry point
| <code>rns.scotmesh.net:4242</code>
| Any Reticulum client
|-
| I2P entry point
| <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code>
| Any Reticulum client, via i2pd
|-
| [[The chat room|Chat hub]] (RRC), room <code>scotmesh</code>
| <code>004e5a15da221d9a236b0e8d74195f13</code>
| MeshChatX, <code>rrc</code> clients
|-
| [[Propagation node|LXMF propagation node]]
| <code>c283b754e0acc11ce48d2f5e29167e0c</code>
| Sideband, MeshChatX, Nomad Network
|-
| [[Nomad Network|Nomad Network node]]
| <code>10a839df2c50635bcb0c8a299b9ca0f8</code>
| Nomad Network, MeshChatX
|-
| Transport instance
| <code>20b962cd814444f7812e409e7c47f319</code>
| Shows up in <code>rnpath</code> and node maps
|}

The node peers outward to <code>rebelnet.uk</code>, <code>rns.cybercore.uk</code> and <code>rmap.world</code>, so a client connected here can reach the rest of the public Reticulum network. See [[Who we peer with]].

== Where the network is ==

Where things actually are, rather than where we would like them to be. Updated by hand as things land.

{| class="wikitable"
|-
!
! Milestone
! Notes
|-
| ✔
| '''Reticulum backbone online'''
| Public transport node at <code>rns.scotmesh.net:4242</code>, peered into the wider network.
|-
| ✔
| '''Reachable over I2P'''
| No port forwarding needed at either end.
|-
| ✔
| '''Chat hub running'''
| RRC hub with the <code>scotmesh</code> room.
|-
| ✔
| '''Propagation node running'''
| Offline message delivery for the region.
|-
| ✔
| '''Web flasher for RNodes and nodes'''
| [https://rnode.scotmesh.net rnode.scotmesh.net], with both ScotMesh profiles built in.
|-
| ✔
| '''LoRa gateway on air'''
| First gateway in Fife, both profiles, linked to the backbone.
|-
| ✔
| '''Standalone solar nodes'''
| [[ScotMesh firmware]]: managed and updated over the mesh. First units on the bench and going out.
|-
| ✘
| '''Coverage beyond Fife'''
| Needs gateways and relays elsewhere. [[Running your own transport node|Put one up]] and tell us.
|}

== Find your way ==

{| class="wikitable"
|-
| '''I have never used Reticulum'''
| Read in order: [[What Reticulum is|what Reticulum is]] → [[How it compares|how it compares]] to Meshtastic, MeshCore and LoRaWAN → [[Connecting to ScotMesh|connecting to ScotMesh]] → [[Choosing a client|choosing a client]] → [[First steps|first steps]].
|-
| '''I am connected. What can I do?'''
| Join [[The chat room|the chat room]], send messages that arrive even when the other person is offline via the [[Propagation node|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; [[ScotMesh firmware]] for a solar relay you can look after from home; [[Antennas and siting|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|known bugs and workarounds]].
|-
| '''What is ScotMesh building?'''
| The [[Project index|project index]]: the [[ScotMesh firmware]], the flasher, and [[MeshCore as a Reticulum Interface|MeshCore as a Reticulum interface]].
|-
| '''I want to read and watch more'''
| [[Learning resources]]: the manual, talks, the community wiki, and where people talk.
|-
| '''What does that word mean?'''
| The [[Glossary|glossary]].
|}

== Say hello ==

ScotMesh is a community, not a company. Most of us are on the [https://discord.gg/ytxfyuDmSt ScotMesh Discord], the quickest place to ask anything, Reticulum or not, and there is also the [https://scotmesh.uk forum at scotmesh.uk]; [[The chat room|the chat room]] is where to find us on the network itself; and [[About ScotMesh]] says who we are and what we run. If a page here is wrong or unclear, say so, or fix it: [[ScotMesh Wiki:About|anyone can ask for an editing account]].

MediaWiki:Common.css

2026-09-11T15:22:33Z

ScotMesh: Style for MeshCore/Meshtastic pointer (sm-otherwiki)

MediaWiki:Sitenotice

2026-09-11T15:22:32Z

ScotMesh: Header title: ScotMesh Reticulum Wiki

<div class="sm-header">[[Main Page|<span class="sm-flag" title="ScotMesh Reticulum Wiki"></span>]]<div class="sm-header-text"><div class="sm-header-title">[[Main Page|ScotMesh Reticulum Wiki]]</div><div class="sm-header-sub">Reticulum in Scotland: free, encrypted, run by the community</div></div></div>

The ScotMesh node

2026-09-11T15:22:07Z

ScotMesh: Chat hub now runs rrc-hub

The '''ScotMesh node''' is a public Reticulum [[Glossary#Transport node|transport node]] for Scotland, reachable as <code>rns.scotmesh.net</code>. 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 <code>enable_transport</code> on, so anything connected to it can reach anything it can reach: other ScotMesh users, and through [[Who we peer with|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 <code>scotmesh</code> 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|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 (<code>rnsd</code>) shared by the chat hub (<code>[https://github.com/thatSFguy/reticulum-relay-chat rrc-hub]</code>), the propagation node (<code>lxmd</code>), the Nomad Network node and an I2P router (<code>i2pd</code>) for the [[Access over I2P|I2P entry point]].

Its live status, updated every two minutes from the daemon itself, is on [https://rns.scotmesh.net rns.scotmesh.net] and at the top of this wiki's [[Main Page|home page]].

== Ways in ==

{| class="wikitable"
! Way in !! Use it when !! Details
|-
| TCP, <code>rns.scotmesh.net</code> port 4242 || You have an ordinary internet connection || [[Connecting to ScotMesh]]
|-
| I2P || You are behind CGNAT or a firewall you do not control || [[Access over I2P]]
|-
| LoRa radio || You are within range of a ScotMesh gateway || [[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|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.
* '''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 [https://discord.gg/ytxfyuDmSt ScotMesh Discord] 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.

[[Category:The ScotMesh Backbone]]

Glossary

2026-09-11T15:22:07Z

ScotMesh: Chat hub now runs rrc-hub

The vocabulary of Reticulum and of this wiki, a sentence or two each. [[How Reticulum works]] puts most of these together into one explanation.

; Announce
: A small signed packet a [[#Destination|destination]] sends to make itself known: its address, public key and optionally a little data such as a node's name. [[#Transport node|Transport nodes]] pass announces on and remember where they came from, which is how [[#Path|paths]] are built.

; Address
: See [[#Destination hash|destination hash]].

; Bearer
: Anything that can carry Reticulum traffic: LoRa, Wi-Fi, the internet, I2P, a serial cable, packet radio. See [[What Reticulum is]].

; Destination
: Something that can be reached on the network: your messaging inbox, a Nomad Network node, a chat hub. Each belongs to an [[#Identity|identity]] and has its own address.

; Destination hash
: A destination's address: 16 bytes, written as 32 hexadecimal characters, such as <code>10a839df2c50635bcb0c8a299b9ca0f8</code>. It is derived from the identity's public key, so nobody else can claim it.

; Gateway mode
: An [[#Interface mode|interface mode]] for a node that connects clients to a wider network. It answers path requests on its clients' behalf.

; Identity
: A pair of cryptographic keys, one for encryption and one for signing, created by your own software. Nobody issues or registers them. Being ''identified'' to a node means proving you hold a particular identity.

; Interface
: A configuration block that connects Reticulum to a [[#Bearer|bearer]]: a TCP connection, an I2P tunnel, an [[#RNode|RNode]]. In the config file each one starts with its name in double brackets, such as <code><nowiki>[[ScotMesh Backbone]]</nowiki></code>.

; Interface mode
: How a node treats announces and path requests on an interface: full, gateway, access point, roaming or boundary.

; Link
: An encrypted, verified connection between two parties, set up with fresh keys each time (forward secrecy). Browsing pages and transferring files use links.

; LXMF
: The message format Reticulum applications use for messaging. Sideband, MeshChatX and Nomad Network all speak it, so their users can message each other.

; Micron
: The lightweight markup [[Nomad Network]] pages are written in.

; microReticulum
: An implementation of Reticulum that runs on small microcontroller boards rather than computers. The [[ScotMesh firmware]] is built on it.

; MTU
: The largest packet a network carries. Reticulum's is 500 bytes, which is why pages for LoRa are kept small.

; Nomad Network
: Pages, files and messaging that live entirely inside Reticulum, with no DNS or hosting. See [[Nomad Network]].

; Path
: What a node knows about reaching a destination: which neighbour to send to, and how many hops away it is.

; Propagation node
: A node that holds [[#LXMF|LXMF]] messages for people who are offline and delivers them when they reappear. It stores them encrypted and cannot read them. See [[Propagation node]].

; RNode
: A LoRa radio running the RNode firmware, used by a computer or phone as a Reticulum interface. See [[RNode]].

; RRC
: The chat protocol used by ScotMesh's chat room, run by a hub program called <code>rrc-hub</code>. See [[The chat room]].

; rnsd, rnstatus, rnpath, rnprobe
: The Reticulum daemon, and the utilities that show its interfaces, look up a path, and test whether a destination answers.

; Transport node
: A Reticulum node that forwards traffic for others, because its owner set <code>enable_transport = Yes</code>. It only ever handles encrypted packets.

[[Category:Getting Started]]