Skip to content

Join requests received are considered as unexpected #2122

@adcoly

Description

@adcoly

Expected Behavior

I install two different gateways on the same Network.
The first one (lbs version 2.0.5) handle properly each device we work with.
The second has a different version of LBS (2.0.6) should also work (same configurations, same deployment).

Current Behavior

Join Requests handled by the second gateway are considered as "unexpected" by the LNS.

Context (Environment)

Device (Host) Operating System

Ubuntu 20.04

Architecture

x64

Container Operating System

Linux Containers

LoRaWAN Module Version

2.2.1

Docker

20.10.25+azure-2

Logs

We notice an additional parameter in the Join Request from the 2nd Gateway: "fts"
Here is a join request from the operational Gateway:

<GatewayID> Received 'jreq' message: '{"msgtype":"jreq","MHdr":0,"JoinEui":"<JoinEUI>","DevEui":"<DevEUI>","DevNonce":18307,"MIC":1914631336,"RefTime":0.000000,"DR":5,"Freq":470700000,"upinfo":{"rctx":0,"xtime":25332748023622995,"gpstime":0,"rssi":-40,"snr":9.5,"rxtime":1704768074.358533}}'.

Here a "failing" join request from the 2nd Gateway:

<GatewayID> Received 'jreq' message: '{"msgtype":"jreq","MHdr":0,"JoinEui":"<JoinEUI>","DevEui":"<DevEUI>","DevNonce":3020,"MIC":1613391280,"RefTime":0.000000,"DR":5,"Freq":470500000,"upinfo":{"rctx":0,"xtime":1050702827,"gpstime":0,"fts":-1,"rssi":-102,"snr":1.75,"rxtime":1704848901.805680}}'.
<GatewayID> Received unexpected 'jreq' message: {"msgtype":"jreq","MHdr":0,"JoinEui":"<JoinEUI>","DevEui":"<DevEUI>","DevNonce":3020,"MIC":1613391280,"RefTime":0.000000,"DR":5,"Freq":470500000,"upinfo":{"rctx":0,"xtime":1050702827,"gpstime":0,"fts":-1,"rssi":-102,"snr":1.75,"rxtime":1704848901.805680}}.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions