LoRaWAN network provisioning¶
Overview¶
Configure your SenArch ARCH-1 LoRaWAN Gateway to connect to your LoRaWAN Network Server (LNS).
Prerequisites¶
- Active LoRaWAN Network Server account
- SSH access to gateway for configuration
Gateway configuration¶
Choose between Basic Station (recommended) or LoRa Packet Forwarder configuration modes.
Basic Station setup¶
- Connect to your gateway via SSH and retrieve the Gateway EUI:
cat /data/info.json
- Locate the WLAN Address entry:
"WLAN Address": "b82...b3e"
Use this value as your Gateway EUI in your LNS registration.
- Register the gateway in your LNS with these settings:
- Frequency plan: Your region (e.g., EU868)
- Packet Forwarder: Semtech Basic Station
- Network Server address: Your LNS URI
- Authentication: API key or token from your LNS
- Update configuration files in
/data/basicstation/:
tc.key: Paste your API key/tokentc.uri: Paste your LNS URI (e.g.,wss://eu1.cloud.thethings.network:8887)tc.trust: TLS certificate (e.g., Let's Encrypt)
The gateway should appear as Online in your LNS after successful provisioning.
Semtech UDP Packet Forwarder setup¶
- Open the gateway configuration file:
nano /data/gateway-conf.json
- Enable UDP Packet Forwarder mode, and configure the following parameters. When the changed file is written to disk, the gateway will reboot using the new parameters.
"gateway_service": "lora_pkt_fwd"
"region": "EU868",
"LPF_gateway_ID": "001...681",
"LPF_server_address": "1.1.1.1",
"LPF_serv_port_up": 1700,
"LPF_serv_port_down": 1700,
"LPF_keepalive_interval": 30,
"LPF_stat_interval": 30
- If the
LPF_gateway_IDdoesn't appear automatically, obtain it manually:
/opt/bin/gateway/chip_id.sh
Ensure LPF_server_address matches your LNS server address.
Best practices¶
- Keep all keys and API tokens secure
- Verify gateway shows online status in your LNS dashboard
- Use consistent frequency plans across your network
Next steps¶
- Set up co-host monitoring for gateway health tracking
- Configure LTE connectivity for cellular backhaul
- Install the gateway at your deployment site