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 #2648

New Issue
Closed
opened 2025-12-29 18:20:49 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:20:49 +01:00
Owner
Copy Link

Originally created by @alexey-kirillov on GitHub (Jun 4, 2019).

Environment

  • NetBox version: 2.5.13

Proposed Functionality

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

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.

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.

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

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

Thank you.

ps: duplicate of #3109, but verified on newer netbox version.

Use Case

Use case: you've allocated a prefix for remote office, prepared a router/switch/dns configuration and remote office admin needs all related info on a single page. You could share a link to netbox/ipam/prefixes/NN/ip-addresses as a documentation.

Database Changes

required

External Dependencies

none

Originally created by @alexey-kirillov on GitHub (Jun 4, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * NetBox version: 2.5.13 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality First of all, thanks for NetBox. I know there is a number of relevant issues, but let's try one more time :) 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. 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. 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 And there's no comment field for all IPAM items :( Thank you. ps: duplicate of #3109, but verified on newer netbox version. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Use case: you've allocated a prefix for remote office, prepared a router/switch/dns configuration and remote office admin needs all related info on a single page. You could share a link to netbox/ipam/prefixes/NN/ip-addresses as a documentation. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes required <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies none
adam added the status: duplicate label 2025-12-29 18:20:49 +01:00
adam closed this issue 2025-12-29 18:20:49 +01:00
adam commented 2025-12-29 18:20:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 4, 2019):

Both of these topics have already been proposed and rejected.

Router

Please see my comments on #2953

Custom Role

Addressed in #2163

@jeremystretch commented on GitHub (Jun 4, 2019): Both of these topics have already been proposed and rejected. > Router Please see my comments on #2953 > Custom Role Addressed in #2163
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 status: duplicate
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#2648
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?