N7EKB's Reticulum Status Page

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.

---

reticulum.n7ekb.net rnstatus

Updated:  Fri, 25 Apr 2025 at 21:10 PDT.   

rnstatus 0.9.4
Could not get RNS status

---

reticulum.n7ekb.net lxmd --status

Updated:   Fri, 25 Apr 2025 at 21:10 PDT.   

lxmd 0.6.3

---

hamshackpc rnstatus

Updated:  Wed, 23 Apr 2025 at 14:07 PDT.   

rnstatus 0.9.4

 AutoInterface[Local LAN webstat]
    Status    : Up
    Mode      : Full
    Rate      : 10.00 Mbps
    Peers     : 0 reachable
    Traffic   : ↑0 B  0 bps
                ↓0 B  0 bps

 TCPServerInterface[Hamshack on Tailnet webstat/100.127.58.23:48086]
    Status    : Up
    Clients   : 2
    Mode      : Full
    Rate      : 10.00 Mbps
    Traffic   : ↑1.85 MB  1.10 Kbps
                ↓2.72 MB  0 bps

 RNodeInterface[RNode RAK4631 Solar webstat]
    Status    : Up
    Mode      : Full
    Rate      : 3.12 kbps
    Noise Fl. : -114 dBm
    Airtime   : 5.06% (15s), 2.31% (1h)
    Ch. Load  : 12.06% (15s), 13.64% (1h)
    Traffic   : ↑161.80 KB  536 bps
                ↓542.53 KB  0 bps

 Transport Instance <3fd741510caa4607f479906e0d7bf106> running
 Uptime is 5h, 32m and 47.81s

---

hamshackpc lxmd --status

Updated:  Fri, 25 Apr 2025 at 21:10 PDT.   

lxmd 0.6.3

LXMF Propagation Node running on <f16b298f6457fe3af8c79cc3720d632f>, uptime is 1m and 17.76s
Messagestore contains 7817 messages, 3.78 MB (0.76% utilised of 500.00 MB)
Accepting propagated messages from all nodes, 256.00 KB per-transfer limit

Peers   : 50 total (peer limit is 50)
          50 discovered, 0 static
          17 available, 33 unreachable

Traffic : 6722 messages received in total (3.37 MB)
          5530 messages received from peered nodes (2.43 MB)
          1189 messages received from unpeered nodes (945.09 KB)
          77945 messages transferred to peered nodes (33.74 MB)
          3 propagation messages received directly from clients
          3 propagation messages served to clients
          Distribution factor is 11.6