Packet Forwarder - packets rejected

When Im trying to send data from server … The following happens

src/jitqueue.c:251:jit_enqueue(): ERROR: Packet REJECTED, timestamp seems wrong, too much in advance (current=3244624583, packet=2092530435, type=0)

What did i miss?

That is probably because the NS wasn’t able to send the response in time. This could be caused by mis-configuration or high latency between the GW and NS.

how to solve this …??

You could increase the rx_delay for example (chirpstack-network-server.toml), to allow for a longer rountrip time between the uplink and downlink. You might need to re-activate your device(s).

Are you using a cellular gateway?

mine is RAK2245 wireless

Hi @brocaar

we have set rx_delay=5 in chirpstack-network-server.toml but we are not getting any success. still, we are getting below error in packet-forwarder

src/jitqueue.c:251:jit_enqueue(): ERROR: Packet REJECTED, timestamp seems wrong, too much in advance (current=3244624583, packet=2092530435, type=0)

@brocaar
Why does that happen on a CLASS-C device? Class-c listens on rx2 infinitely, so it might worth to schedule transmission on RX2 rather than RX1? Could I force NS to schedule transmission on RX2 settings?

A Class-C device could still send a Class-A uplink, in which case the NS might send a Class-A timestamped downlink back to the device.

The latest ChirpStack test versions contain a refactored downlink queue handling, in which case a failed Class-A downlink for a Class-C device would be sent again using Class-C parameters.