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

Different types of ports are connected #6044

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

Originally created by @KosenkoIvan on GitHub (Feb 3, 2022).

NetBox version

nexbox (v3.1.5)

Python version

3.7

Steps to Reproduce

When we add switching, we can connect ports of different types, since it selects only by name.
8
9

Expected Behavior

Ports of different types should not be connected.

Observed Behavior

Connected 1G and 40G ports

Originally created by @KosenkoIvan on GitHub (Feb 3, 2022). ### NetBox version nexbox (v3.1.5) ### Python version 3.7 ### Steps to Reproduce When we add switching, we can connect ports of different types, since it selects only by name. ![8](https://user-images.githubusercontent.com/97949308/152321232-c6bf0547-c347-4566-875b-ff9377ffd545.PNG) ![9](https://user-images.githubusercontent.com/97949308/152321236-c7e0cfd7-f487-48b3-a9dc-543af3e0f88f.PNG) ### Expected Behavior Ports of different types should not be connected. ### Observed Behavior Connected 1G and 40G ports
adam closed this issue 2025-12-29 19:36:00 +01:00
adam commented 2025-12-29 19:36:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 3, 2022):

NetBox does not claim to validate whether two types of connected interfaces will function, and the effort required to compile a set of rules dictating which interface types can interoperate would likely be disproportionate to the value it provides. Still, if you'd like to propose a specific implementation for such a feature, you're welcome to submit a feature request.

@jeremystretch commented on GitHub (Feb 3, 2022): NetBox does not claim to validate whether two types of connected interfaces will function, and the effort required to compile a set of rules dictating which interface types can interoperate would likely be disproportionate to the value it provides. Still, if you'd like to propose a _specific implementation_ for such a feature, you're welcome to submit a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&template=feature_request.yaml).
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#6044
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?