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

Highlight IP addresses in IP addresses table when duplicates exist #5562

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

Originally created by @rhyser9 on GitHub (Oct 26, 2021).

NetBox version

v3.0.4

Feature type

Change to existing functionality

Proposed functionality

When viewing the detail page for an IP address (/ipam/ip-addresses//), one of the tables on the right shows duplicate IP addresses if they exist.

image

This feature request is to extend that functionality to the IP Addresses table (/ipam/ip-addresses/) by highlighting the row red if a duplicate IP address exists. This would be similar to the styling being worked on for the interfaces table in #6925.

I imagine checking for duplicate IPs introduces a decent performance overhead when querying the database, so perhaps an alternative would be to introduce an optional boolean column (similar to the "Assigned" column) that displays this information. As I understand it from recent live coding streams, the optional columns won't run that query if they aren't actually displayed (like the rack space, rack power, and IP prefix utilization columns), so this would enable the end user to decide when and if that performance impact is acceptable.

Use case

Enables the end user to quickly and easily identify whether multiple instances of an IP address exists. For example, I recently imported a list of IPs and hostnames, some of which already existed in Netbox. There's no clear indicator of which IPs are duplicates without close inspection.

image

Database changes

No response

External dependencies

No response

Originally created by @rhyser9 on GitHub (Oct 26, 2021). ### NetBox version v3.0.4 ### Feature type Change to existing functionality ### Proposed functionality When viewing the detail page for an IP address (/ipam/ip-addresses/<id>/), one of the tables on the right shows duplicate IP addresses if they exist. ![image](https://user-images.githubusercontent.com/3577982/138942714-ff0cc5f5-f6ff-46f0-85c1-0dec530592de.png) This feature request is to extend that functionality to the IP Addresses table (/ipam/ip-addresses/) by highlighting the row red if a duplicate IP address exists. This would be similar to the styling being worked on for the interfaces table in #6925. I imagine checking for duplicate IPs introduces a decent performance overhead when querying the database, so perhaps an alternative would be to introduce an optional boolean column (similar to the "Assigned" column) that displays this information. As I understand it from recent live coding streams, the optional columns won't run that query if they aren't actually displayed (like the rack space, rack power, and IP prefix utilization columns), so this would enable the end user to decide when and if that performance impact is acceptable. ### Use case Enables the end user to quickly and easily identify whether multiple instances of an IP address exists. For example, I recently imported a list of IPs and hostnames, some of which already existed in Netbox. There's no clear indicator of which IPs are duplicates without close inspection. ![image](https://user-images.githubusercontent.com/3577982/138942413-ed145f76-e11a-4871-bf0b-331933ebb982.png) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:29:24 +01:00
adam closed this issue 2025-12-29 19:29:24 +01:00
adam commented 2025-12-29 19:29:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 27, 2021):

Makes sense to me. I think the tricky bit will be passing the current IP address as context to the table, but it should be doable.

I assume you'd then remove the "duplicate IPs" table entirely, since it's redundant at that point?

@jeremystretch commented on GitHub (Oct 27, 2021): Makes sense to me. I think the tricky bit will be passing the current IP address as context to the table, but it should be doable. I assume you'd then remove the "duplicate IPs" table entirely, since it's redundant at that point?
adam commented 2025-12-29 19:29:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 27, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 27, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:29:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 27, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 27, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#5562
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?