mirror of
https://github.com/thetechprepper/emcomm-tools-os-community.git
synced 2026-09-17 15:41:44 -04:00
thetechprepper
99 lines
3.2 KiB
Plaintext
99 lines
3.2 KiB
Plaintext
# Author : Gaston Gonzalez
|
|
# Date : 16 July 2026
|
|
# Blueprint : Radio-Only Node, transport disabled
|
|
# Purpose : This confguration is a blueprint for a radio-only node.
|
|
# It uses Mercury as the radio interface.
|
|
|
|
[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 = False
|
|
|
|
|
|
# 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
|
|
|
|
# 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
|
|
|
|
|
|
[interfaces]
|
|
|
|
[[Default Interface]]
|
|
type = AutoInterface
|
|
enabled = no
|
|
|
|
# See https://github.com/Rhizomatica/mercury/blob/mercuryv2/docs/RETICULUM.md
|
|
[[Mercury HF]]
|
|
type = TCPClientInterface
|
|
interface_enabled = {{ET_RETICULUM_INTERFACE_MERCURY_ENABLED}}
|
|
kiss_framing = yes
|
|
target_host = 127.0.0.1
|
|
target_port = 8100
|
|
|
|
# Index Mode Payload Rate (bps)
|
|
# 0 DATAC1 980
|
|
# 9 DATAC17 1410 (not yet supported)
|
|
# 10 QAM16C2 3100 (not yet supported)
|
|
bitrate = 980
|