-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix for LoRaWAN downlink sequence counter rollover #10154
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Thanks.
@itziardelatorre, thank you for your changes. |
CI started |
Too early, aborted, will restart once other rc4 fixes complete. |
Test run: FAILEDSummary: 8 of 9 test jobs failed Failed test jobs:
|
@0xc0170 Failures seem to be unrelated to the PR. Is it possible to kick start the CI again ? |
restarting CI |
Test run: SUCCESSSummary: 13 of 13 test jobs passed |
Fix for LoRaWAN downlink sequence counter rollover
Description
Fix issue related to downlink sequence counter rollover in LoRaWAN.
For the test, the downlink sequence counter of the downlink messages has been incremented by 1600 (< MAX_FCNT_GAP) several times. For example, until 64005 and following situation was shown:
Downlink sequence counter increased to 64005 (by 1600 steps)
The radio module accepts this, as expected.
After that, downlink sequence counter increased to 65536 (rollover for 32 bits sequence counter)
The radio module rejects this frame
With the change everything works fine.
Pull request type
Reviewers
Release Notes