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 ip address to be assigned to multiple devices #1153

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

Originally created by @Atoms on GitHub (Aug 8, 2017).

Feature Request

When UNIQ ip addresses is enabled there is no possibility to add one ip address to multiple devices (with disabled uniq you can add 2 times one address with different device), when ip address role is VIP/Anycast/VRRP/HSRP/GLBP

When i find ip address and it's role is one of those mentioned, i want to see devices it can float around.

Originally created by @Atoms on GitHub (Aug 8, 2017). Feature Request When UNIQ ip addresses is enabled there is no possibility to add one ip address to multiple devices (with disabled uniq you can add 2 times one address with different device), when ip address role is VIP/Anycast/VRRP/HSRP/GLBP When i find ip address and it's role is one of those mentioned, i want to see devices it can float around.
adam closed this issue 2025-12-29 16:29:32 +01:00
adam commented 2025-12-29 16:29:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 8, 2017):

How are you proposing we alter the data model?

@jeremystretch commented on GitHub (Aug 8, 2017): How are you proposing we alter the data model?
adam commented 2025-12-29 16:29:33 +01:00
Author
Owner
Copy Link

@Atoms commented on GitHub (Aug 8, 2017):

We talked about this with college and got to point that we don't know the right solution, but one can be:
introduce table ip_addresses_interface as one to many relation (one ip address can be assigned to multiple interfaces) and use in case role is one of those which will have this feature..

I don't know how easy or hard implementation and validation of this could be.

In Frontend for ip address which is for this role can be some link to assign more devices to this ip or something like that.

@Atoms commented on GitHub (Aug 8, 2017): We talked about this with college and got to point that we don't know the right solution, but one can be: introduce table ip_addresses_interface as one to many relation (one ip address can be assigned to multiple interfaces) and use in case role is one of those which will have this feature.. I don't know how easy or hard implementation and validation of this could be. In Frontend for ip address which is for this role can be some link to assign more devices to this ip or something like that.
adam commented 2025-12-29 16:29:33 +01:00
Author
Owner
Copy Link

@kopacko commented on GitHub (Aug 12, 2017):

Since I am no programmer, from what I can tell is...the IP address is assigned to an interface. If you coded it such that an object (the IP address in this case) can have multiple assigned interfaces, that would allow for VIPs, HSRPs, etc to more easily assigned across multiple physical devices.

@kopacko commented on GitHub (Aug 12, 2017): Since I am no programmer, from what I can tell is...the IP address is assigned to an interface. If you coded it such that an object (the IP address in this case) can have multiple assigned interfaces, that would allow for VIPs, HSRPs, etc to more easily assigned across multiple physical devices.
adam commented 2025-12-29 16:29:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 15, 2017):

The assignment of VIPs to interfaces isn't as simple as modifying the relationship. VIP assignment typically encompasses additional data as well (e.g. VRRP group and priority). I want to keep the direct relationship of IP address to interface. The representation of VIP associations is probably better achieved by introducing a new VIPAssignment model to accommodate the additional data.

@jeremystretch commented on GitHub (Aug 15, 2017): The assignment of VIPs to interfaces isn't as simple as modifying the relationship. VIP assignment typically encompasses additional data as well (e.g. VRRP group and priority). I want to keep the direct relationship of IP address to interface. The representation of VIP associations is probably better achieved by introducing a new `VIPAssignment` model to accommodate the additional data.
adam commented 2025-12-29 16:29:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 25, 2017):

The issue of VIP group tracking can be addressed at a later time. We're going to keep the direct assignment of other IPs to interfaces.

@jeremystretch commented on GitHub (Aug 25, 2017): The issue of VIP group tracking can be addressed at a later time. We're going to keep the direct assignment of other IPs to interfaces.
adam commented 2025-12-29 16:29:33 +01:00
Author
Owner
Copy Link

@Phhere commented on GitHub (Dec 27, 2018):

Any update on this ?

@Phhere commented on GitHub (Dec 27, 2018): Any update on this ?
adam commented 2025-12-29 16:29:33 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 30, 2018):

@Phhere It was closed with a reasoning. I am not sure what kind of update you want.

@DanSheps commented on GitHub (Dec 30, 2018): @Phhere It was closed with a reasoning. I am not sure what kind of update you want.
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#1153
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?