Node session information disappeared in web-interface about chirpstack-application-server HOT 4 CLOSED

Thanks for your answer. Does it mean that the node session will be expired after 5 days of inactivity?

from chirpstack-application-server.

Hi @samng6 it is a bit hard to make any conclusions based on this information.

Note that there are two components:

• LoRa Server: stores node-sessions in Redis (which will eventually expire)
• LoRa App Server: stores node config in PostgreSQL (which will never expire)

LoRa App Server stores NwkSKey and AppSKey in PostgreSQL, but this does not mean the session is still active, as it might already be expired (in LoRa Server).

from chirpstack-application-server.

Just to be sure, does this mean that it is expected behavior for all ABP sessions to eventually expire? If this is the case, is only OTAA considered to be usable long-term?

from chirpstack-application-server.

Currently yes (note that the TTL is reset after each activity), see also: brocaar/chirpstack-network-server#100. I think there is room for improvement here, but currently this is still todo (the vars are defined here https://github.com/brocaar/loraserver/blob/master/internal/common/vars.go#L16).

from chirpstack-application-server.