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 IP Address Roles #641

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

Originally created by @Armadill0 on GitHub (Jan 20, 2017).

We're currently investigating how to mark IP addresses for a specific role, for instance as a gateway. Currently this is only possible via the address description if you want to see the gateway "role" e.g. on the list of ip addresses on the Prefix page.
It's also not possible to filter for a Prefix on the IP address list and combine it with a search in the address description which makes it even harder to find a specific gateway.

The best solution for this in my opinion would be an IP address role field, like we already have it e.g. for devices. This would allow us to mark IP addresses for special use cases like gateways, VRRP, Cluster-IPs, Loopback addresses and so on and to easily find them through filters.
Also the possibility to mark them with a specific color which is also possible for device roles would be great to easily find a gateway in the IP address list of a single Prefix.

What do you think?

Originally created by @Armadill0 on GitHub (Jan 20, 2017). We're currently investigating how to mark IP addresses for a specific role, for instance as a gateway. Currently this is only possible via the address description if you want to see the gateway "role" e.g. on the list of ip addresses on the Prefix page. It's also not possible to filter for a Prefix on the IP address list and combine it with a search in the address description which makes it even harder to find a specific gateway. The best solution for this in my opinion would be an IP address role field, like we already have it e.g. for devices. This would allow us to mark IP addresses for special use cases like gateways, VRRP, Cluster-IPs, Loopback addresses and so on and to easily find them through filters. Also the possibility to mark them with a specific color which is also possible for device roles would be great to easily find a gateway in the IP address list of a single Prefix. What do you think?
adam closed this issue 2025-12-29 16:24:11 +01:00
adam commented 2025-12-29 16:24:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 20, 2017):

I think it might make sense to include some hard-coded operational roles for IP addresses:

  • Default gateway
  • NHRP client (VRRP/HSRP/GLBP/etc.)
  • Virtual IP (generic clustering)

I'm not sure if a loopback role would be appropriate, since that's more a function of the interface to which an IP address is assigned.

@jeremystretch commented on GitHub (Jan 20, 2017): I think it might make sense to include some hard-coded operational roles for IP addresses: * Default gateway * NHRP client (VRRP/HSRP/GLBP/etc.) * Virtual IP (generic clustering) I'm not sure if a loopback role would be appropriate, since that's more a function of the interface to which an IP address is assigned.
adam commented 2025-12-29 16:24:12 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Jan 23, 2017):

Aside: there is already a Prefix role, and VLAN roles re-use Prefix roles.

So they could be shared with IP Address too, although in practice roles like 'default gateway' wouldn't make any sense at the Prefix/VLAN level.

@candlerb commented on GitHub (Jan 23, 2017): Aside: there is already a Prefix role, and VLAN roles re-use Prefix roles. So they could be shared with IP Address too, although in practice roles like 'default gateway' wouldn't make any sense at the Prefix/VLAN level.
adam commented 2025-12-29 16:24:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 23, 2017):

@candlerb Right, the prefix/VLAN roles are user-customizable and functional in nature, whereas IP address roles would pertain to the status of an IP relative to other IPs within its parent prefix.

@jeremystretch commented on GitHub (Jan 23, 2017): @candlerb Right, the prefix/VLAN roles are user-customizable and functional in nature, whereas IP address roles would pertain to the status of an IP relative to other IPs within its parent prefix.
adam commented 2025-12-29 16:24:12 +01:00
Author
Owner
Copy Link

@Armadill0 commented on GitHub (Jan 30, 2017):

To be honest, using prefix/vlan roles also for IP addresses, would be fine for us. This would also make the implementation much less work I assume.

To emphasize the more generic usage within the IPAM functionalities, we could rename them to "IPAM roles" or something similar instead of "Prefix/VLAN roles".

And I would really appreciate the color selection which we already have for device roles.

@Armadill0 commented on GitHub (Jan 30, 2017): To be honest, using prefix/vlan roles also for IP addresses, would be fine for us. This would also make the implementation much less work I assume. To emphasize the more generic usage within the IPAM functionalities, we could rename them to "IPAM roles" or something similar instead of "Prefix/VLAN roles". And I would really appreciate the color selection which we already have for device roles.
adam commented 2025-12-29 16:24:12 +01:00
Author
Owner
Copy Link

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

As mentioned in #906, it might make sense to include an "anycast" role for IP addresses. This role could be used to exempt anycast IPs from duplicate address validation.

@jeremystretch commented on GitHub (Feb 23, 2017): As mentioned in #906, it might make sense to include an "anycast" role for IP addresses. This role could be used to exempt anycast IPs from duplicate address validation.
adam commented 2025-12-29 16:24:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 14, 2017):

Implemented in f427c00d94

@jeremystretch commented on GitHub (Jun 14, 2017): Implemented in f427c00d946a6253ce7b4fe9997d8dfc4c05d664
adam commented 2025-12-29 16:24:13 +01:00
Author
Owner
Copy Link

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

Please add also CARP as an role option

@tioan commented on GitHub (Aug 15, 2017): Please add also CARP as an role option
adam commented 2025-12-29 16:24:13 +01:00
Author
Owner
Copy Link

@porkstoners commented on GitHub (Feb 12, 2019):

Would it be possible to add VARP as a role ?

@porkstoners commented on GitHub (Feb 12, 2019): Would it be possible to add VARP as a role ?
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#641
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?