Skip to content
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

Add support for IP address statuses #87

Closed
bzoel opened this issue Jun 28, 2016 · 3 comments
Closed

Add support for IP address statuses #87

bzoel opened this issue Jun 28, 2016 · 3 comments
Milestone

Comments

@bzoel
Copy link

bzoel commented Jun 28, 2016

Similar to request #36 for reserving rack space without a device, it would be useful to be able to reserve a range of IP space without needing to have an associated device (or 200 separate IP address entries).

For example, in most of our access segments we use a /24. 20-220 are generally handed out by a DHCP server, so we want to be able to note that without specifically tracking devices.

@bzoel bzoel changed the title Add support for reserving IP address ranges [Feature] Add support for reserving IP address ranges Jun 28, 2016
@mdlayher mdlayher changed the title [Feature] Add support for reserving IP address ranges Add support for reserving IP address ranges Jun 30, 2016
@jeremystretch jeremystretch changed the title Add support for reserving IP address ranges Add support for IP address stauses Jul 29, 2016
@jeremystretch
Copy link
Member

Redefining this slightly to entail the addition of a status field to the IPAddress model, similar to what exists on Prefix and VLAN. It should be sufficient to create a number of individual IP address objects to denote reserved IPs.

@bzoel
Copy link
Author

bzoel commented Aug 9, 2016

One thought from me on this - I think the status field does address this issue, but I'm thinking about this from an ease of use perspective.

Sure, I can create 200 IP address objects via bulk creation with the description "DHCP pool" and "used" status, but when I need to decease that pool by 20 IPs, do I have to hit 20 checkboxes? Wondering if there is a better way UI wise to do that.

@jeremystretch
Copy link
Member

Ideally you'll be able to search for e.g. 192.168.0.[180-199], select all, and delete. Still working on the address expansion bit.

@jeremystretch jeremystretch added this to the v1.7 milestone Sep 16, 2016
@jeremystretch jeremystretch changed the title Add support for IP address stauses Add support for IP address statuses Oct 21, 2016
lampwins pushed a commit to lampwins/netbox that referenced this issue Oct 13, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants