Who we peer with
More actions
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.