Hello fellow ChirpStack users,
I’m trying to connect my Laird RG191 to my ChirpStack Gateway Bridge running on a Raspberry Pi 2 B. I downloaded the “full” image. I am following the instructions at Laird - ChirpStack open-source LoRaWAN® Network Server documentation
Here are the modem router IP addresses listed:
I have navigated to the ChirpStack Network Server UI:
Here is the gateway listed/registered:
Here’s my Laird RG191 GUI:
What am I doing wrong and how do I fix it? Any help would be much appreciated.
The chirpstack gateway OS (full or regular) was not intended for additional gateways to be added, its meant to be a gateway itself. And the full version is really only made to test the gateway or have single gateway solutions. I think it is quite difficult to expose the MQTT forwarder port on the CS GW OS.
You should instead get Ubuntu on your pi and do the traditional Ubuntu intstall or docker install.
Thanks for the comment @Liam_Philipp!
Maybe I’ve confused myself. I thought ChripStack is a network server?
Should the Gateway OS be for an “all-in-one” gateway (for example, a Raspberry Pi with a LoRa hat that also hosts a network server)?
My objective is to have my Laird RG191 connected to a network server hosted on a Raspberry Pi which I can register my LoRaWAN nodes to as part of an application. I want to have a private LoRaWAN instance instead of using The Things Network. What software should I be using instead?
Yup it is! But the Chirpstack Gateway OS is slightly different beast than Chirpstack itself.
This is exactly right, the GW OS is designed to make the Pi a gateway itself. The “full” install adds a lightweight network server to the Pi aswell, but it is only designed to process it’s own gateway’s traffic, not to add others to it.
For this you will want the regular Chirpstack install. Either the Ubuntu Install or the Docker Install (personally I prefer docker but it might add a layer of complexity if you are not familiar and want to tinker a bit). I’d recommend installing Ubuntu onto your Pi regardless of which install you do as docker works on anything.
Awesome, thank you mate. It’s obvious now (like most things when people explain them)! This is what happens when you try to dive headfirst into something late at night. I’ll head down that path.
1 Like
