LoRa Timeout

Hi,

i have several LoRa Gateways out there.
Most of them are RBM33G with an LTE and LoRa8 card from mikrotik, some are WAP R mit LoRa8 cards.
All Getways are on routerOS ver 6.46.2 and the LTE cards on v013

Both configurations have the same problem:
LoRa_Timeouts.PNG
why do i see so much timeouts for the connection to TTN?
it is not the LTE connection because i can see the same problem on gateways connected with WiFi or cable.

have anybody an idea why these timeouts happen?

Hello,

Keepalive packets are sent frequently to the server to let you know whether the server is accessible. If an answer is not received, this message is written to the log file. If you see this message, there is a chance that uplinks sent to the server around this moment will not reach the server. It could be caused either by network issues in any segment from your gateway to the server, or also it is caused by server configuration, performance issues. We also have seen this quite regularly with TTN server, but not when using a local ChirpStack server.

Hi I have the same here with my gateway, but do not see any limitations by sending LoRa packets to thethingsnetwork.
I just also do not know where to disable this polling.
Via terminal the address is resolved successfully, but it’s not pingable.
I am not sure if the address could be changed to another url.

Hi. I am extremly disappointed with TTN. I try to test Lora with Mikrotik RBwAPR and keepalive timeout info to EU TTN is more or less every 2-3 minutes (evening, better during day). I must say that in my situation it is NOT network problem. Connectivity to INet is absolutelly OK. Others packets to network is without problems. It is definitelly TTN problem. During this outage forwarded packets from LoRa is definetelly lost. Grrrrrrrr … I am thinking about ChirpStack server, because TTN is unuseable.

Hi guys,

We are based in South Africa with an average of 160-1780ms to eu.mikrotik.thethings.industries.

We are currently seeing most of our gateways report the same keepalive issues.

Since there is no way to modify the “push_timeout_ms” value, we cannot increase the timeout window to support our geographical location.

https://github.com/TheThingsNetwork/lorawan-stack/issues/2075