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 new status for IP Address #7318

New Issue
Closed
opened 2025-12-29 20:21:42 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:21:42 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Dec 4, 2022).

NetBox version

v3.3.9

Feature type

Change to existing functionality

Proposed functionality

IP Addresses within NetBox have allowed statues of the following:

  • Active
  • Reserved
  • Deprecated
  • DHCP
  • SLAAC

I would like to request to add an additional statuses

  • Available
  • Inactive

It would be nice to have both for the greatest flexibility in use cases.

Use case

In my specific use case, it would be nice to be able to add IP addresses and mark their status as 'available' for use. The IP's aren't 'active' in the sense they have a device attached to them and are pingable. So we prefer not to mark IP's as active unless they are associated with a device.

By adding the additional status we would add an IP address to NetBox and mark it as available so other team members knew this IP was available for whatever role. We understand there is a status of 'reserved', but in this example the IP's aren't reserved for any particular device/function .. they are available for someone to assign. (manually, and not DHCP so status of DHCP also doesn't apply)

Database changes

None

External dependencies

None

Originally created by @ghost on GitHub (Dec 4, 2022). ### NetBox version v3.3.9 ### Feature type Change to existing functionality ### Proposed functionality IP Addresses within NetBox have allowed statues of the following: - Active - Reserved - Deprecated - DHCP - SLAAC I would like to request to add an additional statuses - Available - Inactive It would be nice to have both for the greatest flexibility in use cases. ### Use case In my specific use case, it would be nice to be able to add IP addresses and mark their status as 'available' for use. The IP's aren't 'active' in the sense they have a device attached to them and are pingable. So we prefer not to mark IP's as active unless they are associated with a device. By adding the additional status we would add an IP address to NetBox and mark it as available so other team members knew this IP was available for whatever role. We understand there is a status of 'reserved', but in this example the IP's aren't reserved for any particular device/function .. they are available for someone to assign. (manually, and not DHCP so status of DHCP also doesn't apply) ### Database changes None ### External dependencies None
adam added the type: feature label 2025-12-29 20:21:42 +01:00
adam closed this issue 2025-12-29 20:21:42 +01:00
adam commented 2025-12-29 20:21:42 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Dec 4, 2022):

Already possible to add custom status choices.

https://docs.netbox.dev/en/stable/configuration/data-validation/#field_choices

@kkthxbye-code commented on GitHub (Dec 4, 2022): Already possible to add custom status choices. https://docs.netbox.dev/en/stable/configuration/data-validation/#field_choices
adam commented 2025-12-29 20:21:43 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 4, 2022):

Thank you! That is exactly what I was looking for.

@ghost commented on GitHub (Dec 4, 2022): Thank you! That is exactly what I was looking for.
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 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#7318
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?