Which DEB package for Raspbian on Pi 3 Model B

ChirpStack Gateway Bridge
1

Lora Gateway Bridge, has a number of Debian / Ubuntu packages.
Which one do I use on a Raspbian Pi 3 Model B?
armv5, or armv6, or armv7, or arm64?
I think that arm64 is not to be used as my research seems to indicate that Raspbian is still 32 bit.
Can I use sudo install lora-gateway-bridge, and get the correct version installed on my Raspberry Pi 3 Model B?
Kindly provide guidance.

2

Have you tried adding the Debian / Ubuntu repository and then just apt install ...?

https://www.loraserver.io/guides/debian-ubuntu/#setup-lora-server-software-repository

3

Yes, of course.

I had followed your Quickstart on Debian or Ubuntu procedure three times, and each time, I get,

Jul 06 11:22:36 wiriots00 lora-gateway-bridge[13952]: time="2019-07-06T11:22:36-04:00" level=error msg="apply gateway-configuration error" error="gateway does not exist"

I have already asked for help with the lora-gateway-bridge on the server and one person responded that pointed me to the setup for a Managed Packet Forwarder, which means to run the lora-gateway-bridge on the gateway.

My question was with regard to the instructions on this page.

Your provided link says,
Note: when you intent to run the LoRa Gateway Bridge only on the gateways itself, you can skip this step.

But that was not the case, three times I tried to run the lora-gateway-bridge on the sever without success.

4

Now I am totally confused.
I disabled and then purged lora-gateway-bridge from the server.
I apt install lora-gateway-bridge on my Raspberry Pi 3 Model B, Sandobx Electronics Gateway that already has,

I now get,
Jul 07 21:22:42 wiriotg00 lora-gateway-bridge[6185]: time="2019-07-07T21:22:42-04:00" level=error msg="apply gateway-configuration error" error="load config file error: read file error: open : no such file or directory"
and that is crazy, cause here is the directory output,
root@wiriotg00:/opt/gateway/bin# ls -al
total 24
drwxr-xr-x 2 root root 4096 Jul 7 21:03 .
drwxr-xr-x 5 root root 4096 Jun 23 00:22 …
-rw-r–r-- 1 root root 6203 Jun 23 13:41 global_conf.json
-rw-r–r-- 1 root root 283 Jul 7 21:03 local_conf.json
lrwxrwxrwx 1 root root 55 Jun 23 00:22 lora_pkt_fwd -> /opt/gateway/packet_forwarder/lora_pkt_fwd/lora_pkt_fwd
-rwxr-xr-x 1 root root 932 Jun 23 00:22 start.sh
root@wiriotg00:/opt/gateway/bin#
and here is my lora-gateway-bridge.toml file,
This configuration provides a Semtech UDP packet-forwarder backend and
# integrates with a MQTT broker. Many options and defaults have been omitted
# for simplicity.
#
# See https://www.loraserver.io/lora-gateway-bridge/install/config/ for a full
# configuration example and documentation.

Э"]1  P   # Gateway backend configuration.
[backend]
# Backend type.
type="semtech_udp"Э"]1     

  # Semtech UDP packet-forwarder backend.
  [backend.semtech_udp]

  # 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 = "0.0.0.0:1700"

    # 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.
    #
    # 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="0004a30b0022813c"

    # # Base configuration file.
   Э"]9N      # #
    # # 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="/opt/gateway/bin/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="/opt/gateway/bin/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="sudo systemctl restart gateway"

# Integration configuration.
[integration]
# Payload marshaler.
#
# This defines how the MQTT payloadsЭ"]CЛ      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://192.168.126.150:1883"

    # Connect with the given username (optional)
    username=""

    # Connect with the given password (optional)
    password=""

root@wiriotg00:/Э"]од     etc/lora-gateway-bridge#
5 
     [[backend.semtech_udp.configuration]]
    # # Gateway ID.
    # #
    # # The LoRa Gateway Bridge will only apply the configuration updates for this
    # # gateway ID.
     gateway_id="0004a30b0022813c"

    # # 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="/opt/gateway/bin/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="/opt/gateway/bin/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="sudo systemctl restart gateway"

I think the error makes sense. Note that your base_file, output_file and restart_command are commented out :wink:

Since you’re one of the few setting up the managed configuration / using the Gateway Profile, I’m looking forward to your feedback on (please comment in that topic): https://forum.loraserver.io/t/who-is-using-the-gateway-profile-how-are-you-using-it/5091.

6

With Sheepish grin and increasingly red face, I knew that.
I should never do this stuff late at night, rather, I should stumble around in the daylight instead.
I adjusted the target file permissions to ugo+rw.
Now working on another intermittent error,
Jul 08 11:01:12 wiriotg00 lora-gateway-bridge[469]: time="2019-07-08T11:01:12-04:00" level=error msg="integration/mqtt: connection error" error="Network Error : dial tcp 192.168.126.150:1883: connect: network is unreachable"
I am sorry that I forgot to un-comment those entries in lora-gateway-bridge.toml last night.