Kerlink Wirnet Station 868

Hello could you confirm that this kerlink gateway is compliant with the loraserver?

I’m wondering what is the best choice to be more compliant with loraserver, buy a kerlink gateway with or without SPN version.

Thank you so much

Yes, that gateway works fine with LoRa Server.

1 Like

Hello,

basic question concerning Kerlink IoT station gateway, I’m trying to install the lora-gateway-bridge with the gateway installation procedure (https://www.loraserver.io/lora-gateway-bridge/gateway/kerlink/#kerlink-iot-station) but I have a problem to download the binary, I’m using wget command without succes.

[root@Wirgrid_0b031311 bin]# wget https://artifacts.loraserver.io/downloads/lora-gateway-bridge/lora-gateway-bridge_3.0.1_linux_armv5.tar.gz
wget: not an http or ftp url: https://artifacts.loraserver.io/downloads/lora-gateway-bridge/lora-gateway-bridge_3.0.1_linux_armv5.tar.gz

Without ‘s’

[root@Wirgrid_0b031311 bin]# wget http://artifacts.loraserver.io/downloads/lora-gateway-bridge/lora-gateway-bridge_3.0.1_linux_armv5.tar.gz
Connecting to artifacts.loraserver.io (188.166.134.65:80)
wget: not an http or ftp url: https://artifacts.loraserver.io/downloads/lora-gateway-bridge/lora-gateway-bridge_3.0.1_linux_armv5.tar.gz

Or like this

[root@Wirgrid_0b031311 bin]# wget --no-check-certificate http://artifacts.loraserver.io/downloads/lora-gateway-bridge/lora-gateway-bridge_3.0.1_linux_armv5.tar.gz
Connecting to artifacts.loraserver.io (188.166.134.65:80)
wget: not an http or ftp url: https://artifacts.loraserver.io/downloads/lora-gateway-bridge/lora-gateway-bridge_3.0.1_linux_armv5.tar.gz

Any help would be appreciated.

Thank you

Hello,

ok I downloaded lora-gateway-bridge_3.0.1_linux_armv5.tar.gz via scp connection with WinSCP , I followed the instruction kerlink IoT station.

But no “live lorawan frames” after rebooted the gateway and created the gateway on loraserver.

I did the troubleshooting and I performed this command ( sudo tcpdump -AUq -i lo port 1700) to check if the packet forwarder works well?

Here logs:

[root@Wirgrid_0b031311 /root]# tcpdump -AUq -i lo port 1700
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo, link-type EN10MB (Ethernet), capture size 65535 bytes
17:17:54.138888 IP localhost.39829 > localhost.1700: UDP, length 12
E..(._@.@..c...............'.<T....K....
17:18:04.339017 IP localhost.39829 > localhost.1700: UDP, length 12
E..(.a@.@..a...............'.......K....
17:18:09.197189 IP localhost.48504 > localhost.1700: UDP, length 153
E....c@.@............x........C....K....{"stat":{"time":"2019-07-01 15:18:09 GMT","lati":43.47488,"long":5.60768,"alti":217,"rxnb":3,"rxok":1,"rxfw":1,"ackr":0.0,"dwnb":0,"txnb":0}}
17:18:11.745569 IP localhost.48504 > localhost.1700: UDP, length 240
E....e@.@..y.........x.............K....{"rxpk":[{"tmst":274913436,"time":"2019-07-01T15:18:11.709737Z","chan":1,"rfch":1,"freq":868.300000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":11.2,"rssi":-73,"size":19,"data":"QHgFHgaA+h5jnF+BxjvWTC9FOQ=="}]}
17:18:12.019041 IP localhost.48504 > localhost.1700: UDP, length 246
E....g@.@..q.........x........:....K....{"rxpk":[{"tmst":275184308,"time":"2019-07-01T15:18:11.980609Z","chan":0,"rfch":1,"freq":868.100000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":-10.5,"rssi":-118,"size":23,"data":"QFrqDh8AlwUCy0wUjbXfjzas0/NcXrs="}]}
17:18:14.538828 IP localhost.39829 > localhost.1700: UDP, length 12
E..(.i@.@..Y...............'..)....K....
17:18:24.738817 IP localhost.39829 > localhost.1700: UDP, length 12
E..(.k@.@..W...............'.......K....
17:18:34.938790 IP localhost.39829 > localhost.1700: UDP, length 12
E..(.m@.@..U...............'..<....K....
17:18:39.199597 IP localhost.48504 > localhost.1700: UDP, length 153
E....o@.@............x.......|.....K....{"stat":{"time":"2019-07-01 15:18:39 GMT","lati":43.47490,"long":5.60765,"alti":214,"rxnb":2,"rxok":2,"rxfw":2,"ackr":0.0,"dwnb":0,"txnb":0}}

According this log I think localhost.39829 = lora-gateway-bridge?
I didn’t see any packet sent from the LoRa Gateway Bridge to the packet-forwarder is this normal?

As I don’t know where find the log of lora-gateway-bridge, journalctl -f -n 100 -u lora-gateway-bridge and tail -f -n 100 /var/log/lora-gateway-bridge/lora-gateway-bridge.log don’t work I looked if the lora-gateway-bridge was active

Here the output (-aux option doesn’t work):

[root@Wirgrid_0b031311 /root]# ps w |grep lora-gateway-bridge
1667 root      2552 S    grep lora-gateway-bridge

From loraserver side no publishes data mosquitto_sub -v -t "gateway/#" I have got only the data from my multitech gateway…

So I have some questions around mqtt broker connection, I didn’t install mosquitto on kerlink gateway, Should I install it And when should I inform the id/pass of my mqtt broker installed on my loraserver?

For example on my multitech gateway I filled in this information in the lora-gateway-bridge.toml.

As reminder the things network bridge was installed before, I only modified local_conf.json to point to localhost instead router.eu.thethings.network

the local_conf.json is located here ==> /mnt/fsuser-1/thethingsnetwork/

There is also a manifest.xml file located here and others files:

.DS_Store
._.DS_Store
._global_conf.json
._manifest.xml
._poly-pkt-fwd.sh
._poly_pkt_fwd
._readme.md
global_conf.json
local_conf.json
manifest.xml
poly-pkt-fwd.sh
poly_pkt_fwd
poly_pkt_fwd.log
readme.md

these files must be moved to another place ?

Thank you for your help.

Any experience of lora-gateway-bridge deployment on the kerlink IoT/Wirnet station would be welcome :slight_smile:
Thank you.

You tcpdump output looks like the Packet Forwarder is sending to localhost:1700, however this doesn’t confirm that LoRa Gateway Bridge is running on your gateway.

[root@Wirgrid_0b031311 /root]# ps w |grep lora-gateway-bridge
1667 root      2552 S    grep lora-gateway-bridge

This indicates that the lora-gateway-bridge binary is not running. I believe what you are seeing is the grep process.

1 Like

Thank @brocaar for your reply, so the lora-gateway-bridge is not enabled.

My first idea, it’s because there is conflict with the old bridge TTN, the meganism to start “custom” application on boot must point to the old files manifest.xml, poly-pkt-fwd.sh … instead of new files located here:

/mnt/fsuser-1/lora-gateway-bridge/manifest.xml
/mnt/fsuser-1/lora-gateway-bridge/start.sh

Plz could you tell me where is located your local_conf.json in your kerlink gateway?

Thank you

I don’t have a Wirnet Station currently to test with currently, but I have seen the instructions work before. I do have an iBTS, but the paths are different.

Ok thank you, I opened a ticket to Kerlink to expose my issue, I will make a return on this thread.

After some question-reply between the Helpdesk Kerlink and me, he told me that:

Hello,

Actually you have to install a packet forwarder on the station to work with the loraserver.
Can you try to install the Kerlink packet forwarder available on the wiki?
I will do the test on my station in parallel.

Best regards,

I thought it was installed by default.

And here his last reply:

Hello,

I tried this morning to follow the loraserver procedure (link that you provided).
I installed the Semtech packet forwarder as shown by putting the server address on localhost. Then I followed the procedure to install the lora-gateway bridge on the station. I note that the file start.sh does not start the lora-gateway-bridge. There may be a problem with the explanations on loraserver.io.

[root@Wirnet_0B03005A lora-gateway-bridge]# cat start.sh
#!/bin/bash

LOGGER="logger -p local1.notice"

# mosquitto
iptables -A INPUT -p tcp --sport 1883 -j ACCEPT

/mnt/fsuser-1/lora-gateway-bridge/bin/lora-gateway-bridge --mqtt-server tcp://192.168.5.151:1883  2>&1 | $LOGGER &
[root@Wirnet_0B03005A lora-gateway-bridge]#

The command /mnt/fsuser-1/lora-gateway-bridge/bin/lora-gateway-bridge --mqtt-server tcp://192.168.5.151:1883 doesn’t work when I run it manually

[root@Wirnet_0B03005A lora-gateway-bridge]# /mnt/fsuser-1/lora-gateway-bridge/bin/lora-gateway-bridge --mqtt-server tcp://192.168.5.151:1883
Error: unknown flag: --mqtt-server
Usage:
  lora-gateway-bridge [flags]
  lora-gateway-bridge [command]

Available Commands:
  configfile  Print the LoRa Gateway Bridge configuration file
  help        Help about any command
  version     Print the LoRa Gateway Bridge version

Flags:
  -c, --config string   path to configuration file (optional)
  -h, --help            help for lora-gateway-bridge
      --log-level int   debug=5, info=4, error=2, fatal=1, panic=0 (default 4)

Use "lora-gateway-bridge [command] --help" for more information about a command.

FATA[0000] unknown flag: --mqtt-server
[root@Wirnet_0B03005A lora-gateway-bridge]#

It seems that a configuration file is needed.
I advise you to contact loraserver.io support directly for information on how to configure their solution. We only support applications developed by Kerlink.

Hello @brocaar,

could you explain me why we don’t need a lora-gateway-bridge.toml with kerlink wirnet station?

Then something is not clear for me in start.sh /mnt/fsuser-1/lora-gateway-bridge/bin/lora-gateway-bridge --mqtt-server tcp://192.168.1.27:1883 2>&1 | $LOGGER & --mqtt-server is a flag?

If yes why it’s not mentionned in the --help, I don’t have any information about it

[root@Wirgrid_0b031311 lora-gateway-bridge]# ./bin/lora-gateway-bridge --help
LoRa Gateway Bridge abstracts the packet_forwarder protocol into JSON over MQTT
        > documentation & support: https://www.loraserver.io/lora-gateway-bridge
        > source & copyright information: https://github.com/brocaar/lora-gateway-bridge

Usage:
  lora-gateway-bridge [flags]
  lora-gateway-bridge [command]

Available Commands:
  configfile  Print the LoRa Gateway Bridge configuration file
  help        Help about any command
  version     Print the LoRa Gateway Bridge version

Flags:
  -c, --config string   path to configuration file (optional)
  -h, --help            help for lora-gateway-bridge
      --log-level int   debug=5, info=4, error=2, fatal=1, panic=0 (default 4)

Use "lora-gateway-bridge [command] --help" for more information about a command.

Here the logs:

Jul 18 15:32:35 (none) local1.notice logger: time="2019-07-18T15:32:35+02:00" level=fatal msg="unknown flag: --mqtt-server"
Jul 18 15:32:45 (none) local1.notice logger: Error: unknown flag: --mqtt-server
Jul 18 15:32:45 (none) local1.notice logger: Usage:
Jul 18 15:32:45 (none) local1.notice logger:   lora-gateway-bridge [flags]
Jul 18 15:32:45 (none) local1.notice logger:   lora-gateway-bridge [command]
Jul 18 15:32:45 (none) local1.notice logger:
Jul 18 15:32:45 (none) local1.notice logger: Available Commands:
Jul 18 15:32:45 (none) local1.notice logger:   configfile  Print the LoRa Gateway Bridge configuration file
Jul 18 15:32:45 (none) local1.notice logger:   help        Help about any command
Jul 18 15:32:45 (none) local1.notice logger:   version     Print the LoRa Gateway Bridge version
Jul 18 15:32:45 (none) local1.notice logger:
Jul 18 15:32:45 (none) local1.notice logger: Flags:
Jul 18 15:32:45 (none) local1.notice logger:   -c, --config string   path to configuration file (optional)
Jul 18 15:32:45 (none) local1.notice logger:   -h, --help            help for lora-gateway-bridge
Jul 18 15:32:45 (none) local1.notice logger:       --log-level int   debug=5, info=4, error=2, fatal=1, panic=0 (default 4)
Jul 18 15:32:45 (none) local1.notice logger:
Jul 18 15:32:45 (none) local1.notice logger: Use "lora-gateway-bridge [command] --help" for more information about a command.

Currently I’m blocked and kerlink helpdesk send me back to you.

If someone have any experience with kerlink IoT/Wirnet station it would be appreciate to share how to make it work with the loraserver.

Thank you for your help.

Actually, the instructions might need an update. You do need to use a lora-gateway-bridge.toml file!

ok thank you for your fast reply, I 'm adding lora-gateway-bridge.toml to specific path, to debug I can send lora-gateway-bridge with -c flag to indicate the specific path of the lora-gateway-bridge.toml

Hello,

after added lora-gateway-bridge.toml with the good setting it works :wink:

To summarize in addition to following the installation procedure:

Use or install a regular Semtech Packet Forwarder (which match with the version of your kerlink wirnet station)

Add the lora-gateway-bridge.toml with the good setting (following your install).

Start the packet-forwarder and the lora-gateway-bridge (by informing where is located your config file if you use --config flag).

@brocaar Can I help you to update https://www.loraserver.io/lora-gateway-bridge/gateway/kerlink/ field Kerlink IoT station ?

With a pull request ?

1 Like

I missed your message. Yes, that would be great. You will find the kerlink.md file in the lora-gateway-bridge repository.

1 Like