I’ve read articles mentioning remote management/access of gateways with the Semtech LoRa Basics Station. I’ve also found Semtech documentation about running a remote shell session tunnelling through the WebSocket to the LNS.
Does The Things Stack (V3) support remote management if I’ve configured a gateway with the CUPS? If so, how do I use this remote functionality?
Something which I’m confused about is if the LNS or the CUPS enables this remote access. Articles from The Things Industries seem to state that it’s the CUPS which does, however Semtech articles seem to state it’s the LNS.
Here’s a few articles mentioning remote management:
Not only is LoRa Basics Station both easily portable and easily testable thanks to its resource-efficient lean architecture, but it also sports a host of additional features that make it the clear choice when selecting a gateway implementation for a LoRaWAN network.
Among these features are:
LoRaWAN Network Server protocol support, including:
Remote system commands and optional interactive shell
LoRa Basics™ Station can regularly connect to a Configuration and Update Server (CUPS) server to check for configuration and software updates. This page contains information about connecting your gateway to The Things Stack to support remote management via the CUPS Protocol.
The LoRa Basics Station comes with a Configuration and Update Server (CUPS) to easily manage and update these settings, or to remotely access an individual gateway by running a secure shell session on the Station.
I have been trying to find the same answer. I have seen a post where someone was able to use a CUPS server to change the LNS that the TTIG in particular is using (That is all the guy would tell us). It looks like Basic Station is actually a software implementation to use in a custom gateway. What is missing is the information on how to create your own CUPS server so you can configure the gateways. Maybe you have use this on a Pi or another linux system to get the CUPS running.
How does that answer what TTN implemented of the remote management capabilities available in the CUPS/LNS protocol? I understand you are offering an alternative but it doesn’t answer the original question.
You are right @kersing i missunderstood the question! balena provides an operating system to run containers with the basicstation code, and all the tools available on the OS, not, the TTN implementation for CUPS/LNS! Thanks for the headsup!
The LoRa Basics Station software includes two sub-protocols for connecting the gateway to the network server, the LoRaWAN Network Server (LNS), and the Configuration and Update Server (CUPS) protocol.
The LNS protocol establishes a data connection between the LoRa Basics Station compatible gateway and the web server. LoRa upstream and downstream messages are exchanged over a data connection via secure WebSockets.
The CUPS protocol enables credential management, as well as remote configuration of gateways and firmware updates. AWS IoT Core for LoRaWAN provides LNS and CUPS endpoints for LoRaWAN data capture and remote gateway management, respectively.