starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Interface cannot connect to Rear Port #4280

New Issue
Closed
opened 2025-12-29 18:34:23 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:34:23 +01:00
Owner
Copy Link

Originally created by @jameswhite4684 on GitHub (Nov 16, 2020).

Environment
Python version: 3.8.5
NetBox version: 2.9.7

Steps to Reproduce
Create or locate one device with at least one non-connected interface.
Create a device with two front ports mapped to a single rear port.
Connect interface to the rear port.

Expected Behavior
Interface connect to single rear port

Observed Behavior
Errors
Rear ports with multiple positions may only be connected to other pass-through ports

Originally created by @jameswhite4684 on GitHub (Nov 16, 2020). Environment Python version: 3.8.5 NetBox version: 2.9.7 Steps to Reproduce Create or locate one device with at least one non-connected interface. Create a device with two front ports mapped to a single rear port. Connect interface to the rear port. Expected Behavior Interface connect to single rear port Observed Behavior Errors Rear ports with multiple positions may only be connected to other pass-through ports
adam closed this issue 2025-12-29 18:34:23 +01:00
adam commented 2025-12-29 18:34:24 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 17, 2020):

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@DanSheps commented on GitHub (Nov 17, 2020): Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the [feature request template](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.
adam commented 2025-12-29 18:34:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 17, 2020):

This is indeed expected behavior in v2.9. However, the cabling model has been reworked in the upcoming v2.10 release and this will no longer be a constraint.

@jeremystretch commented on GitHub (Nov 17, 2020): This is indeed expected behavior in v2.9. However, the cabling model has been reworked in the upcoming v2.10 release and this will no longer be a constraint.
adam commented 2025-12-29 18:34:24 +01:00
Author
Owner
Copy Link

@jameswhite4684 commented on GitHub (Nov 17, 2020):

Thank you, I know it was possible before 2.9 so I just wasn't sure as I have other cables set that way prior to upgrading to 2.9.

@jameswhite4684 commented on GitHub (Nov 17, 2020): Thank you, I know it was possible before 2.9 so I just wasn't sure as I have other cables set that way prior to upgrading to 2.9.
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#4280
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?