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 column in Interfaces tables for Virtual IPs in assigned FHRP groups #10506

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

Originally created by @mskalecki on GitHub (Nov 22, 2024).

NetBox version

v4.1.6

Feature type

New functionality

Triage priority

I volunteer to perform this work (if approved)

Proposed functionality

Add an available column for the Interfaces table that displays a list of the Virtual IPs assigned to the FHRP groups assigned to the interface.

The new column would look like the existing IP Adresses column, expect it would show the associated virtual IPs instead of the directly assigned IPs.

Use case

Being able to see the virtual IPs associated with an interface is useful for the same reasons it's useful to see the directly assigned IP addresses.

I think it's especially useful when modeling HA clusters in something like a Fortigate Firewall, where the individual unit interfaces don't have dedicated IPs at all. Without seeing the Virtual IPs, you have no immediate indication of what net is on the interface at all. The existing column for showing the FHRP group is not as useful as seeing the Virtual IPs for my use case.

I have a PR ready that is running on my own instance.

Database changes

None

External dependencies

None

Originally created by @mskalecki on GitHub (Nov 22, 2024). ### NetBox version v4.1.6 ### Feature type New functionality ### Triage priority I volunteer to perform this work (if approved) ### Proposed functionality Add an available column for the Interfaces table that displays a list of the Virtual IPs assigned to the FHRP groups assigned to the interface. The new column would look like the existing `IP Adresses` column, expect it would show the associated virtual IPs instead of the directly assigned IPs. ### Use case Being able to see the virtual IPs associated with an interface is useful for the same reasons it's useful to see the directly assigned IP addresses. I think it's especially useful when modeling HA clusters in something like a Fortigate Firewall, where the individual unit interfaces don't have dedicated IPs at all. Without seeing the Virtual IPs, you have no immediate indication of what net is on the interface at all. The existing column for showing the FHRP group is not as useful as seeing the Virtual IPs for my use case. I have a PR ready that is running on my own instance. ### Database changes None ### External dependencies None
adam added the type: featurestatus: needs ownerpending closurecomplexity: low labels 2025-12-29 21:32:22 +01:00
adam closed this issue 2025-12-29 21:32:22 +01:00
adam commented 2025-12-29 21:32:23 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 25, 2025):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 25, 2025): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:32:23 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 25, 2025):

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 (May 25, 2025): 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 complexity: low 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#10506
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?