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

Add the possibility to create new IP roles #1179

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

Originally created by @tdmike on GitHub (Aug 17, 2017).

As the titel says, would it be possible to create custom roles for IP addresses. Currently it's only available for VLANs.

Originally created by @tdmike on GitHub (Aug 17, 2017). As the titel says, would it be possible to create custom roles for IP addresses. Currently it's only available for VLANs.
adam closed this issue 2025-12-29 16:29:46 +01:00
adam commented 2025-12-29 16:29:46 +01:00
Author
Owner
Copy Link

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

IP address roles describe the type of IP address, not its function. There are a limited number of practically relevant roles (loopback, anycast, VRRP, etc.), which is why they are statically defined. What role(s) are you proposing be added?

@jeremystretch commented on GitHub (Aug 17, 2017): IP address roles describe the type of IP address, not its function. There are a limited number of practically relevant roles (loopback, anycast, VRRP, etc.), which is why they are statically defined. What role(s) are you proposing be added?
adam commented 2025-12-29 16:29:47 +01:00
Author
Owner
Copy Link

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

I'd have to agree that customizable roles would be very nice.

There are many good roles of an IP:
1 - BGP peering
2 - Failover
3 - Heartbeat
4 - Replication
5 - etc

The role of the IP, to me, is the purpose/reason that the IP exists.

@kopacko commented on GitHub (Aug 17, 2017): I'd have to agree that customizable roles would be very nice. There are many good roles of an IP: 1 - BGP peering 2 - Failover 3 - Heartbeat 4 - Replication 5 - etc The role of the IP, to me, is the purpose/reason that the IP exists.
adam commented 2025-12-29 16:29:47 +01:00
Author
Owner
Copy Link

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

@kopacko You are confusing applications with the manner in which an IP address is assigned. For instance, BGP peering can be done on regular unicast IPs or on loopback IPs.

@jeremystretch commented on GitHub (Aug 17, 2017): @kopacko You are confusing applications with the manner in which an IP address is assigned. For instance, BGP peering can be done on regular unicast IPs or on loopback IPs.
adam commented 2025-12-29 16:29:47 +01:00
Author
Owner
Copy Link

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

That may be the case, but for those who do not understand unicast, multicast, etc (e.g. the local techs in each of my locations) will not.

Assigning a role that non-technical to understand makes it easier for them.

@kopacko commented on GitHub (Aug 17, 2017): That may be the case, but for those who do not understand unicast, multicast, etc (e.g. the local techs in each of my locations) will not. Assigning a role that non-technical to understand makes it easier for them.
adam commented 2025-12-29 16:29:47 +01:00
Author
Owner
Copy Link

@tdmike commented on GitHub (Aug 17, 2017):

Well I mainly request it since I can not clearly specify which IP is the gateway.

@tdmike commented on GitHub (Aug 17, 2017): Well I mainly request it since I can not clearly specify which IP is the gateway.
adam commented 2025-12-29 16:29:47 +01:00
Author
Owner
Copy Link

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

Perhaps it would help to explain the existing IP roles:

  • Default (none): A normal IP, optionally assigned to an interface
  • Loopback: An IP assigned to a loopback interface
  • Secondary: An IP assigned to an interface as a secondary IP (i.e. ip address x.x.x.x secondary in Cisco IOS)
  • Anycast: An IP that has other instances assigned elsewhere (an intentionally duplicate IP)
  • VIP: A floating IP address
  • VRRP/HSRP/GLBP: A VIP managed by one of the respective NHRP protocols

@tdmike The qualification of an IP as the default gateway for a prefix is a related but different matter. Any of the above (with the exception of loopback) could be the default gateway for a prefix. There are other attributes you can use in determining the gateway IP. For example, whether it's the first or last usable IP in the prefix, whether it's assigned to an interface on a router, etc.

@jeremystretch commented on GitHub (Aug 17, 2017): Perhaps it would help to explain the existing IP roles: * Default (none): A normal IP, optionally assigned to an interface * Loopback: An IP assigned to a loopback interface * Secondary: An IP assigned to an interface as a secondary IP (i.e. `ip address x.x.x.x secondary` in Cisco IOS) * Anycast: An IP that has other instances assigned elsewhere (an intentionally duplicate IP) * VIP: A floating IP address * VRRP/HSRP/GLBP: A VIP managed by one of the respective NHRP protocols @tdmike The qualification of an IP as the default gateway for a prefix is a related but different matter. Any of the above (with the exception of loopback) could be the default gateway for a prefix. There are other attributes you can use in determining the gateway IP. For example, whether it's the first or last usable IP in the prefix, whether it's assigned to an interface on a router, etc.
adam commented 2025-12-29 16:29:48 +01:00
Author
Owner
Copy Link

@sulisu commented on GitHub (Nov 24, 2019):

@jeremystretch Please put this definition of ip address roles into document. Someone using Fortigate firewall might think VIP as different meaning.

@sulisu commented on GitHub (Nov 24, 2019): @jeremystretch Please put this definition of ip address roles into document. Someone using Fortigate firewall might think VIP as different meaning.
adam commented 2025-12-29 16:29:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 25, 2019):

@sulisu Feel free to submit an issue for it if you'd like to contribute a PR.

@jeremystretch commented on GitHub (Nov 25, 2019): @sulisu Feel free to submit an issue for it if you'd like to contribute a PR.
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#1179
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?