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

Anycast IP address multiple device assignments #719

New Issue
Closed
opened 2025-12-29 16:25:04 +01:00 by adam · 5 comments
adam commented 2025-12-29 16:25:04 +01:00
Owner
Copy Link

Originally created by @contemno on GitHub (Feb 20, 2017).

Minor request: Be able to assign an IP address to more than one device.

Originally created by @contemno on GitHub (Feb 20, 2017). Minor request: Be able to assign an IP address to more than one device.
adam closed this issue 2025-12-29 16:25:04 +01:00
adam commented 2025-12-29 16:25:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 21, 2017):

Just to clarify, IP addresses are assigned to interfaces in NetBox, not devices.

There's nothing special about an anycast IP address other than that it has been intentionally instantiated multiple times. Thus, it should be sufficient to create multiple IP address objects (each with the same IP) to represent anycast address assignment.

It might be appropriate to create an "anycast" role for IP addresses, which is a proposed feature, but discussion on that should be held in #819.

@jeremystretch commented on GitHub (Feb 21, 2017): Just to clarify, IP addresses are assigned to interfaces in NetBox, not devices. There's nothing special about an anycast IP address other than that it has been intentionally instantiated multiple times. Thus, it should be sufficient to create multiple IP address objects (each with the same IP) to represent anycast address assignment. It _might_ be appropriate to create an "anycast" role for IP addresses, which is a proposed feature, but discussion on that should be held in #819.
adam commented 2025-12-29 16:25:05 +01:00
Author
Owner
Copy Link

@specialcircumstances commented on GitHub (Feb 21, 2017):

Would this not be prevented by the prevent duplicate option within a VRF?

@specialcircumstances commented on GitHub (Feb 21, 2017): Would this not be prevented by the prevent duplicate option within a VRF?
adam commented 2025-12-29 16:25:05 +01:00
Author
Owner
Copy Link

@contemno commented on GitHub (Feb 21, 2017):

@specialcircumstances That's correct, it would not be possible if the 'prevent duplicate' option is enabled on a VRF.

The issue I was addressing is when viewing the IP address details page there's no indication that it's an anycast (or virtual) IP address assigned to multiple interfaces (on different devices) within the same VRF. The IP address details page will only list the device and interface associated with the single IP address instance currently being viewed.

The workaround is to disable the 'prevent duplicate' option (if applicable) and label the IP addresses as anycast somewhere in the description field as a cue to the user to manually search for the IP address to find all interfaces (and associated devices) assigned the same IP address in the same VRF.

@contemno commented on GitHub (Feb 21, 2017): @specialcircumstances That's correct, it would not be possible if the 'prevent duplicate' option is enabled on a VRF. The issue I was addressing is when viewing the IP address details page there's no indication that it's an anycast (or virtual) IP address assigned to multiple interfaces (on different devices) within the same VRF. The IP address details page will only list the device and interface associated with the single IP address instance currently being viewed. The workaround is to disable the 'prevent duplicate' option (if applicable) and label the IP addresses as anycast somewhere in the description field as a cue to the user to manually search for the IP address to find all interfaces (and associated devices) assigned the same IP address in the same VRF.
adam commented 2025-12-29 16:25:05 +01:00
Author
Owner
Copy Link

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

It would be awesome if one can link the same IP to multiple interfaces for Anycast, VRRP, HSRP, CARP etc address types. As the "prevent duplicates" option is somewhat mandatory imo this invalidates the usefulness of the above mentioned address types to almost zero.

@ossark commented on GitHub (May 7, 2019): It would be awesome if one can link the same IP to multiple interfaces for Anycast, VRRP, HSRP, CARP etc address types. As the "prevent duplicates" option is somewhat mandatory imo this invalidates the usefulness of the above mentioned address types to almost zero.
adam commented 2025-12-29 16:25:05 +01:00
Author
Owner
Copy Link

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

+1
For anycast operations, by definition, it should be possible to re-use an allocated IP address to multiple devices. Use cases are anycast-rp and anycast DNS.

@njgarfield commented on GitHub (May 7, 2019): +1 For anycast operations, by definition, it should be possible to re-use an allocated IP address to multiple devices. Use cases are anycast-rp and anycast DNS.
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#719
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?