Is there any news on this (@brocaar)? I guess with the transition from TTN v2->v3 by September this year this gets more momentum.
I attached a picture how I would imagine the behaviour for a private network, which keeps private netIds local, if they are handled by the local installation.
For everyone not knowing what packet broker is here a 10min explaination: https://www.youtube.com/watch?v=t3qZjuJ3NwM
I think ideally the PacketBroker integration should be an external component, not something embedded within the ChirpStack Network Server. If somebody would be interested to work on such component, then I’m happy to share my thoughts, but I don’t have any plans to create such component yet.
@brocaar I would like to hear about your thoughts and also a bit of light on how to work with Chirpstack and Packet forwarder.
Thanks in advance.
You mean a Packet Forwarder or Packet Broker?
I mean Packet broker, i made a mistake sorry.
The way I would see an integration with the Packet Broker is:
[Packet Broker integration] <--> [MQTT broker] <--> [ChirpStack Network Server]
E.g. it would just behave like a gateway or gateways.