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

Display fhrp group's addresses on assigned interfaces #7915

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

Originally created by @nicolas-janzen on GitHub (Apr 17, 2023).

NetBox version

v3.4.8

Feature type

Data model extension

Proposed functionality

Extend NetBox to display FHRP group IP addresses on the device's interfaces tab and the specific interface.

The proposed change would allow users to see the virtual IP addresses associated with an FHRP group directly on the device's interfaces tab and the specific interface page, making it easier to understand the relationship between devices, interfaces, and FHRP groups.

Use case

Currently, NetBox supports FHRP groups for documentation purposes, but it does not directly display the IP addresses associated with an FHRP group on the interfaces tab or the specific interface page. This requires users to navigate to the FHRP group details page to view the associated IP addresses, which can be time-consuming and inconvenient.

By displaying FHRP group IP addresses on the interfaces tab and the specific interface page, users can easily understand the relationship between devices, interfaces, and FHRP configurations without the need for additional navigation.

It would also improve integration with automation tools like Ansible.

Database changes

This feature may require changes to the database schema to store the relationship between FHRP groups, IP addresses, and device interfaces. A migration script might be needed to update existing database records.

External dependencies

None.

Originally created by @nicolas-janzen on GitHub (Apr 17, 2023). ### NetBox version v3.4.8 ### Feature type Data model extension ### Proposed functionality Extend NetBox to display FHRP group IP addresses on the device's interfaces tab and the specific interface. The proposed change would allow users to see the virtual IP addresses associated with an FHRP group directly on the device's interfaces tab and the specific interface page, making it easier to understand the relationship between devices, interfaces, and FHRP groups. ### Use case Currently, NetBox supports FHRP groups for documentation purposes, but it does not directly display the IP addresses associated with an FHRP group on the interfaces tab or the specific interface page. This requires users to navigate to the FHRP group details page to view the associated IP addresses, which can be time-consuming and inconvenient. By displaying FHRP group IP addresses on the interfaces tab and the specific interface page, users can easily understand the relationship between devices, interfaces, and FHRP configurations without the need for additional navigation. It would also improve integration with automation tools like Ansible. ### Database changes This feature may require changes to the database schema to store the relationship between FHRP groups, IP addresses, and device interfaces. A migration script might be needed to update existing database records. ### External dependencies None.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:29:57 +01:00
adam closed this issue 2025-12-29 20:29:58 +01:00
adam commented 2025-12-29 20:29:58 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 4, 2023):

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 (Aug 4, 2023): 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/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:29:58 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 4, 2023):

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 (Sep 4, 2023): 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.
adam commented 2025-12-29 20:29:58 +01:00
Author
Owner
Copy Link

@nicolas-janzen commented on GitHub (Sep 27, 2023):

I think this is a crucial feature which a lot people would benefit from, also looking at this issue.

@nicolas-janzen commented on GitHub (Sep 27, 2023): I think this is a crucial feature which a lot people would benefit from, also looking at [this](https://github.com/netbox-community/ansible_modules/issues/1029) issue.
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#7915
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?