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 console connection settings field (baud rate) #3197

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

Originally created by @alexjhart on GitHub (Jan 21, 2020).

Please add the ability to track baud rate of the console port on a device. From connecting adhoc to configuring a console server, this information saves time when connecting. Since the defaults vary, and can often be changed, it's important to track this information somewhere, why not where you already have the port and type defined in Netbox? While other settings could also be tracked, this is the most common to vary between devices, so it's an easy place to start. While you could go with a common list (such as https://en.wikipedia.org/wiki/Serial_port#Speed), this could just be an integer field rather than a selection. It could also just be a generic serial connection settings text field.

Originally created by @alexjhart on GitHub (Jan 21, 2020). Please add the ability to track baud rate of the console port on a device. From connecting adhoc to configuring a console server, this information saves time when connecting. Since the defaults vary, and can often be changed, it's important to track this information somewhere, why not where you already have the port and type defined in Netbox? While other settings could also be tracked, this is the most common to vary between devices, so it's an easy place to start. While you could go with a common list (such as https://en.wikipedia.org/wiki/Serial_port#Speed), this could just be an integer field rather than a selection. It could also just be a generic serial connection settings text field.
adam closed this issue 2025-12-29 18:26:33 +01:00
adam commented 2025-12-29 18:26:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 21, 2020):

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 (Jan 21, 2020): This issue has been closed as it does not conform to one of the [provided templates](https://github.com/netbox-community/netbox/issues/new/choose) as required by the [contributing guide](https://github.com/netbox-community/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).
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#3197
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?