mirror of
https://github.com/thetechprepper/emcomm-tools-os-community.git
synced 2026-09-17 15:41:44 -04:00
thetechprepper
163 lines
4.8 KiB
Plaintext
163 lines
4.8 KiB
Plaintext
# This is the default Reticulum config file.
|
|
# You should probably edit it to include any additional,
|
|
# interfaces and settings you might need.
|
|
|
|
# Only the most basic options are included in this default
|
|
# configuration. To see a more verbose, and much longer,
|
|
# configuration example, you can run the command:
|
|
# rnsd --exampleconfig
|
|
|
|
|
|
[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
|
|
|
|
|
|
# By default, the first program to launch the Reticulum
|
|
# Network Stack will create a shared instance, that other
|
|
# programs can communicate with. Only the shared instance
|
|
# opens all the configured interfaces directly, and other
|
|
# local programs communicate with the shared instance over
|
|
# a local socket. This is completely transparent to the
|
|
# user, and should generally be turned on. This directive
|
|
# is optional and can be removed for brevity.
|
|
|
|
share_instance = Yes
|
|
|
|
|
|
# If you want to run multiple *different* shared instances
|
|
# on the same system, you will need to specify different
|
|
# instance names for each. On platforms supporting domain
|
|
# sockets, this can be done with the instance_name option:
|
|
|
|
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
|
|
|
|
|
|
# You can configure whether Reticulum should discover
|
|
# available interfaces from other Transport Instances over
|
|
# the network. If this option is enabled, Reticulum will
|
|
# collect interface information discovered from the network.
|
|
|
|
# discover_interfaces = No
|
|
|
|
|
|
# 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
|
|
|
|
|
|
# If you're connecting to a large external network, you
|
|
# can use one or more external blackhole list to block
|
|
# spammy and excessive announces onto your network. This
|
|
# funtionality is especially useful if you're hosting public
|
|
# entrypoints or gateways. The list source below provides a
|
|
# functional example, but better, more timely maintained
|
|
# lists probably exist in the community.
|
|
|
|
# blackhole_sources = 521c87a83afb8f29e4455e77930b973b
|
|
|
|
|
|
[logging]
|
|
# Valid log levels are 0 through 7:
|
|
# 0: Log only critical information
|
|
# 1: Log errors and lower log levels
|
|
# 2: Log warnings and lower log levels
|
|
# 3: Log notices and lower log levels
|
|
# 4: Log info and lower (this is the default)
|
|
# 5: Verbose logging
|
|
# 6: Debug logging
|
|
# 7: Extreme logging
|
|
|
|
loglevel = 4
|
|
|
|
|
|
# The interfaces section defines the physical and virtual
|
|
# interfaces Reticulum will use to communicate on. This
|
|
# section will contain examples for a variety of interface
|
|
# types. You can modify these or use them as a basis for
|
|
# your own config, or simply remove the unused ones.
|
|
|
|
[interfaces]
|
|
|
|
# This interface enables communication with other
|
|
# link-local Reticulum nodes over UDP. It does not
|
|
# need any functional IP infrastructure like routers
|
|
# or DHCP servers, but will require that at least link-
|
|
# local IPv6 is enabled in your operating system, which
|
|
# should be enabled by default in almost any OS. See
|
|
# the Reticulum Manual for more configuration options.
|
|
|
|
[[Default Interface]]
|
|
type = AutoInterface
|
|
enabled = Yes
|
|
|
|
[[Packet Radio AX25 KISS]]
|
|
type = AX25KISSInterface
|
|
enabled = Yes
|
|
|
|
callsign = {{ET_CALLSIGN}}
|
|
ssid = 1
|
|
|
|
port = /tmp/kisstnc
|
|
mtu = 256
|
|
|
|
[[RNode LoRa Interface]]
|
|
type = RNodeInterface
|
|
enabled = yes
|
|
|
|
# Connect via Wi-Fi
|
|
port = tcp://192.168.8.167
|
|
|
|
# # Add PnP support: /dev/et-lora
|
|
# port = /dev/ttyACM1
|
|
|
|
|
|
# Set frequency to 915 MHz
|
|
frequency = 915000000
|
|
|
|
# Set LoRa bandwidth to 125 KHz
|
|
bandwidth = 125000
|
|
|
|
# Set TX power in dBm
|
|
# 7 dBm = 5 mW
|
|
# 17 dbm =
|
|
# 22 dbm =
|
|
txpower = 17
|
|
|
|
# Select spreading factor 8. Valid
|
|
# range is 7 through 12, with 7
|
|
# being the fastest and 12 having
|
|
# the longest range.
|
|
spreadingfactor = 9
|
|
|
|
# Select coding rate 5. Valid range
|
|
# is 5 throough 8, with 5 being the
|
|
# fastest, and 8 the longest range.
|
|
codingrate = 5
|