I host a public Reticulum Node with TCP client access here on the commercial Internet. The status of this node and the accompanying LXMF propagation node are listed below on this page. Check out the project mapping the reticulum network available here: https://rmap.world.
To connect to my public TCP Reticulum node, here is the config file entry you'll need:
[[reticulum.n7ekb.net]]
type = TCPClientInterface
mode = gateway
enabled = yes
target_host = reticulum.n7ekb.net
target_port = 48086
To use my public LXMF propagation node for store/forward of your messages in an LXMF messaging client such as Sideband or reticulum-meshchat, enter "c872e4647a1aa083af415e483fdcba0a" as your LXMF Propagation Node address.
I have several Meshtastic devices which I have re-flashed with RNode firmware. These LoRA devices are networked together operating on 914.875 MHz (bandwidth 125 Hz, Spreading Factor 8) on the ISM band. My local RNode network is bridged to my public TCP Reticulum Node via my Ham Shack PC, aka "hamshackpc". The status of the hamshackpc RNode interface and separate LXMF propagation node are at the bottom of this page. With the exception of the mobile RNode device in my car, my RNode devices are located in grid square CN86PV (Rainier, WA, USA).
I run Sideband on my GrapheneOS phone paired via Bluetooth to a LilyGo T-Echo device programmed with the RNode firmware. You'll see my announce messages on the Reticulum network as "Ed, N7EKB Pixel 7a". My LXMF ID is "2e6582477f938299905ee3e81039bb8e". If you're not within LoRA RF range of CN86PV then your direct LXMF messages to my phone are routed from the commercial internet into my hamshackpc. From the hamshackpc your message then travels via the hamshackpc's RNode over LoRA RF to the Rnode device directly connected to my phone. If my phone is off making a direct connection impossible, your message can be stored by the LMXF propagation node on my hamshackpc for later retrieval when I turn my phone back on.
When I travel out of range of gridsquare CN86PV my phone uses a free private Tailscale VPN TCP connection over mobile data to a PC that has an RNode device within range of CN86PV. This arrangement ensures that the final path for my messages (both direct and propagated) are traveling over LoRA without the commercial internet. The dream is for the RNode network to grow to the point that the backup TCP connection is no longer needed.
Updated: Wed, 03 Dec 2025 at 08:10 PST.
rnstatus 1.0.0
Shared Instance[rns/default]
Status : Up
Serving : 2 programs
Rate : 1.00 Gbps
Traffic : ↑776.07 MB 5.95 Kbps
↓132.03 MB 0 bps
AutoInterface[Local LAN]
Status : Up
Mode : Full
Rate : 1.00 Gbps
Peers : 0 reachable
Traffic : ↑0 B 0 bps
↓0 B 0 bps
TCPServerInterface[Internal Tailnet/100.117.63.114:48086]
Status : Up
Clients : 1
Mode : Gateway
Rate : 1.00 Gbps
Traffic : ↑34.30 MB 1.49 Kbps
↓63.76 MB 4.11 Kbps
TCPServerInterface[reticulum.n7ekb.net/104.168.132.59:48086]
Status : Up
Clients : 27
Mode : Gateway
Rate : 100.00 Mbps
Traffic : ↑1.87 GB 51.50 Kbps
↓2.29 GB 22.32 Kbps
TCPInterface[R-MAP World/rmap.world:4242]
Status : Up
Mode : Full
Rate : 100.00 Mbps
Traffic : ↑39.24 MB 1.49 Kbps
↓106.86 MB 0 bps
TCPInterface[Quixote Network Spain/reticulum.quixote.network:4242]
Status : Up
Mode : Full
Rate : 100.00 Mbps
Traffic : ↑26.36 MB 1.49 Kbps
↓32.62 MB 1.46 Kbps
TCPInterface[dismail.de Germany/rns.dismail.de:7822]
Status : Up
Mode : Full
Rate : 100.00 Mbps
Traffic : ↑11.50 MB 0 bps
↓6.44 MB 0 bps
TCPInterface[Netherlands Hamnet Gateway/nl.rns.hamesh.eu:8694]
Status : Up
Mode : Full
Rate : 100.00 Mbps
Traffic : ↑26.52 MB 3.08 Kbps
↓36.09 MB 1.46 Kbps
TCPInterface[Gothenburg Sweden/node01.rns.bnz.se:4242]
Status : Up
Mode : Full
Rate : 100.00 Mbps
Traffic : ↑52.21 MB 1.49 Kbps
↓31.74 MB 0 bps
TCPInterface[Sydney Australia/sydney.reticulum.au:4242]
Status : Up
Mode : Full
Rate : 100.00 Mbps
Traffic : ↑25.69 MB 1.49 Kbps
↓50.58 MB 1.59 Kbps
Transport Instance <0d717d0322e95086246d5731f181af45> running
Uptime is 5d, 21h, 18m and 22.72s
Updated: Wed, 03 Dec 2025 at 08:10 PST.
lxmd 0.8.0
LXMF Propagation Node running on <c872e4647a1aa083af415e483fdcba0a>, uptime is 5d, 21h, 17m and 38.18s
Messagestore contains 116440 messages, 49.81 MB (99.62% utilised of 50.00 MB)
Accepting propagated messages from all nodes, 256.00 KB per-transfer limit
Peers : 32 total (peer limit is 32)
29 discovered, 3 static
17 available, 15 unreachable
Traffic : 2796983 messages received in total (9.26 GB)
106148 messages received from peered nodes (681.76 MB)
2690826 messages received from unpeered nodes (8.58 GB)
2282595 messages transferred to peered nodes (6.53 GB)
9 propagation messages received directly from clients
336 propagation messages served to clients
Distribution factor is 0.82
Updated: Wed, 03 Dec 2025 at 08:10 PST.
rnstatus 1.0.0
Shared Instance[rns/default]
Status : Up
Serving : 2 programs
Rate : 1.00 Gbps
Traffic : ↑621.55 MB 8.77 Kbps
↓302.75 MB 0 bps
AutoInterface[Local LAN]
Status : Up
Mode : Full
Rate : 10.00 Mbps
Peers : 0 reachable
Traffic : ↑0 B 0 bps
↓0 B 0 bps
TCPServerInterface[Hamshack on Tailnet/100.127.58.23:48086]
Status : Up
Clients : 0
Mode : Gateway
Rate : 10.00 Mbps
Traffic : ↑38.24 MB 0 bps
↓202.18 KB 0 bps
TCPInterface[reticulum.n7ekb.net via Tailnet/100.117.63.114:48086]
Status : Up
Mode : Full
Rate : 10.00 Mbps
Traffic : ↑433.73 MB 3.83 Kbps
↓205.53 MB 536 bps
RNodeInterface[RNode RAK4631 Solar]
Status : Up
Mode : Full
Rate : 3.12 kbps
Noise Fl. : -111 dBm
Airtime : 4.44% (15s), 2.31% (1h)
Ch. Load : 11.16% (15s), 7.09% (1h)
Traffic : ↑17.22 MB 0 bps
↓16.44 MB 0 bps
Transport Instance <3fd741510caa4607f479906e0d7bf106> running
Uptime is 24d, 10h, 40m and 41.65s
Updated: Wed, 03 Dec 2025 at 08:10 PST.
lxmd 0.8.0
LXMF Propagation Node running on <f16b298f6457fe3af8c79cc3720d632f>, uptime is 24d, 10h, 39m and 36.58s
Messagestore contains 113882 messages, 49.74 MB (99.48% utilised of 50.00 MB)
Accepting propagated messages from static peers only, 256.00 KB per-transfer limit
Peers : 16 total (peer limit is 16)
14 discovered, 2 static
5 available, 11 unreachable
Traffic : 535216 messages received in total (3.13 GB)
419253 messages received from peered nodes (2.96 GB)
115896 messages received from unpeered nodes (176.28 MB)
205158 messages transferred to peered nodes (400.22 MB)
67 propagation messages received directly from clients
91 propagation messages served to clients
Distribution factor is 0.38