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

IP Roles #2550

New Issue
Closed
opened 2025-12-29 18:19:52 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:19:52 +01:00
Owner
Copy Link

Originally created by @alexey-kirillov on GitHub (Apr 25, 2019).

Issue type

[x ] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.6
  • NetBox version: 2.5.10

Proposed Functionality

First of all, thanks for Netbox.
I know there is a number of relevant issues, but let's try one more time :)

  1. Router
    It's not uncommon to have a single gateway on a subnet, which is a default gw for devices, why should we avoid documenting this? Let's call it a "router" role which means this IP can route ip packets to other networks. This would be an attribute of this IP (ability to route), not devices, which use this IP as a gateway.
    In case you have multiple routers, it's up to you to mark them all.

  2. Custom Role
    There are cases when you want to highlight another role, such as DNS,DHCP. Someone will require another set of roles. Why don't you implement configurable list of roles? This is done for prefixes,vlans,racks,devices, but not for IPs.

  3. Ok, we can use tags, but:
    a) some are not relevant for IPs (list of tags can be reduced by using IP roles instead)
    b) tags are not shown in IP list, which makes them hardly usable

  4. And there's no comment field for all IPAM items :(

Thank you.

Originally created by @alexey-kirillov on GitHub (Apr 25, 2019). ### Issue type [x ] Feature request [ ] Bug report [ ] Documentation ### Environment * Python version: 3.6 * NetBox version: 2.5.10 ### Proposed Functionality First of all, thanks for Netbox. I know there is a number of relevant issues, but let's try one more time :) 1. Router It's not uncommon to have a single gateway on a subnet, which is a default gw for devices, why should we avoid documenting this? Let's call it a "router" role which means this IP can route ip packets to other networks. This would be an attribute of this IP (ability to route), not devices, which use this IP as a gateway. In case you have multiple routers, it's up to you to mark them all. 2. Custom Role There are cases when you want to highlight another role, such as DNS,DHCP. Someone will require another set of roles. Why don't you implement configurable list of roles? This is done for prefixes,vlans,racks,devices, but not for IPs. 3. Ok, we can use tags, but: a) some are not relevant for IPs (list of tags can be reduced by using IP roles instead) b) tags are not shown in IP list, which makes them hardly usable 4. And there's no comment field for all IPAM items :( Thank you.
adam closed this issue 2025-12-29 18:19:52 +01:00
adam commented 2025-12-29 18:19:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 25, 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 (Apr 25, 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:19:53 +01:00
Author
Owner
Copy Link

@alexey-kirillov commented on GitHub (Apr 25, 2019):

fixed, please re-open

@alexey-kirillov commented on GitHub (Apr 25, 2019): fixed, please re-open
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#2550
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?