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
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
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.
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
This allows for a few different scenarios.
There could be a more robust DevAddr allocation scheme that would allow for other scenarios like:
But that is potentially overcomplicating the ask here.
The text was updated successfully, but these errors were encountered: