Before to proceed, the problem is not related to TTN Console not working properly all the time [console] [gateway] [not connected] [no traffic] [application] [no data]
We have been aware of the ttn console problem for months and we already fixed with some internal workaround.
Our problem is different some of our gateways seem to be blocked, and for blocked I mean no data are sent to our application, we use http integration.
Here is a list of some blocked gw
Sometimes we can see the above gw to ping ttn from console, but no data are showed or sent to our application.
Our infrastructure is based on 29 of the following model https://www.multitech.com/brands/multiconnect-conduit-ip67
About half of them are based on packet forwarder of ttn, the other half is based on legacy semtech packet forwarder. The problems seems to affect much more the gw with the legacy packet forwarder.
Before to write here, we tested and debug different gw in house to ensure no bug is present in the gw firmware.
I personally tested
- check if the packet forwarder crash or block for some reasons, nothing found the daemon runs without problem and collect the incoming lorawan data ( the firmware provide an angel for the daemon in case of stuck )
- check if the problem it was related to network fault, nothing found
- check the udp traffic sent from the packet forwarder to “router.eu.thethings.network” port 1700, nothing found
After the tests, we decided to move the blocked gw to a new eui and magically it started to run again. We moved a working gw to the previous blocked eui and it stopped to work.
From my personal experience when the ttn console stops to work, also the api http://noc.thethingsnetwork.org:8085/api/v2/gateways/ stops to work. The application ttnctl doesn’t give more details, so we based our observations on what our application receive from the http integration.
Let me know if I’m wrong.