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 "5cc574b78390d5bc96bbc7bc90953d01" 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 underlying 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: Mon, 12 May 2025 at 11:40 PDT.
rnstatus 0.9.4 Shared Instance[rns/default] Status : Up Serving : 1 program Rate : 1.00 Gbps Traffic : ↑161.49 MB 1.63 Kbps ↓1.08 GB 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[Internal Tailnet/100.117.63.114:48086] Status : Up Clients : 0 Mode : Full Rate : 10.00 Mbps Traffic : ↑0 B 0 bps ↓0 B 0 bps TCPServerInterface[reticulum.n7ekb.net/104.168.132.59:48086] Status : Up Clients : 11 Mode : Full Rate : 10.00 Mbps Traffic : ↑1.56 GB 0 bps ↓360.49 MB 4.80 Kbps Transport Instance <0d717d0322e95086246d5731f181af45> running Uptime is 6d, 15h, 34m and 43.08s
Updated: Mon, 12 May 2025 at 11:40 PDT.
lxmd 0.6.3 LXMF Propagation Node running on <c872e4647a1aa083af415e483fdcba0a>, uptime is 6d, 15h, 34m and 41.83s Messagestore contains 61257 messages, 47.56 MB (9.51% utilised of 500.00 MB) Accepting propagated messages from all nodes, 256.00 KB per-transfer limit Peers : 32 total (peer limit is 32) 32 discovered, 0 static 28 available, 4 unreachable Traffic : 58494 messages received in total (44.68 MB) 20768 messages received from peered nodes (15.92 MB) 37726 messages received from unpeered nodes (28.76 MB) 1294403 messages transferred to peered nodes (1.02 GB) 0 propagation messages received directly from clients 0 propagation messages served to clients Distribution factor is 22.13
Updated: Tue, 06 May 2025 at 20:00 PDT.
Updated: Mon, 12 May 2025 at 11:40 PDT.