You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
the function "lw_mtype_msg_up" is used for parsing up & down messages. a little bit confusing but ok. But while calculating the MIC you use in BOTH cases the fcnt32 of up messages.
Is this your intention or a bug?
I think the current implementation will give an error for framecounts > 16 bit. For down messages you should select the global 32bit down fcnt,
The text was updated successfully, but these errors were encountered:
Hi @tothero
Thank you for your feedback. Agree with you parse downlink message through lw_mtype_msg_up is messy, the idea is to reuse APIs, because down/up messages are very similar. I'll see if there is clean way to do it, maybe rename the api to a general one like lw_mtype_msg and call it in lw_mtype_msg_up and lw_mtype_msg_down functions.
I didn't do test again. The code is intended to designed like that. Design it in that way the parser can compatible with counter roll back (16 bits only, 32bits counter roll back not supported).
Thanks for your response. I will see if a can make a PR for you after doing some testing at this point. For LoRaWAN 1.1 there will be only 32 Bit Framecounter no 16 Bit are allowed anymore.
Hi,
the function "lw_mtype_msg_up" is used for parsing up & down messages. a little bit confusing but ok. But while calculating the MIC you use in BOTH cases the fcnt32 of up messages.
Is this your intention or a bug?
I think the current implementation will give an error for framecounts > 16 bit. For down messages you should select the global 32bit down fcnt,
The text was updated successfully, but these errors were encountered: