starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Include 'mark populated' ip ranges in utilization calculation of prefix #11188

New Issue
Closed
opened 2025-12-29 21:41:42 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:41:42 +01:00
Owner
Copy Link

Originally created by @GoepiGB on GitHub (May 16, 2025).

NetBox version

v4.3.1

Feature type

Change to existing functionality

Proposed functionality

If a prefix contains an IP range with the new feature 'mark populated' activated, the IP addresses of said range should be added to the prefix's utilization.

Here are 2 prefixes, the first has an IP range marked as populated, the second has none. The usage looks the same for both.
Image

Image

Use case

To see at first glance how high the usage of a given prefix is, even with DHCP active.

Database changes

None I'm aware of

External dependencies

No response

Originally created by @GoepiGB on GitHub (May 16, 2025). ### NetBox version v4.3.1 ### Feature type Change to existing functionality ### Proposed functionality If a prefix contains an IP range with the new feature 'mark populated' activated, the IP addresses of said range should be added to the prefix's utilization. Here are 2 prefixes, the first has an IP range marked as populated, the second has none. The usage looks the same for both. ![Image](https://github.com/user-attachments/assets/70e61bce-5c8e-4105-b5ae-09b9628cabd1) ![Image](https://github.com/user-attachments/assets/41a49a5b-1498-49f3-9339-045b8554c78f) ### Use case To see at first glance how high the usage of a given prefix is, even with DHCP active. ### Database changes None I'm aware of ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:41:42 +01:00
adam closed this issue 2025-12-29 21:41:42 +01:00
adam commented 2025-12-29 21:41:42 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (May 16, 2025):

Hi there! Thanks for the suggestion.

This behavior was actually a design decision when the “mark populated” feature was introduced (see #9763).

If you’d like the populated IPs to contribute to the prefix's utilization, you can enable “mark utilized” alongside “mark populated”. That should give you the result you’re looking for!

@pheus commented on GitHub (May 16, 2025): Hi there! Thanks for the suggestion. This behavior was actually a design decision when the *“mark populated”* feature was introduced ([see #9763](https://github.com/netbox-community/netbox/issues/9763)). If you’d like the populated IPs to contribute to the prefix's utilization, you can enable *“mark utilized”* alongside *“mark populated”*. That should give you the result you’re looking for!
adam commented 2025-12-29 21:41:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 22, 2025):

Thanks @pheus, I think you hit the nail on the head here.

@jeremystretch commented on GitHub (May 22, 2025): Thanks @pheus, I think you hit the nail on the head here.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11188
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?