Skip to content

Changes on IP-Ranges for better view in prefixes #10506

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pboatone opened this issue Sep 29, 2022 · 1 comment
Closed

Changes on IP-Ranges for better view in prefixes #10506

pboatone opened this issue Sep 29, 2022 · 1 comment
Labels
status: duplicate This issue has already been raised type: feature Introduction of new functionality to the application

Comments

@pboatone
Copy link

NetBox version

v3.3.4

Feature type

Change to existing functionality

Proposed functionality

It should be possible for IP ranges to be marked as "Mark utilized", so that the IP range is not only displayed under "Child Ranges" in a prefix, but also under IP address.
This offers the possibility to see directly in an IP prefix which IP addresses are not free.

It is currently the case that the IP addresses in the IP prefix are displayed as free despite the existing range.

In addition, when creating IP addresses, a warning would be useful if this collided with an IP range. It would be possible to define an IP as static for this range.

Use case

It simplifies entering IP addresses and you can see directly whether an IP address collides with a range that serves as an example for DHCP.

Database changes

External dependencies

@pboatone pboatone added the type: feature Introduction of new functionality to the application label Sep 29, 2022
@jeremystretch
Copy link
Member

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #7947 for further discussion.

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Oct 3, 2022
@jeremystretch jeremystretch added the status: duplicate This issue has already been raised label Oct 3, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants