Timestamp from the future :O

Hi Everyone, im dealing with the TOO_EARLY error from OTA join response.

The issue comes after months of correct work of loraserver and two gateways.

Tracking the issue i get this details:

  1. only ota affected, nodes with abp works fine
  2. the ota joins it the only i see in the log, join and response but the node didnt get the response
  3. the error seems to be the gateway that generates weir timestamps from the future like this:

E…J-@.@…0…y…1…’…TK.{“stat”:{“time”:“2018-09-03 23:16:37 GMT”,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0}}

20:16:46.687917 IP localhost.41440 > localhost.1700: UDP, length 46

the timestamp 3030854628 its form 2066!

i checked the time on loraserver, gateways and are ok, same timezone and correct date…

im clueless about this,…

It is not. This timestamp starts at 0 when you boot your gateway and starts counting from there so it is just a counter. See also: https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT#L135.

To solve the issue, you need to find out what changed to your infrastructure. E.g. it could be a latency issue in your network.

Thanks you @brocaar, nothing changed on the network, the loraserver and gateway are in the same LAN,

We tried continously ping each other and the response time are 1ms or less with no packet loss,

Any other way to deal with this?