Problem with chirpstack-gateway-bridge on Dragino LG308 gateway

ChirpStack Gateway Bridge
1

Hi!

I installed the gateway bridge on the gateway as described (https://www.chirpstack.io/gateway-bridge/gateway/dragino/), but the status of the gateway goes offline.
I want to ask for help to set the active state.

Version:
Dragino LG308 Firmware: lgw-5.4.1615882321
Chirpstack Gateway Bridge: chirpstack-gateway-bridge_3.10.0-r1_mips_24kc.ipk
I set up the mqtt connection (with user name and password): server=“tcp://xxx.xxx.xxx.xxx:8883”
I set up the LoRaWAN Configuration:

image
image893×425 16.4 KB

The service is running, ps output:

489 root 16868 R /opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge --config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml

I see this in the log:

I see this in the log:
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: Starting Packet Forwarder at 20210326171911
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ found global configuration file /etc/lora/global_conf.json, parsing it
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ /etc/lora/global_conf.json does contain a JSON object named SX130x_conf, parsing SX1301 parameters
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ lorawan_public 1, clksrc 1
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ no configuration for LBT
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ antenna_gain 0 dBi
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Configuring TX LUT with 16 indexes
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ radio 0 enabled (type SX1257), center frequency 867500000, RSSI offset -166.000000, tx enabled 1, tx_notch_freq 0
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ radio 1 enabled (type SX1257), center frequency 868500000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora multi-SF channel 0> radio 1, IF -400000 Hz, 125 kHz bw, SF 7 to 12
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora multi-SF channel 1> radio 1, IF -200000 Hz, 125 kHz bw, SF 7 to 12
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora multi-SF channel 2> radio 1, IF 0 Hz, 125 kHz bw, SF 7 to 12
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora multi-SF channel 3> radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora multi-SF channel 4> radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora multi-SF channel 5> radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora multi-SF channel 6> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora multi-SF channel 7> radio 0, IF 400000 Hz, 125 kHz bw, SF 7 to 12
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ /etc/lora/global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ server hostname or IP address is configured to “router.eu.thethings.network”
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ upstream port is configured to “1700”
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ downstream port is configured to “1700”
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ packets received with a valid CRC will be forwarded
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ packets received with a CRC error will NOT be forwarded
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ packets received with no CRC will NOT be forwarded
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ found local configuration file /etc/lora/local_conf.json, parsing it
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ redefined parameters will overwrite global parameters
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ /etc/lora/local_conf.json does not contain a JSON object named SX130x_conf
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ /etc/lora/local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ gateway MAC address is configured to A840411DBEF84150
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ server hostname or IP address is configured to “localhost”
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ upstream port is configured to “1700”
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ downstream port is configured to “1700”
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ downstream keep-alive interval is configured to 30 seconds
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ statistics display interval is configured to 30 seconds
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ upstream PUSH_DATA time-out is configured to 100 ms
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ packets received with a valid CRC will be forwarded
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ packets received with a CRC error will NOT be forwarded
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ packets received with no CRC will NOT be forwarded
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Reference latitude is configured to 22.700000 deg
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Reference longitude is configured to 114.240000 deg
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Reference altitude is configured to 450 meters
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ fake GPS is enabled
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Beaconing period is configured to 0 seconds
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Beaconing signal will be emitted at 869525000 Hz
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Beaconing datarate is set to SF9
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Beaconing modulation bandwidth is set to 125000Hz
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Beaconing TX power is set to 14dBm
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ Beaconing information descriptor is set to 0
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ sockfd=3
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ sockfd=4
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ FPort Filter: 0
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ DevAddrMask: 0x0
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ ABP Decryption: no
Fri Mar 26 17:19:11 2021 daemon.info lora_pkt_fwd[858]: INFO~ sx1276:0, sxtxpw:0, model:LG08, server_type:lorawan

Thanks,
Feri

2

Hi Feri,

i have also the same problem , have you found any solution ??!!

3

Hi, both,

Have you guys figured out how it work for LG308?

4

I’d recommend getting an SSH or serial connection into the gateway and running

logread -f

Ideally using a serial or SSH client that can capture everything sent into a file (or at least window with long history) which you can search through later for items of interest.

Then have a node transmit packets in range of the gateway and see what you get in the logs

Also make sure that that both the lora_pkt_fwd and gateway bridge (whatever the process is called in this installation) are actually running.

5

I have the same problem. The lora_pkt_fwd runs fine and receives the join request from my devices:

Tue Dec 14 01:24:35 2021 daemon.info lora_pkt_fwd[27324]: PKT_FWD~ JOIN_REQ+
{"AppEUI":,"XXXXXXXXXXX", "DevEUI":,"XXXXXXXXX", "DevNonce": "42251"}
Tue Dec 14 01:24:35 2021 daemon.info lora_pkt_fwd[27324]: RXTX~ {"rxpk":[{"tmst":607711436,"time":"2021-12-14T01:24:35.413814Z","chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF11BW125","codr":"4/5","lsnr":9.8,"rssi":-67,"size":23,"data":"XXXXXXXXX="}]}

Is there a way to check functionality of the chirpstack-gateway-bridge? I did install the latest version as documented in the docs and started through the init.d script. It does not show an error.

However, it does not work and seems to not generate any output at all.

logread -f

has no mention of the bridge. If I start the bridge manually using

/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge

it just hangs forever. Also the proposed command to get help (–help) or to generate a new config from generic documentation does just hang forever.

My best guess is, that the executable from the package is just broken. I also tried an older version (3.9.2) with no luck.

I recently provisioned a Kerlink iStation without problems. The gateway-bridge worked as expected.

6

See if you can get a copy of strace or ltrace for your gateway’s Linux and use that to run it so you can see what it is trying to do.

It’s not a given that a daemon intended to be run from an init script would not just sit there appearing to do nothing. If not designed to fork and exit when started from an interactive shell it would never give you the command prompt back, and if it has its own route to system logs it wouldn’t necessarily write to stdout/stderr.

Also use ps to make sure there isn’t already a copy running. If there was, a second copy would probably be unable to claim the UDP port.

7

I have the same exact problem. If I place the gateway bridge in a outside server it seems to work perfectly fine, but if I install the gateway bridge in the gateway itself as it is indicated in the documentation i doesn’t work anymore.

I get:

  • As it is described in the thread it seems that the UDP forwarder delivers the messages to the gateway bridge.
  • The nothing more happens.
  • I can publish mqtt messages in the broker from the gateway manually, so connectivity is fine.
  • Tracked the process using strace and just shows nothing.

I’m kinda stuck here.

EDIT
I found a solution in an old thread. For Dragino LG308 only works the gateway bridge version 3.8.0. Don’t install the latest, just stick to that version. I would ask a moderator or staff member to edit the Dragino gateway documentation and indicate please that the only working version is the 3.8.0. Thanks.

8

I am trying to use Chirpstack Gateway Bridge on a Dragino LPS8 gateway. It is a very similar model comparing LG308. The ram and cpu are the same. So I am expecting this gateway to run Chirpstack GWB successfully.
I make required config file changes but my Chirpstack network server(its on another machine) can not get uplink packet over mqtt subscription.
I need to see chirpstack gateway bridge log screen to see what is going on. So how can I see gateway bridge log screen can you help me ? Bridge is working as a service now.
@brocaar

9

Confirmed v3.8.0 is working for Dragino LPS8.
https://artifacts.chirpstack.io/vendor/dragino/LG308/