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

Marking IP ranges as 100% utilized #6680

New Issue
Closed
opened 2025-12-29 19:43:50 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:43:50 +01:00
Owner
Copy Link

Originally created by @nem1989 on GitHub (Jul 18, 2022).

Posting a new issue since I've noticed the one that I commented is already closed.
What I'm trying to do is to correctly define a DHCP IP range and prevent admins from assigning IP's from that range to devices/VM's, but when I define an IP range, all of it's IP addresses still count as available in it's parent prefix.

NetBox version

v3.2.6

Steps to reproduce

For example let's say we 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 we 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.

Expected behavior

In parent prefix I should see available IP's starting from 192.168.1.100 since all others are reserved for an IP range.

Actual behavior

In IP addresses tab IP ranges are not visible. 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.
Right now 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?

Proposed functionality

Implement a checkbox for IP ranges to mark one as restricted/utilized or atleast make an option to show IP ranges in IP Addresses list. It would prevent admins from assigning IP's from DHCP or reserved ranges to devices or VM's.

Originally posted by @nem1989 in https://github.com/netbox-community/netbox/issues/9412#issuecomment-1187057428

Originally created by @nem1989 on GitHub (Jul 18, 2022). Posting a new issue since I've noticed the one that I commented is already closed. What I'm trying to do is to correctly define a DHCP IP range and prevent admins from assigning IP's from that range to devices/VM's, but when I define an IP range, all of it's IP addresses still count as available in it's parent prefix. ### NetBox version v3.2.6 ### Steps to reproduce For example let's say we 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 we 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. ### Expected behavior In parent prefix I should see available IP's starting from 192.168.1.100 since all others are reserved for an IP range. ### Actual behavior In IP addresses tab IP ranges are not visible. 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. Right now 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? ### Proposed functionality Implement a checkbox for IP ranges to mark one as restricted/utilized or atleast make an option to show IP ranges in IP Addresses list. It would prevent admins from assigning IP's from DHCP or reserved ranges to devices or VM's. _Originally posted by @nem1989 in https://github.com/netbox-community/netbox/issues/9412#issuecomment-1187057428_
adam closed this issue 2025-12-29 19:43:50 +01:00
adam commented 2025-12-29 19:43:51 +01:00
Author
Owner
Copy Link

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

Please resubmit your issue using one of the approved templates.

@jeremystretch commented on GitHub (Jul 18, 2022): Please resubmit your issue using one of the [approved templates](https://github.com/netbox-community/netbox/issues/new/choose).
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
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#6680
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?