#microreticulum — Public Fediverse posts

@circfruit
Explanation for readers:
Python- #Reticulum's simple routing may lead to bad connections. rnsd or #microReticulum may choose a worse direct connection over a better multi-hop mesh connection. This is a real problem.

Reason: Reticulum's design follows the KISS principle.
But #Leviculum follows the Keep-It-Testable principle. I created a concept with emulated radios in https://codeberg.org/Lew_Palm/Periculum/issues/28 to reproduce the problem. A fix for the Leviculum firmware & lnsd daemon will follow.

A compelling article on the advantages of #Reticulum over #Meshtastic and #MeshCore:

https://www.jonaharagon.com/posts/im-getting-into-mesh-networks-meshtastic-meshcore-and-reticulum/

Meshtastic and MeshCore make it relatively easy to set up local LoRa mesh networks, but in practice they remain largely tied to LoRa devices and messaging.

Reticulum goes further: it can build a more resilient network by routing across different kinds of connections, including LoRa, Wi-Fi, Ethernet, microwave links and even the internet. Local networks can therefore interconnect while retaining alternative paths if one connection fails.

Reticulum’s main disadvantage today is that standalone LoRa nodes generally need an attached computer running Reticulum. If #microReticulum can run directly on devices already used for Meshtastic and MeshCore, it could significantly accelerate Reticulum’s adoption.

P.S. I found this article on Hacker News while searching for #MeshCore. The discussion there is also interesting:

https://news.ycombinator.com/item?id=48299638

#Mesh #Decentralization

Reticulum has no separate protocol spec; the Python implementation is effectively the reference. But GitHub, PyPI, and RNS-distributed releases may not show the same version.

I documented how I fetched the signed 1.3.7 release over Reticulum itself using rngit, including signer validation and artifacts retrieved.

https://salemdata.net/johnpress/?p=1056

#Reticulum #RNS #LoRa #MeshNetworking #OpenSource #microReticulum

How does a #Reticulum mesh actually behave on #LoRa when messages must traverse multiple transport nodes?

I ran seven GPS-disciplined #TBeamSupreme units running #microReticulum, forced AMY<->GUY traffic through five intermediate nodes, parsed all seven logs into SQLite, and produced a microsecond-scale chronology plus CAD-delay plot. The test exposes forwarding, channel contention, and radio backoff in one trace.

https://salemdata.net/johnpress/?p=1041

#MeshNetworking #ESP32 #OpenSource

@gafu @chris I'm testing 7 #TBeamsupreme units running #microReticulum altered to represent a topology of nodes that are out-range to some in order to force LINK transport across 5 others. I finally ran #openwebrx while conducting these tests so I could see what transmissions were happening when, and that was a real eye opener. I fixed two kinds of flooding (resulting my my artificial constraints) because I had the visualization of what was dominating the air waves.

Trying to build the #microreticulum #reticulum firmware for the heltec 114 so that it can run on my solar node. Not entirely sure why the author doesn't build it. I'm new to the software side. Let's see what happens :')

Dear fedizens

