LoRaWAN network provisioning¶
Overview¶
Configure the gateway to connect to your LoRaWAN Network Server (LNS). You do this in the Gateway UI, under Settings → Gateway.
Prerequisites¶
- An active LoRaWAN Network Server account
- Access to the Gateway UI
Choose a packet-forwarding mode¶
In the Gateway UI, open Settings → Gateway → Lorawan Gateway Service and choose one:
| Mode | When to use |
|---|---|
basicstation |
Recommended for most LNS platforms (for example The Things Stack). |
udpforwarder |
Semtech UDP packet forwarder, for LNS platforms that expect it. |
relay |
LoRaWAN relay. Beta — configured over SSH with root access (see SSH access). |
Find your gateway identifiers¶
Each forwarding mode has its own EUI, which you register as the gateway's identity in your LNS. The same value is shown under two different names depending on where you look — on the Dashboard and in Settings:
| Forwarding mode | On the Dashboard (Gateway Info) | In Settings (read-only) |
|---|---|---|
| Basic Station | Gateway EUI (used for Basicstation) | Basicstation EUI |
| UDP packet forwarder | Concentrator EUI (used for UDPForwarder) | Forwarder EUI |
Read the value on Dashboard → Gateway Info and register it in your LNS. The matching field in Settings shows the same value and cannot be edited.
UDP packet forwarder setup¶
- Set Settings → Gateway → Lorawan Gateway Service to
udpforwarder. A Forwarder section appears. - Configure the forwarder:
- Region (for example EU868)
- Server Address — your LNS address, as an IP address or a hostname. An IP address is recommended; a hostname works only if the gateway can resolve DNS.
- Server Port Up and Server Port Down
- Keep Alive Interval and Status Interval
- Select Save Changes. The forwarder restarts with the new settings.
Gateway ID for your LNS
The Forwarder EUI in the forwarder settings is read-only (taken from the concentrator). Use it as the gateway EUI when you register the gateway in your LNS.
Adjust the region's radio settings over SSH
Selecting a Region loads a matching global configuration file. If the defaults do not fit your
local regulatory requirements (for example the channel plan), you can edit the file directly over
SSH. The files are in
/data/config/udpforwarder/globalconf/, named global_conf.json.sx1250.<REGION> — for example
global_conf.json.sx1250.EU868. Restart the forwarder (or reboot) after editing.
Basic Station setup (recommended)¶
- Register the gateway in your LNS with:
- Frequency plan for your region (for example EU868)
- Packet forwarder: Semtech Basic Station
- Basicstation EUI: shown read-only in the Basic Station settings (the same value as the Dashboard's Gateway EUI — see Find your gateway identifiers)
- An API key / token and your LNS server URI
- In the Gateway UI, set Settings → Gateway → Lorawan Gateway Service to
basicstation, then select Save Changes. - Finally, under Settings → Basicstation Configuration Files, select Upload New File and add
the files your LNS requires. Give each a configuration name and select the file:
tc.uri— your LNS server URI (for examplewss://eu1.cloud.thethings.network:8887)tc.key— your API key or tokentc.trust— the LNS TLS trust certificatestation.conf,tc.cert, andcups.*files if your LNS uses them
Allowed file types are .conf, .uri, .trust, .key, and .crt, up to 5 MB each and 25 files total.
Uploaded files can be enabled or disabled, downloaded, and deleted individually — or select several with
the checkboxes (or Select all) and remove them at once with Delete Selected.
The gateway should appear as online in your LNS after successful provisioning.
If the service does not come online, see LoRaWAN service does not come online.
Best practices¶
- Before final deployment, open the Dashboard and confirm there is no Gateway Attention Needed banner — it flags any required service (Backhaul, LoRaWAN, VPN) that is down.
- Keep API keys and tokens secure.
- Confirm the gateway shows an online status in your LNS dashboard.
- Use consistent frequency plans across your network.
Next steps¶
- Set up CoHost monitoring for gateway health tracking
- Configure LTE connectivity for cellular backhaul
- Install the gateway at your deployment site