Networking Conduits

Multiple Gateway Deployments


A network of Conduits can be created with several setup as packet forwarder and one as a central network server.
This configuration can be used to increase the area of the network or the number of channels supported. The capacity of the network will still be limited to a single instance of the network server, 2000 end-devices in default configuration.

The /var/config directory is limited to 8 MB. Custom applications may also be installed in the /var/config directory reducing the space available for the database. To reach 2000 connected end-devices it may be necessary to install an SD card to hold the custom application or network server database.



LoRaWAN-Network

AEP Configuration

On Network Server Conduit

The central network server will handle all end-device session information, authenticate uplinks and author downlink packets.

Configure Network Server to accept connections from remote packet forwarders

  1. Go to LoRaWAN > Network Settings on Conduit
  2. Set Public LoRaWAN under Network section, if a private setting is selected all packet forwarders should also be set to private
  3. Click Show Advanced Settings
  4. Under Server Ports verify Local Only is unchecked to allow incoming connections from the packet forwarder Conduits.
  5. Click Submit
  6. Go to Firewall > Settings
  7. Enable Allow Inbound Input Filter Rule, change allowed ports to 1780 and 1782
  8. Save and Restart Conduit

Configure Forwarding Conduit to send packets to the Network Server

  1. Go to LoRaWAN > Network Settings
  2. Enable Packet Forwarder mode
  3. Set Public under Basics section, or match setting selected on Network Server config above.
  4. In Server section, settings must match those of Master Conduit
    1. Set Server Address to IP address
    2. Set Upstream Port to 1780
    3. Set Downstream Port to 1782
  5. Click Submit
  6. Save and Restart Conduit

After the Conduits have rebooted, navigate to the LoRaWAN > Gateways page on the first Conduit. The Forwarding Gateway should now be shown in the list. The IP address of the forwarding Conduit will be listed. Packet forwarders running on the same Conduit as the Network Server will have a local address (127.0.0.1).




Extending Supported Channels for US915 and AU915 Channel Plans


Additional channels can be supported by the network by enabled different Frequency Sub-Band settings on each forwarding Gateway. The supported channels must be relayed to the Network Server using the Channel Mask setting. This will allow the full set of channels to be enabled on the end-device following that OTAA join.

LoRaWAN-Network-USAU

On a Forwarding Conduit

  1. Go to LoRaWAN > Network Settings
  2. Set the Frequency Sub-Band to the desired setting
  3. Click Submit
  4. Save and Restart the Conduit
  5. Configure the other forwarding Conduits likewise

Configure Network Server to support additional channels

  1. 1. Go to LoRaWAN > Network Settings on Conduit
  2. Set channel mask to enable the additional channels
    • FSB 1, 2 and 3 – 00070000000000FFFFFF
    • FSB 1, 2, 3 and 4 – 000F00000000FFFFFFFF
    • FSB 5, 6, 7 and 8 – 00F0FFFFFFFF00000000
    • FSB 1 and 8 – 0081FF000000000000FF
  3. Click Submit
  4. Save and Restart the Conduit




mLinux Configuration


mLinux installations running the Network Server can be configured as well. Note: The mLinux images do not have a firewall enabled by default.

Allow the Network Server to accept incoming connections

  1. Edit the configuration page
    # vi /var/config/lora/lora-network-server.conf
  2. Configure “udp” => “allowPublic” to true
  3. Save the file, enter ‘:x’
  4. Restart the network server,
    # /etc/init.d/lora-network-server restart
    1. Now the UDP ports are set to listen on the external IP interfaces.

      Configure the packet forwarding Conduits

      1. Setup the packet fowarder to send packets to the Network Server Conduit IP address and Ports
      2. See Convert to Basic Packet Forwarder