diff options
Diffstat (limited to 'net-p2p/reticulum/files/config.sample')
-rw-r--r-- | net-p2p/reticulum/files/config.sample | 57 |
1 files changed, 49 insertions, 8 deletions
diff --git a/net-p2p/reticulum/files/config.sample b/net-p2p/reticulum/files/config.sample index cc9dc03ac02e..2cb199d49829 100644 --- a/net-p2p/reticulum/files/config.sample +++ b/net-p2p/reticulum/files/config.sample @@ -4,7 +4,7 @@ [reticulum] -# Define the DB directory +# Define database directory dbdir = "/var/db/reticulum" # If you enable Transport, your system will route traffic @@ -31,12 +31,24 @@ share_instance = Yes # If you want to run multiple *different* shared instances # on the same system, you will need to specify different -# shared instance ports for each. The defaults are given -# below, and again, these options can be left out if you -# don't need them. +# instance names for each. On platforms supporting domain +# sockets, this can be done with the instance_name option: -shared_instance_port = 37428 -instance_control_port = 37429 +instance_name = default + +# Some platforms don't support domain sockets, and if that +# is the case, you can isolate different instances by +# specifying a unique set of ports for each: + +# shared_instance_port = 37428 +# instance_control_port = 37429 + + +# If you want to explicitly use TCP for shared instance +# communication, instead of domain sockets, this is also +# possible, by using the following option: + +# shared_instance_type = tcp # On systems where running instances may not have access @@ -50,13 +62,25 @@ instance_control_port = 37429 # rpc_key = e5c032d3ec4e64a6aca9927ba8ab73336780f6d71790 +# It is possible to allow remote management of Reticulum +# systems using the various built-in utilities, such as +# rnstatus and rnpath. You will need to specify one or +# more Reticulum Identity hashes for authenticating the +# queries from client programs. For this purpose, you can +# use existing identity files, or generate new ones with +# the rnid utility. + +# enable_remote_management = yes +# remote_management_allowed = 9fb6d773498fb3feda407ed8ef2c3229, 2d882c5586e548d79b5af27bca1776dc + + # You can configure Reticulum to panic and forcibly close # if an unrecoverable interface error occurs, such as the # hardware device for an interface disappearing. This is # an optional directive, and can be left out for brevity. # This behaviour is disabled by default. -panic_on_interface_error = No +# panic_on_interface_error = No # When Transport is enabled, it is possible to allow the @@ -67,7 +91,7 @@ panic_on_interface_error = No # Transport Instance, and printed to the log at startup. # Optional, and disabled by default. -respond_to_probes = No +# respond_to_probes = No [logging] @@ -209,6 +233,23 @@ loglevel = 4 # Serial port for the device port = /dev/ttyUSB0 + # It is also possible to use BLE devices + # instead of wired serial ports. The + # target RNode must be paired with the + # host device before connecting. BLE + # devices can be connected by name, + # BLE MAC address or by any available. + + # Connect to specific device by name + # port = ble://RNode 3B87 + + # Or by BLE MAC address + # port = ble://F4:12:73:29:4E:89 + + # Or connect to the first available, + # paired device + # port = ble:// + # Set frequency to 867.2 MHz frequency = 867200000 |