Skip to content

[Kerlink iStation] Forwarding LoRa packets to TTN

Sébastien Jean edited this page Apr 24, 2024 · 2 revisions

The following describes how to forward LoRa packet to TTN, by configuring the Packet Forwarder.

Useful resources

Preamble

The gateway used is a Wirnet iStation 868, connected to a LAN/WAN using a 48V/30W PoE Adapter (gateway requires less than 9W).

Gateway EUI is 7076FF00560503F6, so short id (refering to CPU, ...) is 0503F6, ip address is 192.168.1.199

Opening a connection to the gateway

This step requires a web browser on a machine connected to the same LAN.

Using a terminal and an SSH client, open a SSH connection to the gateway:

sebastienjean@Air-SebJ-6 ~ % ssh [email protected]
The authenticity of host '192.168.1.199 (192.168.1.199)' can't be established.
ED25519 key fingerprint is SHA256:avsigvHVnCWhzxoTC78Dl6VJKiRVhrYrV30gqk3v+xs.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.1.199' (ED25519) to the list of known hosts.
[email protected]'s password: 
root@klk-wiis-0503F6:~ # 

N.B. login is root, default password is pdmk-gatewayID (here pdmk-0503F6).

Configuring the packet forwarder

As described here, use klk_apps_config to configure a single forwarding instance (on OS versions > 5.0 it is possible to forward to multiple LNS, refer to the previous document)

root@klk-wiis-0503F6:~ # klk_apps_config --activate-cpf --lns-server eu1.cloud.thethings.network --lns-dport 1700 --lns-uport 1700
Stopping lorad 2.3.0
Stopping lorafwd 1.4.0
WARNING: Unable to find lorafwd pid
WARNING: Unable to find lorafwd pid
WARNING: Unable to find lorafwd pid
WARNING: Unable to find lorafwd pid
WARNING: Unable to find lorafwd pid
Starting lorad 2.3.0
Starting lorafwd 1.4.0
lorafwd[1457]: <6> Parsing configuration file: /var/run/lora/gateway-id.toml
lorafwd[1457]: <6> Parsing configuration file: /etc/lorafwd.toml
root@klk-wiis-0503F6:~ # 

N.B. here, the warning indicates that packet forwarding was not yet enabled.