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

Provide way to limit DevAddr allocation within NetID #49

Closed
michaeldjeffrey opened this issue Oct 6, 2022 · 0 comments
Closed

Provide way to limit DevAddr allocation within NetID #49

michaeldjeffrey opened this issue Oct 6, 2022 · 0 comments

Comments

@michaeldjeffrey
Copy link
Contributor

Currently ChirpStack will assign a random DevAddr from the entire allowable range of a NetID.
If an operator wanted to limit the range of DevAddrs assigned to devices within their instance, they would not be able to do so.

Adding a configuration setting for DevAddr assignments could look something like

[network]
  net_id = "000001"
  devaddr_range = ["02000000", "020000AA"]

This allows for a few different scenarios.

  • Standing up a test instance of ChirpStack with your own NetID and keeping test devices from bleeding into Production DevAddr space.
  • Multiple operators sharing a NetID without overlapping.
  • Could be used to more quickly deny traffic not meant for the Instance.

There could be a more robust DevAddr allocation scheme that would allow for other scenarios like:

  • Migrating devices across ChirpStack instances that share a NetID.
  • Partitioning DevAddrs within Applications in an Instance.

But that is potentially overcomplicating the ask here.

brocaar added a commit that referenced this issue Oct 19, 2022
This type defines the (NetID derived) prefix that must be used when
generating device addresses. This can be retrieved from the NetID, but
it is also possible to define a prefix that defines a smaller address
range within the NetID.

See also #49.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant