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 interface binding #2597

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

Originally created by @njgarfield on GitHub (May 8, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.5.12

Proposed Functionality

This request is to allow a single IP address in a VRF to be bound to multiple devices. The currently functionality does not allow this. If I bind an IP address to a specific device interface and then navigate to another second device interface, when I bind an IP address on that second device interface the IP address is deleted from the first device.

Use Case

For hundreds of servers running a routing daemon (e.g. FRR/quagga/bird), the same anycast address could be configured on a loopback interface. This is very common in CDN and DNS provider networks.
Similarly for anycast RP in multicast networks.

Database Changes

Perhaps. not sure.

External Dependencies

None.

Originally created by @njgarfield on GitHub (May 8, 2019). ### Environment * Python version: 3.6 * NetBox version: 2.5.12 ### Proposed Functionality This request is to allow a single IP address in a VRF to be bound to multiple devices. The currently functionality does not allow this. If I bind an IP address to a specific device interface and then navigate to another second device interface, when I bind an IP address on that second device interface the IP address is deleted from the first device. ### Use Case For hundreds of servers running a routing daemon (e.g. FRR/quagga/bird), the same anycast address could be configured on a loopback interface. This is very common in CDN and DNS provider networks. Similarly for anycast RP in multicast networks. ### Database Changes Perhaps. not sure. ### External Dependencies None.
adam closed this issue 2025-12-29 18:20:15 +01:00
adam commented 2025-12-29 18:20:15 +01:00
Author
Owner
Copy Link

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

This issue has been closed as it does not conform to one of the provided templates as required by the contributing guide. If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).

@jeremystretch commented on GitHub (May 8, 2019): This issue has been closed as it does not conform to one of the [provided templates](https://github.com/digitalocean/netbox/issues/new/choose) as required by the [contributing guide](https://github.com/digitalocean/netbox/blob/master/CONTRIBUTING.md). If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).
adam commented 2025-12-29 18:20:16 +01:00
Author
Owner
Copy Link

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

Environment

  • Python version: 3.6
  • NetBox version: 2.5.12

Proposed Functionality

This request is to allow a single IP address in a VRF to be bound to multiple devices. The currently functionality does not allow this. If I bind an IP address to a specific device interface and then navigate to another second device interface, when I bind an IP address on that second device interface the IP address is deleted from the first device.

Use Case

For hundreds of servers running a routing daemon (e.g. FRR/quagga/bird), the same anycast address could be configured on a loopback interface. This is very common in CDN and DNS provider networks.
Similarly for anycast RP in multicast networks.

Database Changes

Perhaps. not sure.

External Dependencies

None.

@njgarfield commented on GitHub (May 8, 2019): ### Environment * Python version: 3.6 * NetBox version: 2.5.12 ### Proposed Functionality This request is to allow a single IP address in a VRF to be bound to multiple devices. The currently functionality does not allow this. If I bind an IP address to a specific device interface and then navigate to another second device interface, when I bind an IP address on that second device interface the IP address is deleted from the first device. ### Use Case For hundreds of servers running a routing daemon (e.g. FRR/quagga/bird), the same anycast address could be configured on a loopback interface. This is very common in CDN and DNS provider networks. Similarly for anycast RP in multicast networks. ### Database Changes Perhaps. not sure. ### External Dependencies None.
adam commented 2025-12-29 18:20:16 +01:00
Author
Owner
Copy Link

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

@jeremystretch template applied. Please consider re-opening issue.

@njgarfield commented on GitHub (May 8, 2019): @jeremystretch template applied. Please consider re-opening issue.
adam commented 2025-12-29 18:20:16 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 8, 2019):

@njgarfield,

I think what you want actually is "relaxed IP uniqueness enforcement with certain IP address roles".

@DanSheps commented on GitHub (May 8, 2019): @njgarfield, I think what you want actually is "relaxed IP uniqueness enforcement with certain IP address roles".
adam commented 2025-12-29 18:20:16 +01:00
Author
Owner
Copy Link

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

@DanSheps is "relaxed IP uniqueness enforcement with certain IP address roles" a current feature.

I have created a new vrf, created IP objects within that VRF, ensured ENFORCE_GLOBAL_UNIQUE is set to false.

Technically the IP address is unique in the IP address schema, but in the network graph it has multiple bindings.

@njgarfield commented on GitHub (May 8, 2019): @DanSheps is "relaxed IP uniqueness enforcement with certain IP address roles" a current feature. I have created a new vrf, created IP objects within that VRF, ensured ENFORCE_GLOBAL_UNIQUE is set to false. Technically the IP address is unique in the IP address schema, but in the network graph it has multiple bindings.
adam commented 2025-12-29 18:20:16 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 8, 2019):

No, it is not a current feature, I am suggesting this is what you want.

However, if the object is in a VRF, you need to have the VRF's enforcement of unique addresses also turned off (when you create the VRF)

@DanSheps commented on GitHub (May 8, 2019): No, it is not a current feature, I am suggesting this is what you want. However, if the object is in a VRF, you need to have the VRF's enforcement of unique addresses also turned off (when you create the VRF)
adam commented 2025-12-29 18:20:16 +01:00
Author
Owner
Copy Link

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

@DanSheps yes, Unique IP Space is not enforced on the VRF I created.

And yes, you are suggesting correctly that I believe this is effectively an enhancement request (albeit a minor one).
Thanks,
Nick

@njgarfield commented on GitHub (May 8, 2019): @DanSheps yes, Unique IP Space is not enforced on the VRF I created. And yes, you are suggesting correctly that I believe this is effectively an enhancement request (albeit a minor one). Thanks, Nick
adam commented 2025-12-29 18:20:16 +01:00
Author
Owner
Copy Link

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

This request is to allow a single IP address in a VRF to be bound to multiple devices.

Each IP address may only be bound to one interface. You'll need to create multiple IP addresses and assign each to its own interface. Note that NetBox does support creating duplicate IPs with the anycast role within a VRF, even if unique enforcement is enabled for the VRF.

If I bind an IP address to a specific device interface and then navigate to another second device interface, when I bind an IP address on that second device interface the IP address is deleted from the first device.

This does not happen. NetBox will under certain circumstances prevent the creation of a duplicate IP address, but it will not delete an existing IP address.

@jeremystretch commented on GitHub (May 8, 2019): > This request is to allow a single IP address in a VRF to be bound to multiple devices. Each IP address may only be bound to one interface. You'll need to create multiple IP addresses and assign each to its own interface. Note that NetBox does support creating duplicate IPs with the anycast role within a VRF, even if unique enforcement is enabled for the VRF. > If I bind an IP address to a specific device interface and then navigate to another second device interface, when I bind an IP address on that second device interface the IP address is deleted from the first device. This does not happen. NetBox will under certain circumstances prevent the creation of a duplicate IP address, but it will not delete an existing IP address.
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#2597
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?