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

Allow "floating" ip address object types to be assigned to multiple interfaces #2594

New Issue
Closed
opened 2025-12-29 18:20:14 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:20:14 +01:00
Owner
Copy Link

Originally created by @ossark on GitHub (May 7, 2019).

Proposed Functionality

Allow floating address types (HSRP, VRRP, CARP, Anycast etc) to be assignable to several interfaces on different devices.

Use Case

Due to the nature of the above mentioned IP addresses, they are not unique even within a context that mandates uniqueness, it would mimic reality if these address types could be assignable to multiple interfaces.

With the current setting of "prevent duplicates" for IP addresses the above address types are rendered mostly useless. The only way currently of distinguishing the "ownership" of a floating address is either through the description field (very bad) or tags (bad).

With the proposed functionality implemented it would be possible to utilize the floating ip address types properly while not having to create multiple ip address objects that are in fact separate objects in database but the same object in practice thereby breaking the database to reality representation.

Originally created by @ossark on GitHub (May 7, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Proposed Functionality Allow floating address types (HSRP, VRRP, CARP, Anycast etc) to be assignable to several interfaces on different devices. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Due to the nature of the above mentioned IP addresses, they are not unique even within a context that mandates uniqueness, it would mimic reality if these address types could be assignable to multiple interfaces. With the current setting of "prevent duplicates" for IP addresses the above address types are rendered mostly useless. The only way currently of distinguishing the "ownership" of a floating address is either through the description field (very bad) or tags (bad). With the proposed functionality implemented it would be possible to utilize the floating ip address types properly while not having to create multiple ip address objects that are in fact separate objects in database but the same object in practice thereby breaking the database to reality representation.
adam closed this issue 2025-12-29 18:20:14 +01:00
adam commented 2025-12-29 18:20:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 7, 2019):

NetBox modeling virtual/floating IPs and IPs managed by NHRPs (VRRP, etc.) as individual IPs because it may be necessary to track unique attributes of each. For example, VRRP IPs typically each get a different priority value. (This isn't supported currently but see #2456.)

With the current setting of "prevent duplicates" for IP addresses the above address types are rendered mostly useless.

NetBox permits the creation of IP addresses with these roles even if unique address enforcement is enabled. If you can identify a scenario where this does not work, please open a bug and detail the steps someone else can take to reproduce the issue.

@jeremystretch commented on GitHub (May 7, 2019): NetBox modeling virtual/floating IPs and IPs managed by NHRPs (VRRP, etc.) as individual IPs because it may be necessary to track unique attributes of each. For example, VRRP IPs typically each get a different priority value. (This isn't supported currently but see #2456.) > With the current setting of "prevent duplicates" for IP addresses the above address types are rendered mostly useless. NetBox permits the creation of IP addresses with these roles even if unique address enforcement is enabled. If you can identify a scenario where this does not work, please open a bug and detail the steps someone else can take to reproduce the 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
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#2594
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?