LoRaWAN
The LoRaWAN configuration page controls the SubG (868 MHz / 915 MHz) packet forwarder.
Hardware requirement
This section is only visible in Cockpit when a LoRaWAN SubG EdgeCard is installed in one of the Edge Slots and has been detected. If no card is present or the slot is powered off, this section will not appear.
Applicable cards:
| Card | Frequency |
|---|---|
| EDGE-GWC-02-LW-868 | EU 868 MHz |
| EDGE-GWC-02-LW-915 | US 915 MHz |
Gateway EUI
The Gateway EUI defaults to an EUI derived from the device MAC address. It can be overridden manually if your LoRaWAN Network Server requires a specific value. Use the auto-derived value unless you have a specific reason to change it.
Forwarder Type
Select the packet forwarder mode:
| Mode | Description |
|---|---|
| Semtech UDP | Legacy UDP packet forwarder. Compatible with most LoRaWAN Network Servers. |
| Basics Station | Modern WebSocket-based forwarder. Supports LNS and CUPS protocols with TLS. |
Semtech UDP Forwarder
| Parameter | Description | Default |
|---|---|---|
| Region | Regional frequency plan. Only regions supported by the installed card are available as options. Currently EU868 is supported on the EDGE-GWC-02-LW-868. | — |
| Server Address | LoRaWAN Network Server hostname or IP | — |
| Server Port | UDP port of the Network Server | 1700 |
| Sub-band | Frequency sub-band FSB1–FSB8 (US915 only) | — |
Basics Station
Basics Station supports two independent server connections: LNS (LoRaWAN Network Server) and CUPS (Configuration and Update Server). They serve different roles and can be enabled independently or together.
Typical usage:
- CUPS only: The recommended approach for most deployments. CUPS contacts the configuration server, which pushes the LNS credentials and connection details to the gateway automatically. No manual LNS configuration is needed.
- LNS only: The gateway connects directly to the LNS using the credentials provided here. No automatic configuration update is performed.
- CUPS + LNS: The gateway contacts CUPS first. If CUPS provides updated LNS credentials, those are used. If CUPS is unreachable or does not supply LNS configuration, the manually configured LNS settings serve as fallback.
LNS Connection
| Parameter | Description | Default |
|---|---|---|
| Enable LNS | Enable the LNS connection | — |
| Server Address | LNS WebSocket server hostname | — |
| Server Port | LNS server port | 8887 |
| TLS Mode | Authentication mode (see TLS Modes) | No TLS |
| Device Token | Token string for server+token authentication | — |
| CA Certificate | Server CA certificate in PEM format | — |
| Device Certificate | Gateway certificate in PEM format | — |
| Device Key | Gateway private key in PEM format | — |
CUPS Connection
| Parameter | Description | Default |
|---|---|---|
| Enable CUPS | Enable the CUPS connection | — |
| Server Address | CUPS server hostname | — |
| Server Port | CUPS server port | 443 |
| TLS Mode | Authentication mode (see TLS Modes) | No TLS |
| Device Token | Token string for server+token authentication | — |
| CA Certificate | Server CA certificate in PEM format | — |
| Device Certificate | Gateway certificate in PEM format | — |
| Device Key | Gateway private key in PEM format | — |
TLS Modes
| Mode | Description |
|---|---|
| No TLS | Unencrypted WebSocket connection |
| Server only | Server identity verified using CA certificate |
| Mutual TLS | Both server and gateway authenticated with certificates |
| Server + Token | Server verified by CA cert; gateway authenticated by token |
Note
Certificates must be uploaded in PEM format.
Tokens and keys after saving
After saving, token and key fields are shown empty for security reasons. The stored values are not lost — they remain active on the device until you explicitly enter and save a new value.