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

IP ranges: add new toggle "Ignore in prefix utilization" #8207

New Issue
Closed
opened 2025-12-29 20:33:48 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:33:48 +01:00
Owner
Copy Link

Originally created by @stavr666 on GitHub (Jun 18, 2023).

NetBox version

v3.5.3

Feature type

Change to existing functionality

Proposed functionality

Add new option to create/edit IP range form:
image

Use case

While keep UI and API "next available IP" functionality (ranges helps there), provide more accurate Prefix utilization information for some cases:

  • systematically reserved in most prefixes ranges of IP;
  • automated DHCP management scenarios, where all DHCP actual clients is registered in Netbox.

Example:
image

2 ranges exist for prefix:

  • reserved for network team, that prevents for accidentally put some static in defined range;
  • DHCP range, that both prevents from creation static, and use in external scripts for DHCP configuration.

For some prefixes (/23 and narrower), I'd prefer to know, how many IPs actually available (Utilization and Available IPs in UI), ignoring Ranges. This way I can make an informed decision about where to place a new project, which it is supposed to allocate a certain IP pool, without checking each time all "100% utilized" Prefixes.

Database changes

No response

External dependencies

No response

Originally created by @stavr666 on GitHub (Jun 18, 2023). ### NetBox version v3.5.3 ### Feature type Change to existing functionality ### Proposed functionality Add new option to create/edit IP range form: ![image](https://github.com/netbox-community/netbox/assets/84839985/41d16c96-4673-497f-b71b-bd35f5ae5163) ### Use case While keep UI and API "next available IP" functionality (ranges helps there), provide more accurate Prefix utilization information for some cases: - systematically reserved in most prefixes ranges of IP; - automated DHCP management scenarios, where all DHCP actual clients is registered in Netbox. Example: ![image](https://github.com/netbox-community/netbox/assets/84839985/065e58d0-5649-4bd1-9a12-d7d260027d8e) 2 ranges exist for prefix: - reserved for network team, that prevents for accidentally put some static in defined range; - DHCP range, that both prevents from creation static, and use in external scripts for DHCP configuration. For some prefixes (/23 and narrower), I'd prefer to know, how many IPs actually available (Utilization and Available IPs in UI), ignoring Ranges. This way I can make an informed decision about where to place a new project, which it is supposed to allocate a certain IP pool, without checking each time all "100% utilized" Prefixes. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:33:48 +01:00
adam closed this issue 2025-12-29 20:33:48 +01:00
adam commented 2025-12-29 20:33:49 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 17, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 17, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:33:49 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 17, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 17, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#8207
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?