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

Collapsable DHCP IP ranges #6506

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

Originally created by @inigoleaga on GitHub (May 24, 2022).

NetBox version

v3.2.2

Feature type

New functionality

Proposed functionality

It would be nice if you could collapse (and uncollapse) a consecutive list of IPs which status is "DHCP".

Use case

Sometimes, you can find a large DHCP IP pool that messes up the "IP Address" tab of a prefix:

image

It would be helpful to see a unique line that represents the hole DHCP IP pool. That way, the rest of the manually assigned IPs would be seen, removing some importance to the DHCP range, since in some cases it does not provide much valuable information.

Database changes

External dependencies

Originally created by @inigoleaga on GitHub (May 24, 2022). ### NetBox version v3.2.2 ### Feature type New functionality ### Proposed functionality It would be nice if you could collapse (and uncollapse) a consecutive list of IPs which status is "DHCP". ### Use case Sometimes, you can find a large DHCP IP pool that messes up the "IP Address" tab of a prefix: ![image](https://user-images.githubusercontent.com/43034818/170004334-905fafb0-d9bf-4347-bf0a-c5cd14773bcb.png) It would be helpful to see a unique line that represents the hole DHCP IP pool. That way, the rest of the manually assigned IPs would be seen, removing some importance to the DHCP range, since in some cases it does not provide much valuable information. ### Database changes - ### External dependencies -
adam added the type: feature label 2025-12-29 19:41:42 +01:00
adam closed this issue 2025-12-29 19:41:42 +01:00
adam commented 2025-12-29 19:41:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 24, 2022):

The simple solution is to use the IP range model, which was introduced specifically for this purpose.

@jeremystretch commented on GitHub (May 24, 2022): The simple solution is to use the IP range model, which was introduced specifically for this purpose.
adam commented 2025-12-29 19:41:43 +01:00
Author
Owner
Copy Link

@inigoleaga commented on GitHub (May 24, 2022):

I actually have the same "issue" if I create an IP range:
image

If I check the IPs under the "IP range" I see the same:
image

And If I remove the IPs they will be presented as "available" when they are not:
image

@inigoleaga commented on GitHub (May 24, 2022): I actually have the same "issue" if I create an IP range: ![image](https://user-images.githubusercontent.com/43034818/170060615-386ebe3e-2b85-4594-9a11-b9f3bb1e69ff.png) If I check the IPs under the "IP range" I see the same: ![image](https://user-images.githubusercontent.com/43034818/170061659-e5775e44-ac7d-4a3d-be55-1cd61945f76e.png) And If I remove the IPs they will be presented as "available" when they are not: ![image](https://user-images.githubusercontent.com/43034818/170061002-e8e0901b-a39a-4c36-b83c-902f9c0be486.png)
adam commented 2025-12-29 19:41:43 +01:00
Author
Owner
Copy Link

@nem1989 commented on GitHub (Jul 18, 2022):

I'm having the same issue here. When I define an IP range, DHCP for instance, all of it's IP addresses still count as available in prefix.
For example let's say I have a subnet (192.168.1.0/24) with a gateway (192.168.1.1) and DHCP range 192.168.1.2 - 192.168.1.99.
Then in Netbox I define:

  • a prefix 192.168.1.0/24
  • an IP address 192.168.1.1
  • an IP range 192.168.1.2 - 192.168.1.99 marked as reserved.

Then all IP addresses except 192.168.1.1 are listed as available in prefix 192.168.1.0/24 which is not what I expect to see.
Instead I expect available IP's to start from 192.168.1.100 since there is a reserved IP range in place.

To achieve what I want I have to bulk create individual IP addresses in mentioned range to fill it. Think of it: why do I need ranges if I have to create the whole set of IP's anyway?

Is this going to be fixed? Or is it by design?
It would be great to have a checkbox for IP ranges to mark one as 100% utilized just like we can do with prefixes.

@nem1989 commented on GitHub (Jul 18, 2022): I'm having the same issue here. When I define an IP range, DHCP for instance, all of it's IP addresses still count as available in prefix. For example let's say I have a subnet (192.168.1.0/24) with a gateway (192.168.1.1) and DHCP range 192.168.1.2 - 192.168.1.99. Then in Netbox I define: - a prefix 192.168.1.0/24 - an IP address 192.168.1.1 - an IP range 192.168.1.2 - 192.168.1.99 marked as reserved. Then all IP addresses except 192.168.1.1 are listed as available in prefix 192.168.1.0/24 which is not what I expect to see. Instead I expect available IP's to start from 192.168.1.100 since there is a reserved IP range in place. To achieve what I want I have to bulk create individual IP addresses in mentioned range to fill it. Think of it: why do I need ranges if I have to create the whole set of IP's anyway? Is this going to be fixed? Or is it by design? It would be great to have a checkbox for IP ranges to mark one as 100% utilized just like we can do with prefixes.
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#6506
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?