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

Extra info in Prefix information screen #5116

New Issue
Closed
opened 2025-12-29 19:24:27 +01:00 by adam · 7 comments
adam commented 2025-12-29 19:24:27 +01:00
Owner
Copy Link

Originally created by @chesronw on GitHub (Jul 29, 2021).

NetBox version

v2.11.9

Feature type

Change to existing functionality

Proposed functionality

Hi,

Is it possible to define in the prefix information screen also some extra information about that prefix for how to use?
It would be great to define also the default gateway, DNS and NTP information.

DNS and NTP info could be in a custom field of course.
But the gateway you want to specify this from the IP address. So also that IP is also marked as the default gateway.

A good example is that in PHPIpam (Yes Netbox is better)
At a IP address you have a YES/NEW button for the gateway.

image

After setting the gateway it is also in de subnet visible in the subnet details

image

Use case

The use case in this is that other departments like system administrators also know what the gateway other needed information is about a subnet.

Database changes

No response

External dependencies

No response

Originally created by @chesronw on GitHub (Jul 29, 2021). ### NetBox version v2.11.9 ### Feature type Change to existing functionality ### Proposed functionality Hi, Is it possible to define in the prefix information screen also some extra information about that prefix for how to use? It would be great to define also the default gateway, DNS and NTP information. DNS and NTP info could be in a custom field of course. But the gateway you want to specify this from the IP address. So also that IP is also marked as the default gateway. A good example is that in PHPIpam (Yes Netbox is better) At a IP address you have a YES/NEW button for the gateway. ![image](https://user-images.githubusercontent.com/85490348/127472001-ce59e34a-8418-4116-9e03-d64fe43592cf.png) After setting the gateway it is also in de subnet visible in the subnet details ![image](https://user-images.githubusercontent.com/85490348/127471666-a50c211a-836b-4b73-8f7e-a5736c12ed0b.png) ### Use case The use case in this is that other departments like system administrators also know what the gateway other needed information is about a subnet. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:24:27 +01:00
adam closed this issue 2025-12-29 19:24:27 +01:00
adam commented 2025-12-29 19:24:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2021):

NetBox doesn't have built-in fields for these on the prefix model because it doesn't always make sense to do so. However, if it makes sense for your particular use case, you have the option of adding custom fields to the prefix model to track these values.

@jeremystretch commented on GitHub (Jul 29, 2021): NetBox doesn't have built-in fields for these on the prefix model because it doesn't always make sense to do so. However, if it makes sense for your particular use case, you have the option of adding [custom fields](https://netbox.readthedocs.io/en/stable/additional-features/custom-fields/) to the prefix model to track these values.
adam commented 2025-12-29 19:24:28 +01:00
Author
Owner
Copy Link

@chesronw commented on GitHub (Jul 29, 2021):

Hi Jeremy,

Thanks for your update!
I agree that is not always make sense.

But a custom field is possible but you need to double the administration also in the IP address tab

Is it possible to make this as a optional option to mark it as the gateway?
Where in the prefix screen you can see the IP that is marked as gateway?

@chesronw commented on GitHub (Jul 29, 2021): Hi Jeremy, Thanks for your update! I agree that is not always make sense. But a custom field is possible but you need to double the administration also in the IP address tab Is it possible to make this as a optional option to mark it as the gateway? Where in the prefix screen you can see the IP that is marked as gateway?
adam commented 2025-12-29 19:24:28 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 29, 2021):

That specific requirement could also be baked in as a netbox plugin @chesronw . Have you looked into these ?

@jsenecal commented on GitHub (Jul 29, 2021): That specific requirement could also be baked in as a netbox plugin @chesronw . Have you looked into these ?
adam commented 2025-12-29 19:24:28 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 30, 2021):

I agree with everything here, I don't see this being implemented in core.

This has also been brought up in the following:

#3109
#2953
#1610

@DanSheps commented on GitHub (Jul 30, 2021): I agree with everything here, I don't see this being implemented in core. This has also been brought up in the following: #3109 #2953 #1610
adam commented 2025-12-29 19:24:28 +01:00
Author
Owner
Copy Link

@julianze commented on GitHub (Jul 30, 2021):

DNS and NTP information is best documentated with config contexts. Config contexts aren't linkable to prefix, but for sites or other models.
I think many prefix will have same DNS and NTP informations, so config contexts are the right place. You can see at every device the rendered configs. So the sysadmin (happy sysadmin day 😄 ) will see the right configs for a particular host.

Default gateway:
The latest discussion about this is in the discussions section. I have made there a proposal which should address all requirements and concerns of both sides (user + maintainer):
https://github.com/netbox-community/netbox/discussions/6030#discussioncomment-591688

Maybe we can discuss further this in the discussion section?

@julianze commented on GitHub (Jul 30, 2021): DNS and NTP information is best documentated with config contexts. Config contexts aren't linkable to prefix, but for sites or other models. I think many prefix will have same DNS and NTP informations, so config contexts are the right place. You can see at every device the rendered configs. So the sysadmin (happy sysadmin day 😄 ) will see the right configs for a particular host. Default gateway: The latest discussion about this is in the discussions section. I have made there a proposal which should address all requirements and concerns of both sides (user + maintainer): https://github.com/netbox-community/netbox/discussions/6030#discussioncomment-591688 Maybe we can discuss further this in the discussion section?
adam commented 2025-12-29 19:24:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 29, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 29, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:24:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2021):

I'm going to close this out as the consensus seems to be that it doesn't make sense to pursue at this time.

@jeremystretch commented on GitHub (Oct 5, 2021): I'm going to close this out as the consensus seems to be that it doesn't make sense to pursue at this time.
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#5116
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?