Mirror/markqvist___Reticulum
1
0
Fork 0
mirror of https://github.com/markqvist/Reticulum.git synced 2026-04-27 22:25:37 +00:00
Code Issues Projects Releases Packages Wiki Activity

Updated Frequently Asked Questions (markdown)

markqvist 2025-05-19 12:40:15 +02:00
commit d1ce3da2c2
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
Frequently-Asked-Questions.md

@ -90,7 +90,9 @@ Nothing. This is a matter for local authorities, be it law enforcement or the pr
## What are the system requirements for running a Reticulum node?
This varies significantly and is becoming far more consistent. Most Pi-like SBCs can run the network stack and a node without issue, although the Gen 1 and Zeroes tend to require manual compilation of the crypto libraries or a less secure pure-Python implementation. Through experimentation, a major node can run on a single core in the GHz class with about 780 MB of RAM. This includes file transfer and other capability, but this is application specific, as Reticulum can load a file and transfer it, requiring the file be loaded into RAM, or stream it directly with a much lower overhead. At time of writing, major nodes are running on a 2 gig VM, a Pi 4, and a 2 gig Le Potato.
This varies significantly and is becoming far more consistent. Most Pi-like SBCs can run the network stack and a node without issue, although the Gen 1 and Zeroes tend to require manual compilation of the crypto libraries or a less secure pure-Python implementation. Through experimentation, a major node can run on a single core in the GHz class with about 780 MB of RAM. This includes file transfer and other capability, but this is application specific, as Reticulum can load a file and transfer it, requiring the file be loaded into RAM, or stream it directly with a much lower overhead. At time of writing, major nodes are running on a 2 gig VM, a Pi 4, and a 2 gig Le Potato.
Recent improvements (post version `0.9.5` of Reticulum) has significantly improved memory consumption for both the core stack and Reticulum-based applications, and as an example, a major node handling more than 300 interfaces, and an average of 1000 active links at any given time currently uses about 250 megabytes of RAM. An LXMF propagation node with 50 connected peers, handling around 2 million messages per month will use around 280 megabytes of RAM.
A pure router written in C for microcontrollers is under development, but does not currently support all features of the network stack.