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: Sun, 13 Jul 2025 at 00:00 PDT.
rnstatus 0.9.6 Shared Instance[rns/default] Status : Up Serving : 2 programs Rate : 1.00 Gbps Traffic : ↑1.63 GB 0 bps ↓1.85 GB 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 : ↑638.68 MB 0 bps ↓804.48 MB 0 bps TCPServerInterface[reticulum.n7ekb.net/104.168.132.59:48086] Status : Up Clients : 18 Mode : Gateway Rate : 100.00 Mbps Traffic : ↑4.66 GB 0 bps ↓2.49 GB 15.59 Kbps TCPInterface[R-MAP World/rmap.world:4242] Status : Up Mode : Full Rate : 100.00 Mbps Traffic : ↑303.30 MB 0 bps ↓347.87 MB 0 bps TCPInterface[Quixote Network Spain/reticulum.quixote.network:4242] Status : Up Mode : Full Rate : 100.00 Mbps Traffic : ↑53.49 MB 0 bps ↓1.61 GB 1.46 Kbps TCPInterface[dismail.de Germany/rns.dismail.de:7822] Status : Up Mode : Full Rate : 100.00 Mbps Traffic : ↑346.38 MB 0 bps ↓201.55 MB 0 bps TCPInterface[Netherlands Hamnet Gateway/nl.rns.hamesh.eu:8694] Status : Up Mode : Full Rate : 100.00 Mbps Traffic : ↑49.06 MB 0 bps ↓115.80 MB 0 bps TCPInterface[Gothenburg Sweden/node01.rns.bnz.se:4242] Status : Up Mode : Full Rate : 100.00 Mbps Traffic : ↑60.13 MB 0 bps ↓225.16 MB 1.60 Kbps TCPInterface[Sydney Australia/sydney.reticulum.au:4242] Status : Down Mode : Full Rate : 100.00 Mbps Traffic : ↑5.19 KB 0 bps ↓2.68 KB 0 bps Transport Instance <0d717d0322e95086246d5731f181af45> running Uptime is 16d, 4h, 50m and 8.07s
Updated: Sun, 13 Jul 2025 at 00:00 PDT.
lxmd 0.7.1 LXMF Propagation Node running on <c872e4647a1aa083af415e483fdcba0a>, uptime is 16d, 4h, 49m and 43.9s Messagestore contains 64641 messages, 50.21 MB (100.42% 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 31 available, 1 unreachable Traffic : 419833 messages received in total (3.01 GB) 142289 messages received from peered nodes (1.75 GB) 277543 messages received from unpeered nodes (1.26 GB) 1418649 messages transferred to peered nodes (3.05 GB) 1 propagation messages received directly from clients 241 propagation messages served to clients Distribution factor is 3.38
Updated: Sun, 13 Jul 2025 at 00:00 PDT.
rnstatus 0.9.6 Shared Instance[rns/default] Status : Up Serving : 1 program Rate : 1.00 Gbps Traffic : ↑514.82 MB 0 bps ↓598.99 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 : 1 Mode : Gateway Rate : 10.00 Mbps Traffic : ↑172.83 MB 0 bps ↓107.65 MB 0 bps TCPInterface[reticulum.n7ekb.net via Tailnet/100.117.63.114:48086] Status : Up Mode : Full Rate : 10.00 Mbps Traffic : ↑754.98 MB 0 bps ↓574.60 MB 0 bps RNodeInterface[RNode RAK4631 Solar] Status : Up Mode : Full Rate : 3.12 kbps Noise Fl. : -113 dBm Airtime : 0.0% (15s), 2.25% (1h) Ch. Load : 0.0% (15s), 7.09% (1h) Traffic : ↑9.71 MB 0 bps ↓10.22 MB 0 bps Transport Instance <3fd741510caa4607f479906e0d7bf106> running Uptime is 14d, 4h, 49m and 17.08s
Updated: Sun, 13 Jul 2025 at 00:00 PDT.
lxmd 0.7.1 LXMF Propagation Node running on <f16b298f6457fe3af8c79cc3720d632f>, uptime is 14d, 4h, 49m and 21.82s Messagestore contains 61701 messages, 50.30 MB (100.6% utilised of 50.00 MB) Accepting propagated messages from static peers only, 256.00 KB per-transfer limit Peers : 17 total (peer limit is 16) 15 discovered, 2 static 16 available, 1 unreachable Traffic : 280294 messages received in total (1.39 GB) 164382 messages received from peered nodes (1.22 GB) 115896 messages received from unpeered nodes (176.28 MB) 1678644 messages transferred to peered nodes (1.92 GB) 16 propagation messages received directly from clients 63 propagation messages served to clients Distribution factor is 5.99