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

gnrc_lorawan: downlink data might not be received when using ABP. #16962

Open
jia200x opened this issue Oct 7, 2021 · 1 comment
Open

gnrc_lorawan: downlink data might not be received when using ABP. #16962

jia200x opened this issue Oct 7, 2021 · 1 comment
Labels
Area: LoRa Area: LoRa radio support State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT

Comments

@jia200x
Copy link
Member

jia200x commented Oct 7, 2021

Description

There are some scenarios where the LoRaWAN Network Server will try to negotiate RX configuration for ABP nodes using Fopts.
GNRC LoRaWAN only implements a minimal sets of Fopts, so it will simply ignore some of this Fopts.

Some Network Servers such as TTNv3 or the newer version of Chirpstack will keep sending these Fopts requests until the node replies, delaying the scheduled downlink forever. Therefore, an application would never receive any downlink data under these circumstances.

This issue DOES NOT affect OTAA nodes. (and in fact, OTAA should be always preferred regardless of the issue due to security reasons.

The only solution would be to implement the following Fopts:

  • RXParamSetupReq
  • DevStatusReq
  • NewChannnelReq
  • RXTimingSetup

Exptected results

A node running examples/gnrc_lorawan should be able to receive DL frames when joining with ABP (using TTNv3 or the newest Chirpstack)

Actual results

The node will never receive a downlink under the circumstances.

@jia200x jia200x added Type: new feature The issue requests / The PR implemements a new feature for RIOT Area: LoRa Area: LoRa radio support labels Oct 7, 2021
@stale
Copy link

stale bot commented Apr 17, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Apr 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: LoRa Area: LoRa radio support State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
None yet
Development

No branches or pull requests

1 participant