The LORIOT Packet Forwarder allows you to connect to the LORIOT Network Server.

There is not much configuration to do as it will automatically find most of the configuration on the server side. The only configurable parameters are related to the connection.

The packet forwarder can be used in combination with the official Cloud (infrastructure as a service) or for with your own infrastructure (on premise).

Connection

Connect to the LORIOT Cloud

Automatic server detection

By default, the forwarder will try to auto-detect on which server the gateway is registered. To do so, it goes through a list of server and connects to each of them so check if the gateway is registered.

This list is actually exhaustive, but it may grow and the forwarder needs to be updated to get the new list. The forwarder will be updated through the system upgrades.

Manual server configuration

When the server is manually configured, the forwarder will only try to connect to the defined server. The time to be connected will be a little faster, depending on which server you are.

Connect to your private LORIOT Server

When connection to your own server, you will need to configure manually the server where to connect as the address is part of your infrastructure.

Configuration

The forwarder has to be configured through the program arguments on start time. It's the Process Monitor (pmonitor) who starts the packet forwarders.

To change the start arguments, configure the pmonitor's LORIOT service file:

sudo nano /etc/pmonitor/services-available/loriot-packet-forwarder.yml
CODE

You can add any supported argument at the program-arguments line. To see which arguments are supported, please check the official LORIOT documentation.

Network Server configuration

The server can be easily configured through the GUI:

To add the server address and the port to the service configuration, use -s and -p. 

sudo nano /etc/pmonitor/services-available/loriot-packet-forwarder.yml
CODE

Example:

LORIOT service configuration

description: LORIOT Packet Forwarder
autostart: true
log: true
jobs:
    forwarder:
        description: The forwarder
        process:
            run-mode: exec
            program-path: /opt/loriot/loriot-pkt-fwd
            program-arguments: -f -s antartic.loriot.io -p 443
            delays:
                start: 5000
                term: 10000
                restart: 5000
YML

The information you see in the GUI are directly read from this file. You can therefore change the config through the GUI or manually at any time.

Certificate configuration

To specify the certificate of your private server:

  1. Upload the server to the gateway to the following folder
    /etc/opt/loriot-packet-forwarder (create the folder)
  2. Add the certificate path as -c argument of the service:
sudo nano /etc/pmonitor/services-available/loriot-packet-forwarder.yml
CODE

LORIOT service configuration

description: LORIOT Packet Forwarder
autostart: true
log: true
jobs:
    forwarder:
        description: The forwarder
        process:
            run-mode: exec
            program-path: /opt/loriot/loriot-pkt-fwd
            program-arguments: -f -s loriot.your-company.com -p 6644 -c /etc/opt/loriot-packet-forwarder/loriot.your-company.com.crt
            delays:
                start: 5000
                term: 10000
                restart: 5000
YML

The certificate can be configured from the CLI only, for the moment...