Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DevNonce has been reused - LoRaWAN® L2 1.0.4 Specification #55

Open
Praneethsvch opened this issue Apr 14, 2023 · 0 comments
Open

DevNonce has been reused - LoRaWAN® L2 1.0.4 Specification #55

Praneethsvch opened this issue Apr 14, 2023 · 0 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@Praneethsvch
Copy link
Collaborator

DevNonce Overview

According to LoRaWAN® L2 1.0.4 Specification pg 45, for each transmission of a join-request by the end-device, the DevNonce value shall be incremented and stored in non-volatile memory.

"DevNonce is a counter starting at 0 when the end-device is initially powered up and
incremented with every Join-Request. A DevNonce value SHALL never be reused for a given
JoinEUI value. If the end-device can be power-cycled, then DevNonce SHALL be
persistent (e.g., stored in a non-volatile memory). Resetting DevNonce without changing
JoinEUI will cause the Join Server to discard the Join-Requests of the end-device. For each
end-device, the Join Server keeps track of the last DevNonce value used by the end-device
and ignores Join-Requests if DevNonce is not incremented."

Fix/Improvements todo:

  • Increment by 1 for every join-request on the end-deive
  • Store DevNonce in non-volatile memory
@Praneethsvch Praneethsvch added bug Something isn't working enhancement New feature or request labels Apr 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants