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

2.5-beta1: passthrough port component #2137

New Issue
Closed
opened 2025-12-29 17:22:37 +01:00 by adam · 4 comments
adam commented 2025-12-29 17:22:37 +01:00
Owner
Copy Link

Originally created by @LukeLR on GitHub (Nov 21, 2018).

Environment

  • Python version: unknown
  • NetBox version: 2.5-beta1

Steps to Reproduce

The changelog of the 2.5-beta1 release says:

NetBox now supports modeling physical cables for console, power, and interface connections. The new pass-through port component type has also been introduced to model patch panels and similar devices.

But I can't find anything related to passthrough port components when adding a new device type, neither in front/rear ports, interfaces or anywhere else. Am I missing something?

Expected Behavior

Pass-through port components are visible as a port type when adding front or rear ports.

Observed Behavior

No pass-through port components can be selected when adding new ports.

Originally created by @LukeLR on GitHub (Nov 21, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss 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 * Python version: unknown * NetBox version: 2.5-beta1 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce The changelog of the 2.5-beta1 release says: > NetBox now supports modeling physical cables for console, power, and interface connections. The new pass-through port component type has also been introduced to model patch panels and similar devices. But I can't find anything related to passthrough port components when adding a new device type, neither in front/rear ports, interfaces or anywhere else. Am I missing something? <!-- What did you expect to happen? --> ### Expected Behavior Pass-through port components are visible as a port type when adding front or rear ports. <!-- What happened instead? --> ### Observed Behavior No pass-through port components can be selected when adding new ports.
adam closed this issue 2025-12-29 17:22:37 +01:00
adam commented 2025-12-29 17:22:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 21, 2018):

Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using the template provided here. For general discussion, questions, or assistance with installation issues, please post to our mailing list.

@jeremystretch commented on GitHub (Nov 21, 2018): Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using the template provided [here](https://raw.githubusercontent.com/digitalocean/netbox/develop/.github/ISSUE_TEMPLATE.md). For general discussion, questions, or assistance with installation issues, please post to our [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss).
adam commented 2025-12-29 17:22:38 +01:00
Author
Owner
Copy Link

@LukeLR commented on GitHub (Nov 21, 2018):

Besides having used the template, using the mailing list is not possible for people without a Google account. But thanks, anyways.

@LukeLR commented on GitHub (Nov 21, 2018): Besides having used the template, using the mailing list is not possible for people without a Google account. But thanks, anyways.
adam commented 2025-12-29 17:22:38 +01:00
Author
Owner
Copy Link

@LBegnaud commented on GitHub (Nov 21, 2018):

it is free to create a google account. You also need an account to post this issue here... so I'm not sure what your point is.

@LBegnaud commented on GitHub (Nov 21, 2018): it is free to create a google account. You also need an account to post this issue here... so I'm not sure what your point is.
adam commented 2025-12-29 17:22:38 +01:00
Author
Owner
Copy Link

@LukeLR commented on GitHub (Nov 22, 2018):

Not everyone is comfortable with Google collecting their data. Not everyone would even agree if Google accounts are free or paid by your data... But my question was solved, thanks.

@LukeLR commented on GitHub (Nov 22, 2018): Not everyone is comfortable with Google collecting their data. Not everyone would even agree if Google accounts are free or paid by your data... But my question was solved, thanks.
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#2137
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?