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

Add support for IP address statuses #56

New Issue
Closed
opened 2025-12-29 15:30:56 +01:00 by adam · 3 comments
adam commented 2025-12-29 15:30:56 +01:00
Owner
Copy Link

Originally created by @bzoel on GitHub (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.

Originally created by @bzoel on GitHub (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.
adam closed this issue 2025-12-29 15:30:56 +01:00
adam commented 2025-12-29 15:30:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2016):

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.

@jeremystretch commented on GitHub (Jul 29, 2016): 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.
adam commented 2025-12-29 15:30:58 +01:00
Author
Owner
Copy Link

@bzoel commented on GitHub (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.

@bzoel commented on GitHub (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.
adam commented 2025-12-29 15:30:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 9, 2016):

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 commented on GitHub (Aug 9, 2016): 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.
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#56
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?