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

Additional IP Address Column #712

New Issue
Closed
opened 2025-12-29 16:25:02 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:25:02 +01:00
Owner
Copy Link

Originally created by @bsakdol on GitHub (Feb 15, 2017).

It would be great to add a "parent" or "prefix" column to the view for IP Addresses so it would be easier to determine which IP's are, for lack of a better word, orphaned from a prefix. When I click on the IP Address menu to view all the "host" IP's, one thing I can't determine without a great deal of effort is which IP's belong to a prefix and which ones have been added without a prefix.

Originally created by @bsakdol on GitHub (Feb 15, 2017). It would be great to add a "parent" or "prefix" column to the view for IP Addresses so it would be easier to determine which IP's are, for lack of a better word, orphaned from a prefix. When I click on the `IP Address` menu to view all the "host" IP's, one thing I can't determine without a great deal of effort is which IP's belong to a prefix and which ones have been added without a prefix.
adam closed this issue 2025-12-29 16:25:02 +01:00
adam commented 2025-12-29 16:25:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 17, 2017):

I'm not sure this makes sense to include in the IP addresses table. There's a significant performance hit to make an additional query for each IP in the list, and it's not information that's going to be needed most of the time. (We're also a bit pressed for horizontal space.)

Orphan IP addresses are probably better detected using a yet-to-be-developed reporting feature that could be run without interfering with the main table.

@jeremystretch commented on GitHub (Feb 17, 2017): I'm not sure this makes sense to include in the IP addresses table. There's a significant performance hit to make an additional query for each IP in the list, and it's not information that's going to be needed most of the time. (We're also a bit pressed for horizontal space.) Orphan IP addresses are probably better detected using a yet-to-be-developed reporting feature that could be run without interfering with the main table.
adam commented 2025-12-29 16:25:02 +01:00
Author
Owner
Copy Link

@bsakdol commented on GitHub (Feb 17, 2017):

To prevent the performance hit of the additional query, maybe it is a better idea to just require a prefix to be created before a host IP can be added. It just seems like there is a pretty big disconnect between the host IP's and the prefixes.

@bsakdol commented on GitHub (Feb 17, 2017): To prevent the performance hit of the additional query, maybe it is a better idea to just require a prefix to be created before a host IP can be added. It just seems like there is a pretty big disconnect between the host IP's and the prefixes.
adam commented 2025-12-29 16:25:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 17, 2017):

maybe it is a better idea to just require a prefix to be created before a host IP can be added

Not everyone wants to use NetBox this way. It's a perfectly valid use case to have IPs which don't belong to a parent prefix. For example, you might want to track the IPs assigned to WAN interfaces on CPE devices, but don't care about the prefixes in use on those circuits. (Also, it wouldn't do anything to address the performance concern when listing IP addresses.)

@jeremystretch commented on GitHub (Feb 17, 2017): > maybe it is a better idea to just require a prefix to be created before a host IP can be added Not everyone wants to use NetBox this way. It's a perfectly valid use case to have IPs which don't belong to a parent prefix. For example, you might want to track the IPs assigned to WAN interfaces on CPE devices, but don't care about the prefixes in use on those circuits. (Also, it wouldn't do anything to address the performance concern when listing IP addresses.)
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#712
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?