starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add SNIP and Other IP Address Roles #8340

New Issue
Closed
opened 2025-12-29 20:35:31 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:35:31 +01:00
Owner
Copy Link

Originally created by @etherwrangler on GitHub (Jul 16, 2023).

NetBox version

v3.5.6

Feature type

Data model extension

Proposed functionality

Add "SNIP" and "Other" to the ipam.IPAddress.role field or make this field support custom FIELD_CHOICES.

Use case

Citrix NetScalers have an IP type called a SNIP (Subnet IP) that would be useful to track as separate from a VIP when added to an FHRP Group.

Database changes

None.

External dependencies

None.

Originally created by @etherwrangler on GitHub (Jul 16, 2023). ### NetBox version v3.5.6 ### Feature type Data model extension ### Proposed functionality Add "SNIP" and "Other" to the ipam.IPAddress.role field or make this field support custom FIELD_CHOICES. ### Use case Citrix NetScalers have an IP type called a SNIP (Subnet IP) that would be useful to track as separate from a VIP when added to an FHRP Group. ### Database changes None. ### External dependencies None.
adam added the type: feature label 2025-12-29 20:35:31 +01:00
adam closed this issue 2025-12-29 20:35:31 +01:00
adam commented 2025-12-29 20:35:32 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 18, 2023):

I am not in favor to add proprietary protocols to that list, but would be in favor to support FIELD_CHOICES for this field.

@jsenecal commented on GitHub (Jul 18, 2023): I am not in favor to add proprietary protocols to that list, but would be in favor to support `FIELD_CHOICES` for this field.
adam commented 2025-12-29 20:35:32 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Jul 19, 2023):

if we were to enable FIELD_CHOICES for that list we would want to make sure that we have a way to mark wether choices are anycast or not (aka allowing duplicate ips) right now there are hard coded checks for some of the choices to ignore duplicate IP logic in vrf's

@ITJamie commented on GitHub (Jul 19, 2023): if we were to enable FIELD_CHOICES for that list we would want to make sure that we have a way to mark wether choices are anycast or not (aka allowing duplicate ips) right now there are hard coded checks for some of the choices to ignore duplicate IP logic in vrf's
adam commented 2025-12-29 20:35:32 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 19, 2023):

I have used Citrix Netscaler and SNIP is just a VIP, there isn't any special protocol with the IP itself, it is all handled as part of the Netscaler clustering protocol.

IMO, not in favor of this and really utlimately not in favor of even opening IP roles to FIELD_CHOICES.

@DanSheps commented on GitHub (Jul 19, 2023): I have used Citrix Netscaler and SNIP is just a VIP, there isn't any special protocol with the IP itself, it is all handled as part of the Netscaler clustering protocol. IMO, not in favor of this and really utlimately not in favor of even opening IP roles to FIELD_CHOICES.
adam commented 2025-12-29 20:35:32 +01:00
Author
Owner
Copy Link

@etherwrangler commented on GitHub (Jul 24, 2023):

Going to close this request. We'll use tag's instead of this. When the request was made was not aware that this field has logic built in based on some choices as @ITJamie mentioned. Given that I feel it would be overburdening to request this be implemented.

@etherwrangler commented on GitHub (Jul 24, 2023): Going to close this request. We'll use tag's instead of this. When the request was made was not aware that this field has logic built in based on some choices as @ITJamie mentioned. Given that I feel it would be overburdening to request this be implemented.
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 type: feature
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#8340
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?