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

Poduct Enhancement Request #2311

New Issue
Closed
opened 2025-12-29 17:24:43 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:24:43 +01:00
Owner
Copy Link

Originally created by @jimbod777 on GitHub (Jan 28, 2019).

I am new to using Netbox and I love this product!! It would be nice to see in the 'STATUS' in IP Addresses to have an option to select Not Used. Take for example I have a subnet, 192.168.1.0/30. Of course the first available IP address would be 192.168.1.1 up to 192.168.1.2. Those are your available IPs you have in this subnet. The 192.168.1.0 would be your network and 192.168.1.3 would be your broadcast, which are both un-usable. It would be nice to have this option available, or at least have Netbox Identify when you are using a Network and Broadcast address and have those tagged automatically as unavailable or Not Used.

Originally created by @jimbod777 on GitHub (Jan 28, 2019). I am new to using Netbox and I love this product!! It would be nice to see in the 'STATUS' in IP Addresses to have an option to select Not Used. Take for example I have a subnet, 192.168.1.0/30. Of course the first available IP address would be 192.168.1.1 up to 192.168.1.2. Those are your available IPs you have in this subnet. The 192.168.1.0 would be your network and 192.168.1.3 would be your broadcast, which are both un-usable. It would be nice to have this option available, or at least have Netbox Identify when you are using a Network and Broadcast address and have those tagged automatically as unavailable or Not Used.
adam closed this issue 2025-12-29 17:24:43 +01:00
adam commented 2025-12-29 17:24:43 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (Jan 28, 2019):

Please edit your Issue with using one of the templates provided here.
I like your Idea but you have to use one of the templates (Yours would be the "Feature Request") otherwise this issue will be closed.

@tb-killa commented on GitHub (Jan 28, 2019): Please edit your Issue with using one of the templates provided [here](https://github.com/digitalocean/netbox/issues/new/choose). I like your Idea but you have to use one of the templates (Yours would be the "Feature Request") otherwise this issue will be closed.
adam commented 2025-12-29 17:24:44 +01:00
Author
Owner
Copy Link

@jimbod777 commented on GitHub (Jan 28, 2019):

###Environment
*Python version: 3.6
*NetBox version: 2.5.3

###Proposed Functionality
Feature Request.
In IP Addresses have the ability to choose Not Used or auto tag Network and Broadcast Address as Not Used.

###Use Case
It would be nice to see in the 'STATUS' in IP Addresses to have an option to select Not Used. Take for example I have a subnet, 192.168.1.0/30. Of course the first available IP address would be 192.168.1.1 up to 192.168.1.2. Those are your available IPs you have in this subnet. The 192.168.1.0 would be your network and 192.168.1.3 would be your broadcast, which are both un-usable. It would be nice to have this option available, or at least have Netbox Identify when you are using a Network and Broadcast address and have those tagged automatically as unavailable or Not Used.

###Database Changes
Yes

###External Dependencies
No

@jimbod777 commented on GitHub (Jan 28, 2019): ###Environment *Python version: 3.6 *NetBox version: 2.5.3 ###Proposed Functionality Feature Request. In IP Addresses have the ability to choose Not Used or auto tag Network and Broadcast Address as Not Used. ###Use Case It would be nice to see in the 'STATUS' in IP Addresses to have an option to select Not Used. Take for example I have a subnet, 192.168.1.0/30. Of course the first available IP address would be 192.168.1.1 up to 192.168.1.2. Those are your available IPs you have in this subnet. The 192.168.1.0 would be your network and 192.168.1.3 would be your broadcast, which are both un-usable. It would be nice to have this option available, or at least have Netbox Identify when you are using a Network and Broadcast address and have those tagged automatically as unavailable or Not Used. ###Database Changes Yes ###External Dependencies No
adam commented 2025-12-29 17:24:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 29, 2019):

If an IP address is unused, it should not be created in NetBox. Please post to the mailing list if you'd like further clarification on the object's intended use.

@jeremystretch commented on GitHub (Jan 29, 2019): If an IP address is unused, it should not be created in NetBox. Please post to the mailing list if you'd like further clarification on the object's intended use.
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#2311
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?