██████ ██████ ███████████ █████ █████ █████████
▒▒██████ ██████ ▒▒███▒▒▒▒▒███▒▒███ ▒▒███ ███▒▒▒▒▒███
▒███▒█████▒███ ▒███ ▒███ ▒███ ▒███ ███ ▒▒▒
▒███▒▒███ ▒███ ▒██████████ ▒███ ▒███ ▒███
▒███ ▒▒▒ ▒███ ▒███▒▒▒▒▒███ ▒███ ▒███ ▒███ █████
▒███ ▒███ ▒███ ▒███ ▒███ ▒███ ▒▒███ ▒▒███
█████ █████ ███████████ ▒▒████████ ▒▒█████████
▒▒▒▒▒ ▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒
Mesh Brisbane Users Group
Network Basics
Reticulum Network Building tips
Thanks for popping in on the reticulum network.
The network will be as useful as you want it to be/make it to be. The easiest and most useful place to begin making connectivity is between your own devices.
This means the creation of a Transport Node. What is the difference between a transport node and a regular peer? it's the below setting in .reticulum/config -
[reticulum]
# If you enable Transport, your system will route traffic
# for other peers, pass announces and serve path requests.
# This should only be done for systems that are suited to
# act as transport nodes, ie. if they are stationary and
# always-on. This directive is optional and can be removed
# for brevity.
enable_transport = True
The machine you enable this on should be the one you intend to connect to the most interfaces.
Interface types
Auto Interface - AutoInterface facilitates communication with other discoverable Reticulum nodes over any kind of local Ethernet or WiFi without requiring any other network infrastructure. If firewalls are present on the machine it must allow through UDP ports 29716 and 42671 for this to function. This is the interface that will feed your local network.
RNode - RNode LoRa interface, usually connected either through usb, bluetooth low energy, or wifi.
For Brisbane the commonly used distance settings for RNodes are the below.
Frequency - 925.875Mhz
Bandwidth - 250000
Spread factor - 9
Coding rate - 4:5
This is easily entered using a program like NomadNet. If entering the interface directly into the reticulum config file it would look similar to the below assuming a USB connection on a linux machine.
[[RNodeMediumFast]]
type = RNodeInterface
interface_enabled = True
port = /dev/ttyACM0
frequency = 925875000
txpower = 22
bandwidth = 250000
spreadingfactor = 9
codingrate = 5
outgoing = True
mode = internal
announce_cap = 2.0
name = RNodeMediumFast
selected_interface_mode = 1
configured_bitrate = None
You may wonder what some of these other settings are, we'll cover some of them later.
Backbone Interface / TCPClient Interface - These interfaces connect over IP networks as a medium to pass reticulum traffic to a specific instance.
There are plentiful backbone interfaces with lots of connectivity available.
Interface Modes
How do I stop the fat tcp backbone from announce flooding my RNode interface to it's set limit you ask? Interface modes.
By setting the well connected internet backbone as "boundary" and the RNode as "internal" it will stop the propagation of announcements from the internet side to the local LoRa Network. Traffic can still go between them should it be requested and paths resolved.
Regular non-transport end points should in almost all cases use the regular "full" mode which is the default setting.