Skip to main content

Dragino LoRaWAN Gateway Setup

This guide provides instructions on how to configure an 8-channel Dragino LoRaWAN gateway such as the LPS8 or DLOS8 to work with the Helium network.

warning

Dragino Hotspots will only mine HNT through packet transfer, and is considered a Data Only Hotspot. The ability to mine HNT with anything other than Approved Hotspots is not currently supported. Please join the #gateway-development channel in the Helium Discord Server for the latest updates.

Video Guide for Setup

Link to YouTube tutorial explaining packet forwarder setup.

Prerequisites

Prior to configuring your Dragino to work with the Helium network, please confirm that it is connected to the Internet and updated to the latest firmware. Refer to the user guide provided on the Dragino download site for more detailed instructions.

  • Connect to a Wi-Fi or Ethernet network with Internet access.
  • Update to the latest firmware from Dragino. As recommended by Dragino, leave "Preserve Settings" unchecked when upgrading firmware to avoid issues caused by incompatibility of settings between versions. This guide assumes the standard firmware version v5.4.1618196981 or later. Earlier firmware versions may require ca-bundle to be installed prior to gateway-rs (via SSH: opkg update and opkg install ca-bundle). Note, the OpenVPN firmware may be used however port numbers may differ from what's included here.
  • Change the root password from the default of 'dragino', if desired.

Configure LoRa Frequency Plan

To be able to send and receive LoRa data, your gateway must be configured to the frequencies specified for your region. You may be able to use the predefined frequency in the Dragino or some cases may need to manually set them per the frequencies used by Helium in your region.

  1. Log into the Dragino gateway web interface. In the standard Dragino firmware connect via your browser at http://<ip_address>:8000 once the Dragino is connected to your network.
  2. Navigate to Lora > Lora from the Menu.
  3. Under Radio Settings, select your region in the Frequency Plan drop down and, if applicable, the Frequency Sub Band. For example, in the US, select US915 for the frequency plan and 2 for the sub band.
  4. If desired, set Static GPS coordinates.
  5. Click Save & Apply.

For some regions, it my be necessary to manually populate Populate the Customized Channel Settings based on the Helium frequencies for your region. Refer to the Helium sample LoRa packet forwarder global.conf files for your region as a guide to the values to use. You can check the values used by the pre-defined frequency plans by viewing the global_conf.json file: cat /etc/lora/global_conf.json

Example of customized channel settings using the US915 frequency plan for Helium

Configure LoRaWAN Settings

Next, you will configure the LoRa packet forwarder on the Dragino to forward packets to the Helium Gateway service which will be installed on the Dragino in the next step.

  1. From the Dragino web interface, navigate to LoRaWAN > LoRaWAN from the menu.
  2. Select Custom / Private LoRaWAN from the Service Provider.
  3. Set the Server Address to 127.0.0.1 and both Uplink and Downlink ports to 1680. This will configure the forwarder to use the default port used by Helium Gateway.
  1. Click Save & Apply.

Install Helium Gateway (gateway-rs) on the Dragino

Finally, you will install the Helium Gateway service. This requires SSH access to the Dragino.

  1. Connect to the Dragino over SSH. By default, the standard Dragino firmware uses port 2222 for SSH (the OpenVPN firmware uses port 22) and the root user has access. ssh root@<ip address> -p 2222
  2. Copy the Helium Gateway package to the Dragino. The latest source code and pre-built releases are available on GitHub. Option 1: Download from GitHub: On the Dragino run cd /tmp and wget -O helium-gateway-<version>-dragino.ipk https://github.com/helium/gateway-rs/releases/download/<version>/helium-gateway-<version>-dragino.ipk. Option 2: Copy from another computer: Run this command from on the computer within the directory containing the package scp helium-gateway-<version>-dragino.ipk <dragino ip>:/tmp/.
  3. Install the Helium Gateway package opkg install /tmp/helium-gateway-<version>-dragino.ipk.
  4. Backup your key file /etc/helium_gateway/gateway_key.bin and keep in a safe place. This will be needed to recover this gateway especially if it is onboarded to the blockchain.

Helium Gateway is now installed and should be running. Use the command helium_gateway key info to view the public key address and animal name of your gateway.

Verify

Your Dragino gateway should now be setup and forwarding LoRaWAN data traffic to the Helium Network.

Through Helium Console

If you have a LoRaWAN device configured through the Helium Console, you should now see it uplinking traffic through the Dragino gateway. You can verify this by turning on your device within range of the Dragino and looking for traffic in Console associated to the Dragino gateway's animal name.

Note, during the alpha period, the helium gateway service by default routes data traffic to the Staging Router/Console.

Through the System Logs

Use the Dragino system log to verify that Helium Gateway has started. You can view the log in the web interface or by using logread on the commandline interface (e.g, logread | grep helium_gateway). In the logs, you should see messages indicating helium_gateway is starting. If you do not see these, try restarting the service (/etc/init.d/helium_gateway restart) or reboot the Dragino as the messages may have rotated out of the log.

Example logs showing the Helium Gateway service starting

Thu Mar 25 19:43:06 2021 daemon.err helium_gateway[2031]: Mar 25 19:43:06.184 INFO starting server, key: <public key>, version: 1.0.0-alpha.4
Thu Mar 25 19:43:06 2021 daemon.err helium_gateway[2031]: Mar 25 19:43:06.289 INFO starting, module: gateway
Thu Mar 25 19:43:06 2021 daemon.err helium_gateway[2031]: Mar 25 19:43:06.306 INFO starting, module: router

Additionally, the LoRa Packet Forwarder log can provide some clues as to whether the LoRaWAN server configuration is correct. Search the system log for PULL_DATA messages and confirm that they are acknowledged such as REPORT~ # PULL_DATA sent: 1 (100.00% acknowledged). This indicates that the packet forwarder is communicating with the Helium Gateway service running on the Dragino and is getting replies from the service as expected. Note, this is not a foolproof way to confirm it is configured correctly. By default, the LoRaWAN Server settings are configured for the TTN EU server which will also provide acknowledgment. However, the absence of acknowledgment could indicate the the LoRaWAN settings are not correct per the above.

Onboard as Data-Only Hotspot

As part of the Light Hotspot project, a new class of Hotspots called "Data-Only Hotspots" can be added to the blockchain, meaning Dragino LPS80/DLOS8 Hotspots can be added to the Network. These Hotspots can mine HNT for transferring data but never for Proof-of-Coverage. See Light Hotspots for more information. This process will require using the Helium command-line interface (CLI) Wallet to submit the onboarding and assert location transactions.

Edit this page