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

"1000Base-TX" network interface type missing #9375

New Issue
Closed
opened 2025-12-29 20:49:07 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:49:07 +01:00
Owner
Copy Link

Originally created by @aaroneg on GitHub (Mar 20, 2024).

Originally assigned to: @Julio-Oliveira-Encora on GitHub.

Deployment Type

Self-hosted

NetBox Version

v3.7.4

Python Version

3.8

Steps to Reproduce

Edit a network interface on a device type, use the filter to type 'tx', the only type matching the filter is '100BASE-TX' which is not the same form factor.
Documentation on the 1000-BASETX form factor can be found here https://en.wikipedia.org/wiki/Gigabit_Ethernet#1000BASE-TX
It is not enough to just say to use 1000-BASET because the two have different media requirements, they are separate.

Expected Behavior

1000base-tx should appear as an option.

Observed Behavior

the option does not appear

Originally created by @aaroneg on GitHub (Mar 20, 2024). Originally assigned to: @Julio-Oliveira-Encora on GitHub. ### Deployment Type Self-hosted ### NetBox Version v3.7.4 ### Python Version 3.8 ### Steps to Reproduce Edit a network interface on a device type, use the filter to type 'tx', the only type matching the filter is '100BASE-TX' which is not the same form factor. Documentation on the 1000-BASETX form factor can be found here https://en.wikipedia.org/wiki/Gigabit_Ethernet#1000BASE-TX It is not enough to just say to use 1000-BASET because the two have different media requirements, they are separate. ### Expected Behavior 1000base-tx should appear as an option. ### Observed Behavior the option does not appear
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 20:49:07 +01:00
adam closed this issue 2025-12-29 20:49:07 +01:00
adam commented 2025-12-29 20:49:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 3, 2024):

Do you actually have 1000Base-TX equipment in use? Can you elaborate on why the 1000Base-T designation is insufficient?

@jeremystretch commented on GitHub (Apr 3, 2024): Do you actually have 1000Base-TX equipment in use? Can you elaborate on why the 1000Base-T designation is insufficient?
adam commented 2025-12-29 20:49:08 +01:00
Author
Owner
Copy Link

@aaroneg commented on GitHub (Apr 3, 2024):

Yes, and the media requirements are different as I noted when opening the
issue.

On Wed, Apr 3, 2024 at 8:18 AM Jeremy Stretch @.***>
wrote:

Do you actually have 1000Base-TX equipment in use? Can you elaborate on
why the 1000Base-T designation is insufficient?

—
Reply to this email directly, view it on GitHub
https://github.com/netbox-community/netbox/issues/15489#issuecomment-2034588559,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKU7P6LIVWD7HX42JBQMBLY3P6QHAVCNFSM6AAAAABE7VON2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZUGU4DQNJVHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@aaroneg commented on GitHub (Apr 3, 2024): Yes, and the media requirements are different as I noted when opening the issue. On Wed, Apr 3, 2024 at 8:18 AM Jeremy Stretch ***@***.***> wrote: > Do you actually have 1000Base-TX equipment in use? Can you elaborate on > why the 1000Base-T designation is insufficient? > > — > Reply to this email directly, view it on GitHub > <https://github.com/netbox-community/netbox/issues/15489#issuecomment-2034588559>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKU7P6LIVWD7HX42JBQMBLY3P6QHAVCNFSM6AAAAABE7VON2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZUGU4DQNJVHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
adam commented 2025-12-29 20:49:08 +01:00
Author
Owner
Copy Link

@Julio-Oliveira-Encora commented on GitHub (May 27, 2024):

Could you please assign it to me?

@Julio-Oliveira-Encora commented on GitHub (May 27, 2024): Could you please assign it to me?
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 complexity: low status: accepted 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#9375
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?