Locations not shown when subnet runs out of available IPs
Open
bug
- Dominant language
- Rust
- Stars
- 2.8k
- Forks
- 115
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 51
Description
When a location subnet is configured with range (for example, a /24), and the number of enrolled devices exceeds the available IP addresses in that subnet, the enrollment process completes successfully. Since no additional IP addresses can be assigned within that subnet, the desktop client receives an empty list of locations.
Desktop client show only this, we may need to describe more details in client/core about lack of space in subnet.
Contributor guide
Assessment
This issue has not been assessed yet.