¶ Configure LoRaWAN on a gateway
Modifying the LoRaWAN configuration settings of the gateway may affect the connectivity to the LoRaWAN Network Server (LNS).
Please proceed with caution and ensure that you fully identified the implications before making any modifications.
The constraints associated to the LoRaWAN configuration command are as follows:
▸ The LoRaWAN configuration command is only accessible to users with SERVICE_ADMINISTRATOR and CHANNEL_ ADMINISTRATOR roles
▸ It is not possible to send a new LoRaWAN configuration command if another one is already pending for the same gateway
▸ It is possible to cancel a LoRaWAN configuration command only if it has not yet been sent to the gateway
Configuring Basic Station implies having a minimal version of Basic Station Packet Forwarder installed on the gateway:
▸ Basic Station Packet Forwarder 3.3.0 for a gateway running on KerOS 5
▸ Basic Station Packet Forwarder 4.2.0 for a gateway running on KerOS 6, integrated by default in KerOS 6.3See Gateway requirements for details.
In release 4.9 of Wanesy Management Cockpit, only configuring Basic Station for LNS Server at gateway level is supported.
¶ Gateway requirements
¶ Gateway running on KerOS 5
If your gateway is running on KerOS 5, you need to:
- Install the version Basic Station Packet Forwarder 3.3.0
- Activate the Basic Station Packet Forwarder
¶ Gateway running on KerOS 6
If your gateway is running on KerOS 6, you need to:
- Install the release KerOS 6.3
- Install the package
basicstation, to install the version Basic Station Packet Forwarder 4.2.0 integrated by default in KerOS 6.3 - Install the package
basicstation-credentials-kerlink01, integrated by default in KerOS 6.3 - Activate the Basic Station Packet Forwarder
¶ Basic Station configuration
To configure the LoRaWAN settings of a gateway, you need to go to the Gateway overview page and select LoRaWAN from the CONFIGURATION menu.
This menu redirects to a new dedicated page Gateway LoRaWAN configuration, including two parts:
- The LoRaWAN configuration of the gateway, with possibility to select the LoRaWAN network mode
- The informations related to the last configuration command sent to the gateway (if any)
¶ Mechanism
The feature to configure Basic Station is based on the implementation of a CUPS boot server between the Wanesy Management Center and the gateway.
The mechanism is completely unrelated to the telemetry messages (which are for example used to send a Magic link or a backhaul configuration to the gateway).
The gateway checks for a pending CUPS configuration on server side:
- At startup of Basic Station
- Then each hour in nominal mode
When checking for a pending CUPS configuration on server side, Basic Station notifies the server with the current configuration present on the gateway (if any):
- LNS URI
- CRC of credentials
This mechanism only works if no external CUPS server is configured on the gateway.
The authentication mode and the associated credentials can’t be reported by the gateway for security reason.
¶ Configure Basic Station LNS Server
To configure the Basic Station LNS Server, the following parameters are mandatory:
- LNS URI (mandatory), address of the LNS connection endpoint
- Authentication mode (mandatory), 3 modes are supported
¶ TLS Server and Client Authentication (default)
In this mode, the gateway authenticates the LNS server by establishing a TLS connection, and the server verifies the identity of the gateway by asking for its certificate, as well as a signature with its private key.
The following parameters are mandatory:
- Trust the server’s CA certificate, which enables the gateway to establish trust with the LNS server
- Certificate the gateway certificate
- Key the gateway private key
¶ TLS Server Authentication
In this mode, the gateway authenticates the LNS server by establishing a TLS connection
The following parameter is mandatory:
- Trust the server’s CA certificate, which enables the gateway to establish trust with the LNS server
¶ TLS Server Authentication and Client Token
In this mode, the gateway authenticates the LNS server by establishing a TLS connection, and the server verifies the identity of the gateway by checking a security token provided by the gateway
The following parameters are mandatory:
- Trust the server’s CA certificate, which enables the gateway to establish trust with the LNS server
- Token contained in one or more HTTP header fields, with the possibility to upload a token file or to manually enter the fields
¶ Sending LoRaWAN configuration to the gateway
After clicking on SEND CONFIGURATION button, you will be asked to confirm in a popup.
Once triggered, the LoRAWAN configuration command will be sent to the gateway when the next Basic Station CUPS exchange is done.
When a LoRaWAN configuration command is pending (waiting to be sent to the gateway):
- The LoRaWAN configuration displayed is the expected one
- An orange dot next to the
LoRaWANentry in theCONFIGURATIONmenu - The total number of pending actions (including configuration and software update) in the
CONFIGURATIONmenu - A status badge with the total number of pending actions (including configuration and software update) in gateway list (with filtering option)
Depending on its progress, the LoRaWAN configuration command goes through different possible statuses:
- Created: the command has been created
- Pending: the command is ready to be sent to the gateway
- Sent: the command has been sent to the gateway
- Cancel request: the cancellation of the command has been requested
- Cancelled: the command has been cancelled
To cancel the LoRaWAN configuration command, you need to click on the CANCEL CONFIGURATION button present in the Last configuration sent block.
The following informations related to the last LoRaWAN configuration command sent to the gateway are displayed in the Last configuration sent block:
- The creation date of the command
- The application date of the command (corresponding to the date when it was sent to the gateway, in response to the receipt of a telemetry message)
- The content of the command sent (displayed in a popup when clocking on the eye link)
- The status of the command
¶ Receiving LoRaWAN configuration from the gateway
10 seconds after the configuration update, Basic Station recontacts the CUPS boot server to notify it with LNS URI and CRC of credentials.
The configuration received from the gateway is compared to the configuration previously sent and a message indicates if the configuration is up to date or not.
