N7EKB's Reticulum Status Page

Sideband app status with RNode and TCP connections 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 "1ac621739a76ad2743eef8d036cc61e5" 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:  Wed, 02 Apr 2025 at 22:00 PDT.   

rnstatus 0.9.3

 Shared Instance[37428]
    Status    : Up
    Serving   : 5 programs
    Rate      : 1.00 Gbps
    Traffic   : ↑84.73 MB  6.53 Kbps
                ↓40.01 MB  0 bps

 AutoInterface[Local LAN]
    Status    : Up
    Mode      : Gateway
    Rate      : 1.00 Gbps
    Peers     : 0 reachable
    Traffic   : ↑0 B  0 bps
                ↓0 B  0 bps

 TCPServerInterface[Internal Tailnet Server/100.113.187.99:48086]
    Status    : Up
    Clients   : 1
    Mode      : Gateway
    Rate      : 1.00 Gbps
    Traffic   : ↑58.21 MB  0 bps
                ↓21.86 MB  0 bps

 TCPInterface[hamshack RNode via Tailnet/hamshackpc.tail00c184.ts.net:48086]
    Status    : Up
    Mode      : Boundary
    Rate      : 1.00 Gbps
    Traffic   : ↑8.11 MB   0 bps
                ↓30.47 MB  0 bps

 TCPServerInterface[reticulum.n7ekb.net/104.168.132.59:48086]
    Status    : Up
    Clients   : 10
    Mode      : Gateway
    Rate      : 10.00 Mbps
    Traffic   : ↑68.98 MB  0 bps
                ↓62.31 MB  3.48 Kbps

 TCPInterface[Sideband TCP/sideband.connect.reticulum.network:7822]
    Status    : Up
    Mode      : Full
    Rate      : 10.00 Mbps
    Traffic   : ↑46.15 MB  0 bps
                ↓67.76 MB  0 bps

 TCPInterface[XZ Group/reticulum.xzgroup.net:8666]
    Status    : Up
    Mode      : Full
    Rate      : 10.00 Mbps
    Traffic   : ↑9.36 MB  0 bps
                ↓2.87 MB  0 bps

 TCPInterface[Reticulum Network World Map/rmap.world:4242]
    Status    : Up
    Mode      : Full
    Rate      : 10.00 Mbps
    Traffic   : ↑4.96 MB  0 bps
                ↓5.18 MB  0 bps

 Transport Instance <b082264df033806d0977982271d36c3d> running
 Uptime is 14h, 49m and 27.36s


reticulum.n7ekb.net lxmd --status

Updated:   Wed, 02 Apr 2025 at 22:00 PDT.   

lxmd 0.6.3

LXMF Propagation Node running on <1ac621739a76ad2743eef8d036cc61e5>, uptime is 14h, 49m and 15.73s
Messagestore contains 31951 messages, 32.02 MB (6.4% 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
          41 available, 9 unreachable

Traffic : 257784 messages received in total (133.27 MB)
          32664 messages received from peered nodes (30.47 MB)
          225119 messages received from unpeered nodes (102.80 MB)
          4747 messages transferred to peered nodes (11.53 MB)
          1 propagation messages received directly from clients
          0 propagation messages served to clients
          Distribution factor is 0.02


hamshackpc RNode rnstatus

Updated:  Wed, 02 Apr 2025 at 22:00 PDT.   

rnstatus 0.9.3

 TCPInterface[reticulum.n7ekb.net via Tailnet webstat/100.113.187.99:48086]
    Status    : Up
    Mode      : Boundary
    Rate      : 1.00 Gbps
    Traffic   : ↑22.12 MB  1.69 Kbps
                ↓57.41 MB  0 bps

 RNodeInterface[Solar RAK4631 RNode FW 1.81 webstat]
    Status    : Up
    Mode      : Full
    Rate      : 3.12 kbps
    Noise Fl. : -113 dBm
    Airtime   : 0.0% (15s), 2.29% (1h)
    Ch. Load  : 0.0% (15s), 10.34% (1h)
    Traffic   : ↑545.75 KB  0 bps
                ↓1.10 MB    0 bps

 Transport Instance <aa6c2f57394e9394206182fdb7c061fa> running
 Uptime is 22h, 33m and 2.19s


hamshackpc lxmd --status

Updated:  Wed, 02 Apr 2025 at 22:00 PDT.   

lxmd 0.6.3

LXMF Propagation Node running on <9594b9982fdfb75ebd617769ff479c71>, uptime is 8d, 1h, 20m and 0.78s
Messagestore contains 41166 messages, 24.57 MB (4.91% utilised of 500.00 MB)
Accepting propagated messages from all nodes, 256.00 KB per-transfer limit

Peers   : 68 total (peer limit is 75)
          67 discovered, 1 static
          22 available, 46 unreachable

Traffic : 602894 messages received in total (392.45 MB)
          197922 messages received from peered nodes (143.36 MB)
          404865 messages received from unpeered nodes (249.09 MB)
          573414 messages transferred to peered nodes (388.66 MB)
          107 propagation messages received directly from clients
          170 propagation messages served to clients
          Distribution factor is 0.95