Who we peer with: Difference between revisions

Revision as of 15:50, 11 September 2026

A transport node on its own is an island. The ScotMesh node peers with other public Reticulum nodes, which is what lets someone connected here reach the rest of the network, and lets the rest of the network reach ScotMesh. Being open about whose infrastructure our traffic crosses is the point of this page.

Current peers

Peer	Where	Link
`rebelnet.uk`	UK	TCP
`rns.cybercore.uk`	UK	TCP
`rmap.world`	France	TCP. Also the home of the Reticulum node map, which is why ScotMesh nodes that publish their position appear there.
An I2P transport node in Northern Ireland	Northern Ireland	I2P

Peers change occasionally as nodes come and go; this table is updated by hand.

What peering means

Two transport nodes peer by one connecting to the other as an interface, exactly as a client does. From then on each announces the paths it knows to the other, and forwards traffic for it. Nothing else is shared: no user lists, no message contents, no logs.

It costs the operator almost nothing. Transport nodes relay ciphertext only: every packet is encrypted end to end before it reaches them, and packets carry no sender address. A peer sees that traffic for a given destination passes through, and the bandwidth it uses; that is all. Bandwidth on a Reticulum node is tiny by internet standards.

Peering with us

We would like more links, particularly across the UK and Ireland, and particularly over radio where two networks are within reach of each other.

If you run a transport node, add ours as a peer:

  [[ScotMesh Backbone]]
    type = TCPClientInterface
    enabled = yes
    target_host = rns.scotmesh.net
    target_port = 4242

That is enough for traffic to flow both ways. If your node is reachable by others, tell us its hostname and port (or I2P address) on the forum and we will add a connection from our side too, so the link survives either end restarting. Running your own transport node covers setting a node up in the first place.

@@ Line 1: / Line 1: @@
-''Outline — the shape of the page, not the page. Expand or replace freely.''
+A transport node on its own is an island. The ScotMesh node '''peers''' with other public Reticulum nodes, which is what lets someone connected here reach the rest of the network, and lets the rest of the network reach ScotMesh. Being open about whose infrastructure our traffic crosses is the point of this page.
-Whose infrastructure ScotMesh traffic crosses. Being open about this is the point.
+== Current peers ==
-== To cover ==
+{| class="wikitable"
+! Peer !! Where !! Link
+|-
+| <code>rebelnet.uk</code> || UK || TCP
+|-
+| <code>rns.cybercore.uk</code> || UK || TCP
+|-
+| <code>rmap.world</code> || France || TCP. Also the home of the Reticulum node map, which is why ScotMesh nodes that publish their position appear there.
+|-
+| An I2P transport node in Northern Ireland || Northern Ireland || I2P
+|}
-* Current peers and where they are
+Peers change occasionally as nodes come and go; this table is updated by hand.
-* Why peering costs the operator nothing — transport nodes relay ciphertext only
-* How to peer with us
+== What peering means ==
-* That we would like more UK and Irish links
+Two transport nodes peer by one connecting to the other as an interface, exactly as a client does. From then on each announces the paths it knows to the other, and forwards traffic for it. Nothing else is shared: no user lists, no message contents, no logs.
+It costs the operator almost nothing. Transport nodes '''relay ciphertext only''': every packet is encrypted end to end before it reaches them, and packets carry no sender address. A peer sees that traffic for a given destination passes through, and the bandwidth it uses; that is all. Bandwidth on a Reticulum node is tiny by internet standards.
+== Peering with us ==
+We would like more links, particularly across the UK and Ireland, and particularly over radio where two networks are within reach of each other.
+If you run a transport node, add ours as a peer:
+<syntaxhighlight lang="text">  [[ScotMesh Backbone]]
+    type = TCPClientInterface
+    enabled = yes
+    target_host = rns.scotmesh.net
+    target_port = 4242</syntaxhighlight>
+That is enough for traffic to flow both ways. If your node is reachable by others, tell us its hostname and port (or I2P address) on the [https://scotmesh.uk forum] and we will add a connection from our side too, so the link survives either end restarting. [[Running your own transport node]] covers setting a node up in the first place.
 [[Category:The ScotMesh Backbone]]