brocaar / chirpstack-packet-multiplexer Goto Github PK

Hi,

it would be nice if you also could publish this on docker hub.

Thx

It seems to stop when DNS resolve fails for one of the backends. Perhaps just continue and print and error in the log?
As a side-note, I wonder how DNS changes are propagating between lets say a chirpstack docker and a packet-multiplexer docker.

Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"./lora-packet-multiplexer\": stat ./lora-packet-multiplexer: no such file or directory": unknown

Steps for reproduction:

1. Clone project
2. docker-compose run --rm packetmultiplexer bash

I'm able to start the container if I copy the root folder into cmd. Unfortunately, there are similar reference errors within the container (related to make). The same error occurs if simply building the Dockerfile:

go: finding github.com/brocaar/lora-packet-multiplexer/cmd latest build command-line-arguments: cannot load github.com/brocaar/lora-packet-multiplexer/cmd/lora-packet-multiplexer/cmd: cannot find module providing package github.com/brocaar/lora-packet-multiplexer/cmd/lora-packet-multiplexer/cmd make: *** [Makefile:6: build] Error 1

Hi.

One of the LNS we work with requires the Gateway unique identifier to follow a specific format. Due to this, we can't use the real EUI from the LoRa concentrator chip.

I know the real solution would be to fix the broken LNS. But if we were to create a pull request adding support for gateway aliases (translating the Gateway unique identifier when talking to specific backends), is that something you would consider merging, or would you see that as completely outside the scope for the multiplexer?

Can it have some gateway ID wildcard/regexp?
Or are there some other criteria we can match on? (frequency/channel perhaps)
Do we need to restart the service to reload the configuration or can we send some signal?

Dear Orne,
Can you look at this trouble, please? I have two backends, both with uplink_only = false. Even so, the multiplexer is blocking downlink messages. I compiled the SNAPSHOT-6e3aab3 yesterday (3.0.0).
THX

INFO[0000] starting LoRa Packet Multiplexer docs="https://www.loraserver.io/" version=SNAPSHOT-6e3aab3
INFO[0000] starting listener addr="0.0.0.0:1700"
INFO[0000] dial udp gateway_id=fcc23dfffe0dd3fa host="127.0.0.1:1701" uplink_only=false
INFO[0000] dial udp gateway_id=fcc23dfffe0dd3fa host="router.eu.thethings.network:1700" uplink_only=false
INFO[0002] packet received from gateway addr="127.0.0.1:44464" gateway_id=fcc23dfffe0dd3fa packet_type=PushData
INFO[0002] sending packet to gateway addr="127.0.0.1:44464" gateway_id=fcc23dfffe0dd3fa packet_type=PushACK
INFO[0002] forwarding packet to backend from="127.0.0.1:44464" gateway_id=fcc23dfffe0dd3fa packet_type=PushData to="router.eu.thethings.network:1700"
INFO[0002] forwarding packet to backend from="127.0.0.1:44464" gateway_id=fcc23dfffe0dd3fa packet_type=PushData to="127.0.0.1:1701"
INFO[0002] packet received from backend gateway_id=fcc23dfffe0dd3fa host="127.0.0.1:1701" packet_type=PushACK
INFO[0002] packet received from backend gateway_id=fcc23dfffe0dd3fa host="router.eu.thethings.network:1700" packet_type=PushACK
INFO[0005] packet received from gateway addr="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData
INFO[0005] sending packet to gateway addr="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullACK
INFO[0005] forwarding packet to backend from="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData to="127.0.0.1:1701"
INFO[0005] forwarding packet to backend from="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData to="router.eu.thethings.network:1700"
INFO[0005] packet received from backend gateway_id=fcc23dfffe0dd3fa host="127.0.0.1:1701" packet_type=PullACK
INFO[0005] packet received from backend gateway_id=fcc23dfffe0dd3fa host="router.eu.thethings.network:1700" packet_type=PullACK
INFO[0015] packet received from gateway addr="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData
INFO[0015] sending packet to gateway addr="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullACK
INFO[0015] forwarding packet to backend from="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData to="127.0.0.1:1701"
INFO[0015] forwarding packet to backend from="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData to="router.eu.thethings.network:1700"
INFO[0015] packet received from backend gateway_id=fcc23dfffe0dd3fa host="127.0.0.1:1701" packet_type=PullACK
INFO[0015] packet received from backend gateway_id=fcc23dfffe0dd3fa host="router.eu.thethings.network:1700" packet_type=PullACK
INFO[0021] packet received from gateway addr="127.0.0.1:42350" gateway_id=fcc23dfffe0dd3fa packet_type=PushData
INFO[0021] sending packet to gateway addr="127.0.0.1:42350" gateway_id=fcc23dfffe0dd3fa packet_type=PushACK
INFO[0021] forwarding packet to backend from="127.0.0.1:42350" gateway_id=fcc23dfffe0dd3fa packet_type=PushData to="127.0.0.1:1701"
INFO[0021] forwarding packet to backend from="127.0.0.1:42350" gateway_id=fcc23dfffe0dd3fa packet_type=PushData to="router.eu.thethings.network:1700"
INFO[0021] packet received from backend gateway_id=fcc23dfffe0dd3fa host="127.0.0.1:1701" packet_type=PushACK
INFO[0021] packet received from backend gateway_id=fcc23dfffe0dd3fa host="router.eu.thethings.network:1700" packet_type=PushACK
INFO[0022] packet received from backend gateway_id=fcc23dfffe0dd3fa host="127.0.0.1:1701" packet_type=PullResp
INFO[0022] ignoring downlink packet, backend is uplink only gateway_id=fcc23dfffe0dd3fa host="127.0.0.1:1701" packet_type=PullResp
INFO[0025] packet received from gateway addr="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData
INFO[0025] sending packet to gateway addr="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullACK
INFO[0025] forwarding packet to backend from="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData to="127.0.0.1:1701"
INFO[0025] forwarding packet to backend from="127.0.0.1:50906" gateway_id=fcc23dfffe0dd3fa packet_type=PullData to="router.eu.thethings.network:1700"
INFO[0025] packet received from backend gateway_id=fcc23dfffe0dd3fa host="127.0.0.1:1701" packet_type=PullACK
INFO[0025] packet received from backend gateway_id=fcc23dfffe0dd3fa host="router.eu.thethings.network:1700" packet_type=PullACK
I

Is there easy way to allow all gateways to passthrough to certain hosts/backends ?

Please, don't abandon this project, is AWESOME !!

I followed the steps as indicated, and reached the part of editing the .toml config file. However, it is nowhere to be found...

To complete the installation, update the configuration file which is located at /etc/chirpstack-packet-multiplexer/chirpstack-packet-multiplexer.toml and (re)start the service:

sudo systemctl restart chirpstack-packet-multiplexer

Such folder under /etc does not exist, nor the .toml... I ran a search from root and no results of such .toml...
Running chirpstack-packet-multiplexer configfile does print the default configuration shown in the Readme...

Any hints on this one?
Running on Ubuntu 20.04. Another colleague tried in 18.04 and had the same issue.

Thanks