-
-
Notifications
You must be signed in to change notification settings - Fork 545
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
Devaddr got only 8bytes, wondering if it's enough #56
Comments
sorry, typo |
Hi, |
@ivajloip |
That's my understanding. Note that currently the implementation does not support this. |
@ivajloip , I agree with you. |
Possibly, you could have different neighbouring @yzk0281 I need the |
@ivajloip |
@brocaar |
As long as the networks (with different |
@brocaar @ivajloip |
@yzk0281 Second point, as long as no roaming is required for your network, you have no problem using all the 4 bytes (i.e. without netID) and this was also said during the Munich event. @brocaar Hopefully in a few months we will have access to the specification so that we can tackle those problems :) For now I agree that it is too early. |
This document explains the NetID allocation, and roaming impact, although not clearing the extra use of NwkSKey to unequivocally identify nodes. https://es.scribd.com/document/317164891/20160603-NetID-Alloc-Policy-Application-1178-1 |
By the way, I found something that confirms my understanding about
|
Using the NwkSKey to map a non-unique device address (DevAddr) to a unique DevEUI is sufficient, if the NwkSKey is unique (as recommended).
|
Regarding non unique DevAddr I already found a problem in current loraserver architecture. It is possible to have several nodes with same DevAddr but different DevEUI. If you delete on of nodes all records from Redis for appropriate DevAddr are deleted as well. |
It should not be possible right now to have multiple nodes with the same |
Thanks for reporting this bug 👍 Will look into a fix! |
@iBrick your issue has been solved and released as |
Thank you very much for fixing! I wanted to ask how do you build project. I'm new to Docker and what I do is build it with command 'docker-compose up --build'. It build the binary successfully but recipe for target 'serve' fail. I can use the binary locally afterwards but it doesn't start inside Docker. but still no luck as I get these errors: And what is the way to debug program inside Docker? |
After #68 I'll look into changing the way how the |
I forgot to update this issue after the 0.12.0 release: please note that the node-session api since 0.12.0 now uses the |
I'm currently working on refactoring the session storage so that a single |
This has been implemented in LoRa Server 0.15.0. Please refer to the changelogs for details :-) |
Devaddr got only 8bytes and each nodes need a unique Devaddr,
what if 8 bytes is not enough for all the nodes?
The text was updated successfully, but these errors were encountered: