I learned that ChirpStack App Server supports using separate/custom/external/centralized join server by pointing [join_server.default] in loraserver.toml to its IP address. I wonder if I can actually use the ChirpStack Application Server as my external join server. For example, I plan to install the network server and application server on the gateway, but separate out the join server and install it on one server instance and have multiple gateways point out to that server instance. I was thinking to reinstall the ChirpStack Application Server on that server instance but use it only as a join server. Is this possible? Like can I turn off the application server functionalities and keep only the join server functionalities in the ChirpStack Application Server?
Thank you @bconway ! The links were helpful, however, my question was more about utilizing ChirpStack Application Server as a Join Server only that is installed outside of the gateway on a server. Does anyone have any experience or knowledge about that?
I would like to ask how to configure chirpstack v4 so that one is as an application server and the other as a join server.
On the first one (chirpstack1) I have to set in section: [join_server]
server as [join_server.chirpstack2] server=“http://chirpstack2:8003”
and on the second(chirpstack2) in the section: [network_controller]
Should this configuration work? Do I need to set some other endpoint?
In general, you can connect to any external join-server that implements the join-server API as specified by the LoRaWAN Backend Specs.
Please note that using a join-server is not mandatory. If you configure the AppKey in ChirpStack (after adding the device), then ChirpStack will handle the join-request without the need of an external join-server.