When updating the lora-gateway-bridge on our kerlink gateway from 2.7 to 3.1 we’re only receiving half of the toml file. We updated the gateway like this:
mkdir -p /user/.updates
cd /user/.updates
wget https://artifacts.loraserver.io/vendor/kerlink/ifemtocell/lora-gateway-bridge_3.0.1-r1_klk_wifc.ipk
kerosd -u
reboot
The status of the update can bee seen by following command:
2019.06.06-11:57:26 -- Update Status : updated 1, failed 0 , partial 0 result : OK
But the toml file created stops in the middle and are obviously missing some text:
(#) 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.
(#)
(#) Example (this configuration can be repeated):
(#)
(#) [[backend.semtech_udp.configuration]]
(#) (#) Gateway ID.
(#) (#)
(#) (#) The LoRa Gateway Bridge will only apply the configuration updates for this
(#) (#) gateway ID.
(#) gateway_id=“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"
(#) Integration configuration.
[integration]
(#) Payload marshaler.
(#)
(#) This defines how the MQTT payloads are encoded. Valid options are:
(#) * protobuf: Protobuf encoding (this will become the LoRa Gateway Bridge v3 default)
(#) * json: JSON encoding (easier for debugging, but less compact than ‘protobuf’)
marshaler=“protobuf”
(#) MQTT integration configuration.
[integration.mqtt]
(#) Event topic template.
event_topic_template=“gateway/{{ .GatewayID }}/event/{{ .EventType }}”
(#) Command topic template.
command_topic_template=“gateway/{{ .GatewayID }}/command/#”
(#) MQTT authentication.
[integration.mqtt.auth]
(#) Type defines the MQTT authentication type to use.
(#)
(#) Set this to the name of one of the sections below.
type=“generic”
(#) Generic MQTT authentication.
[integration.mqtt.auth.generic]
(#) MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws)
server="tcp://127.0.0.1:1883"
(#) Connect with the given username (optional)
username=""
(#) Connect with the given password (optional)
password=""
Where can we get the rest? Or maybe this is all there is? Is the lora-gateway-bridge.toml file the same as the one on the server? Then we can just copy the text into this toml file.
