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

Front Port - Rear Port Table View "Device A" and "Decive B" #9280

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

Originally created by @LHBL2003 on GitHub (Feb 23, 2024).

NetBox version

v3.7.1

Feature type

Change to existing functionality

Proposed functionality

Add "Device Connection A" and "Device Connection B" to the Front Ports / Rear Ports table to see what is at the end of the line.
This function already exists for interfaces, so I hope that it is easy to extend.

image

image

Use case

We have illustrated network sockets and patch panels in Netbox. Not all network sockets are connected to a switch. Using the trace view, you can see which connection a device is connected to at the end of the route. Unfortunately, you first have to click on all the trace buttons to find an existing connection. It is quicker if you can see the start and end devices in the table.

Database changes

No response

External dependencies

No response

Originally created by @LHBL2003 on GitHub (Feb 23, 2024). ### NetBox version v3.7.1 ### Feature type Change to existing functionality ### Proposed functionality Add "Device Connection A" and "Device Connection B" to the Front Ports / Rear Ports table to see what is at the end of the line. This function already exists for interfaces, so I hope that it is easy to extend. ![image](https://github.com/netbox-community/netbox/assets/46369917/8c9bb045-5a8d-4ba2-9904-8fa17f75155f) ![image](https://github.com/netbox-community/netbox/assets/46369917/19d4809c-7c54-469a-aaab-16614cf88059) ### Use case We have illustrated network sockets and patch panels in Netbox. Not all network sockets are connected to a switch. Using the trace view, you can see which connection a device is connected to at the end of the route. Unfortunately, you first have to click on all the trace buttons to find an existing connection. It is quicker if you can see the start and end devices in the table. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:47:48 +01:00
adam closed this issue 2025-12-29 20:47:48 +01:00
adam commented 2025-12-29 20:47:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 23, 2024):

This is not possible for pass-through (front & rear) ports as they don't terminate an end-to-end connection, whereas interfaces do. If you search closed issues you'll find plenty of discussion on this topic.

@jeremystretch commented on GitHub (Feb 23, 2024): This is not possible for pass-through (front & rear) ports as they don't terminate an end-to-end connection, whereas interfaces do. If you search closed issues you'll find plenty of discussion on this topic.
adam commented 2025-12-29 20:47:49 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Feb 23, 2024):

Too bad. I actually always thought that the through-connectors were a nice idea. But somehow these are so severely limited that it seems more like a half-hearted function. But it's nice that there are several discussions about it. Maybe this feature will get a hearing at some point. Thanks for the feedback though.

;(

@LHBL2003 commented on GitHub (Feb 23, 2024): Too bad. I actually always thought that the through-connectors were a nice idea. But somehow these are so severely limited that it seems more like a half-hearted function. But it's nice that there are several discussions about it. Maybe this feature will get a hearing at some point. Thanks for the feedback though. ;(
adam commented 2025-12-29 20:47:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 23, 2024):

If you're really interested in exploring this, you're more than welcome to try developing and presenting a proof of concept. You would be the first to do so.

@jeremystretch commented on GitHub (Feb 23, 2024): If you're really interested in exploring this, you're more than welcome to try developing and presenting a proof of concept. You would be the first to do so.
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 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#9280
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?