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

Mapping between used Prefixes and IP Addresses availability #6292

New Issue
Closed
opened 2025-12-29 19:39:03 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:39:03 +01:00
Owner
Copy Link

Originally created by @VictorPetrescu on GitHub (Apr 5, 2022).

NetBox version

v3.1.10

Feature type

New functionality

Proposed functionality

You should not be allowed to allocate an IP Addresses from the /30 child Prefix. Or even to mark them as used in the IP Addresses View.

Use case

Prefix: 192.168.100.0/24
Child Prefix 1: 192.168.100.32/30 (Marked as 100% Utilized)
Child Prefix 2: 192.168.100.36/30 (Marked as 100% Utilized)
Child Prefix 3: 192.168.100.40/30 (Marked as 100% Utilized)

Under the IP Addresses Section in the 192.168.100.0/24 Prefix I should not be allowed to alocate an IP Address from none of the 3 Child Prefixes, or at least to see them used, not available, like in the picture.

192.168.100.34 says is available, and I could add 192.168.100.33/32 and 192.168.100.37/32, even though there part of a fully utilized prefix.

Screenshot_98

Also in the IP Addresses Section from the Child Prefix (192.168.100.32/30) there are still Available IPs.

Let's say I give /30 to a customer 1...I have to know that when I allocate an IP Address to another customer 2, I don't use one from the range given to customer 1.

Thank you.

Database changes

No response

External dependencies

No response

Originally created by @VictorPetrescu on GitHub (Apr 5, 2022). ### NetBox version v3.1.10 ### Feature type New functionality ### Proposed functionality You should not be allowed to allocate an IP Addresses from the /30 child Prefix. Or even to mark them as used in the IP Addresses View. ### Use case [](https://user-images.githubusercontent.com/11586456/161392652-c0c63d8b-a7e3-481f-bc2e-604b2c17d0df.png)Prefix: 192.168.100.0/24 Child Prefix 1: 192.168.100.32/30 (Marked as 100% Utilized) Child Prefix 2: 192.168.100.36/30 (Marked as 100% Utilized) Child Prefix 3: 192.168.100.40/30 (Marked as 100% Utilized) Under the IP Addresses Section in the 192.168.100.0/24 Prefix I should not be allowed to alocate an IP Address from none of the 3 Child Prefixes, or at least to see them used, not available, like in the picture. 192.168.100.34 says is available, and I could add 192.168.100.33/32 and 192.168.100.37/32, even though there part of a fully utilized prefix. ![Screenshot_98](https://user-images.githubusercontent.com/11586456/161742508-777a7e61-0076-4d5c-beb6-e7195df8b371.png) Also in the IP Addresses Section from the Child Prefix (192.168.100.32/30) there are still Available IPs. Let's say I give /30 to a customer 1...I have to know that when I allocate an IP Address to another customer 2, I don't use one from the range given to customer 1. Thank you. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:39:03 +01:00
adam closed this issue 2025-12-29 19:39:03 +01:00
adam commented 2025-12-29 19:39:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 7, 2022):

You should not be allowed to allocate an IP Addresses from the /30 child Prefix. Or even to mark them as used in the IP Addresses View.

Why would this not be allowed? They are valid IP addresses just like any other.

@jeremystretch commented on GitHub (Apr 7, 2022): > You should not be allowed to allocate an IP Addresses from the /30 child Prefix. Or even to mark them as used in the IP Addresses View. Why would this not be allowed? They are valid IP addresses just like any other.
adam commented 2025-12-29 19:39:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 22, 2022):

Closing due to lack of response.

@jeremystretch commented on GitHub (Apr 22, 2022): Closing due to lack of response.
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 status: revisions needed 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#6292
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?