I'm getting into secure resilient decentralised mesh p2p/p4p communication networks.
(Wow, that's a mouthful)

Could y'all give me some advice about relevant tech and hardware?

My primary use case is getting a few thousand people securely connected (messaging, preferably some web services as well) in a large area (hundreds of km²) with rugged terrain.
Eventually the use case will become fairly similar to "neighbourhood-first software", with 100k people across a few thousand km²: https://tv.lumbung.space/w/nzuB248U2LQA1LCn7vYmER

I've watched and read some stuff about #meshtastic, #meshcore and #reticulum, like
this blog post https://www.jonaharagon.com/posts/im-getting-into-mesh-networks-meshtastic-meshcore-and-reticulum
this glorious video https://www.youtube.com/watch?v=W_F4rEaRduk
and #p4panda in this blog post https://lores.tech/blog/example-chat-app/

I'm leaning in favour of reticulum with p4panda on top, but can be convinced otherwise.

What sorta hardware is suitable?
Is #microreticulum functional?
Do you know of any decent guides?

Boosts welcome, cheers!

#fedihelp #fediask #mesh #networking #p2p #p4p #anarchism #digitalAutonomy #localResilienceTech #decentralization #decentralisation #neighbourhoodFirstSoftware

Debugging #microReticulum LINK/transport behavior over LoRa is hard when the “wire” is invisible.

I’m testing BOB, CY & DAN, with DAN acting as the middle node between two units that cannot hear each other directly. To look for possible RF collisions, I modified #OpenWebRX.

It is fuzzy, but it turns millisecond logs and invisible transmissions into something I can actually see.

https://salemdata.net/johnpress/?p=868

#Reticulum #TBeamSupreme #LoRa #ESP32 #EmbeddedSystems #Radio #SDR #OpenSource #AIcoding

Looking at two Rust paths toward #Reticulum: Reticulum-rs, a smaller MIT-licensed library, and Leviculum, a much broader AGPL implementation with a no_std core, daemon/CLI, interop tests, and embedded ambitions.

My practical question: could either help with #ESP32 / #TBeamSupreme transport work, or does #microReticulum still win today?

https://salemdata.net/johnpress/?p=850

#Rust #EmbeddedSystems #LoRa #NoStd #ProtocolDesign

Herding T-Beam Cats: my practical test bench for running 7 LilyGo T-Beam SUPREMEs with PlatformIO, synchronized clocks, serial monitors, structured logs, and Codex-assisted debugging bounded by actual evidence.

https://salemdata.net/johnpress/?p=777

#TBeamSupreme #ESP32 #PlatformIO #Reticulum #microReticulum #EmbeddedSystems #Gentoo #AIcoding #Codex #HardwareHacking

Two $17 Raspberry Pi Zero 2 W boards exchanging encrypted poems over #Reticulum using Bluetooth only -- no LoRa hat, no extra radio, no carrier network.

A small-board demo of #microReticulum in C++ with BLE as the link layer. Cheap hardware, built-in radios, real packets, real timing, real tinkering.

https://salemdata.net/johnpress/?p=720

#RaspberryPi #PiZero2W #Bluetooth #BLE #Linux #SBC #Maker #SmallBoardComputers

Skipping the #TBeamSupreme for this test: two bare #RaspberryPiZero2W boards running #microReticulum with my BLE interface, each sending poetry to the other over their built-in Bluetooth radios.

Two $17 SBCs, 8.8 MB builds, fully secure Reticulum link, and ambidextrous roles: start both, and they decide who is client/server.

#Bluetooth #BLE #Reticulum #RaspberryPi #MeshNetworking

Has anyone made this #ratspeak #reticulum #microreticulum stand-alone work on a #cardputer #m5cardputer #esp32 https://github.com/ratspeak/ratcom ? I did not manage to get any lora radio announces from my extant lora rnode mesh to reach the cardputer nor for any cardputer announces to reach my rnode mesh, even with changes to codebase. (see fix in link below)

Milestone: Torlando’s Python BLE Reticulum protocol behavior has now been partially distilled into a C++ protocol/session core and field-tested between two Raspberry Pi Zero 2Ws. The test moved the full U.S. Constitution both directions over Reticulum using BLE, with C++ fragmentation/session backends confirmed.

https://salemdata.net/johnpress/?p=695

Next stop: microReticulum on the LilyGO T-Beam SUPREME.

#Reticulum #BLE #Bluetooth #microReticulum #TBeamSupreme #LilyGO #RaspberryPi #ESP32 #LoRa #Cplusplus

Going beyond the home lab, today i put up 2 more #reticulum transport nodes with modified #microreticulum firmwares (responding with battery % on msg). I managed to get messages through from about 7km away with 3 hops over LoRa and 1 TCP interface. Obviously the ultimate goal is to send an image at that distance, I but need to fix some bugs on the t-deck firmware because it failed me.

@circfruit Fabulous. A friend made this #varna9000 #microreticulum https://github.com/varna9000/micropython-reticulum work on the Lilygo #T3S3 and he is over the moon. We are dead excited to make these devices run as a complete #lora #standalone #mesh #radio . Thanks so much! Just fabulous. #reticulum

Working toward running #microReticulum natively on the LilyGO T-Beam SUPREME (ESP32-S3 + SX1262).

Hardware exercises complete (GPS, OLED, SD) and basic LoRa ping-pong via RadioLib.

Next: implement a proper Reticulum LoRa interface layer for SX1262 on ESP32-S3 — binding microReticulum’s interface abstraction to SPI/DIO/TCXO for full RNS operation.

Interested in collaborating or testing? #Reticulum #LoRa #ESP32 #TBeam #Meshtastic