# debug=5, info=4, warning=3, error=2, fatal=1, panic=0 log_level = 4 # Configuration which relates to the packet-forwarder. [packet_forwarder] # ip:port to bind the UDP listener to # # Example: 0.0.0.0:1700 to listen on port 1700 for all network interfaces. # This is the listeren to which the packet-forwarder forwards its data # so make sure the 'serv_port_up' and 'serv_port_down' from your # packet-forwarder matches this port. udp_bind = "localhost:1700" # Skip the CRC status-check of received packets # # This is only has effect when the packet-forwarder is configured to forward # LoRa frames with CRC errors. skip_crc_check = false # # Managed packet-forwarder configuration. # # # # By configuring one or multiple managed packet-forwarder sections, the # # LoRa Gateway Bridge updates the configuration when the backend receives # # a configuration change, after which it will restart the packet-forwarder. # [[packet_forwarder.configuration]] # # Gateway MAC. # # # # The LoRa Gateway Bridge will only apply the configuration updates for this # # gateway MAC. # mac="0102030405060708" # # Base configuration file. # # # # This file will be used as base-configuration and will not be overwritten on # # a configuration update. This file needs to exist and contains the base # # configuration and vendor specific # base_file="/etc/lora-packet-forwarder/global_conf.json" # # Output configuration file. # # # # This will be the final configuration for the packet-forwarder, containing # # a merged version of the base configuration + the requested configuration # # update. # # Warning: this file will be overwritten on a configuration update! # output_file="/etc/lora-packet-forwarder/local_conf.json" # # Restart command. # # # # This command is issued by the LoRa Gateway Bridge on a configuration # # change. Make sure the LoRa Gateway Bridge process has sufficient # # permissions to execute this command. # restart_command="/etc/init.d/lora-packet-forwarder restart" # Configuration for the MQTT backend. [backend.mqtt] # MQTT topic templates for the different MQTT topics. # # The meaning of these topics are documented at: # https://docs.loraserver.io/lora-gateway-bridge/use/data/ # # The default values match the default expected configuration of the # LoRa Server MQTT backend. Therefore only change these values when # absolutely needed. # Use "{{ .MAC }}" as an substitution for the LoRa gateway MAC. uplink_topic_template="gateway/{{ .MAC }}/rx" downlink_topic_template="gateway/{{ .MAC }}/tx" stats_topic_template="gateway/{{ .MAC }}/stats" ack_topic_template="gateway/{{ .MAC }}/ack" config_topic_template="gateway/{{ .MAC }}/config" # MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws) server="tcp://192.168.0.255:1883" # Connect with the given username (optional) username="loragw" # Connect with the given password (optional) password="62374838" # Quality of service level # # 0: at most once # 1: at least once # 2: exactly once # # Note: an increase of this value will decrease the performance. # For more information: https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels qos=0 # Clean session # # Set the "clean session" flag in the connect message when this client # connects to an MQTT broker. By setting this flag you are indicating # that no messages saved by the broker for this client should be delivered. clean_session=true # Client ID # # Set the client id to be used by this client when connecting to the MQTT # broker. A client id must be no longer than 23 characters. When left blank, # a random id will be generated. This requires clean_session=true. client_id="loragw" # CA certificate file (optional) # # Use this when setting up a secure connection (when server uses ssl://...) # but the certificate used by the server is not trusted by any CA certificate # on the server (e.g. when self generated). ca_cert="" # mqtt TLS certificate file (optional) tls_cert="" # mqtt TLS key file (optional) tls_key=""