Skip to content

Disassociate between interface FHRP group assignment options and interface IP address #19262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hzc12321 opened this issue Apr 22, 2025 · 0 comments
Labels
status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application

Comments

@hzc12321
Copy link

hzc12321 commented Apr 22, 2025

NetBox version

v4.2.5

Feature type

Change to existing functionality

Proposed functionality

Existing functionality : When trying to assign FHRP groups to interfaces, only FHRP groups with a related IP address assigned are displayed as options. (I didn't really read the code, but from the system behaviour, "related" means the FHRP group must be assigned an IP address of the same subnet prefix as the interface IP)

Proposed functionality : When trying to assign FHRP groups to interfaces, all FHRP groups should be displayed as options regardless of any relationship between the FHRP group IP and interface IP

There isn't a need to worry about being too hard to find the right FHRP group when hundreds of groups being displayed as mentioned in #8435 . The purpose of "Avoiding the user from having to select from hundreds of potential groups" is already achieved by another functionality where users are allowed to type and quick search within the column.

Related issues :
#18975
#18696

Use case

This is a removal of unnecessary existing restriction. It's not a must that each interface's IP address is under the same parent prefix as the FHRP group's VIP, there could be additional mechanisms like NAT in the middle. For example : We have a whole dedicated subnet specifically used as F5 load-balanced service VIPs, and the VM interface IPs are not from the same subnet.

There is an existing workaround; Assigning FHRP groups to the interface before assigning a physical IP, but this is not clean and not scalable. Once the interface IP is specified, it's painful when there is a need to modify its FHRP group assignments.

Database changes

No response

External dependencies

No response

@hzc12321 hzc12321 added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Apr 22, 2025
@arthanson arthanson added status: under review Further discussion is needed to determine this issue's scope and/or implementation and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants