Change definition of completed cable path for connection column #9159

Closed
opened 2025-12-29 20:46:22 +01:00 by adam · 1 comment
Owner

Originally created by @julianstolp on GitHub (Jan 26, 2024).

NetBox version

v3.7.1

Feature type

Change to existing functionality

Proposed functionality

The "Connection" field in the interface table should show the device connected at the other end, regardless of the interface type. If I remember correctly, this was implemented in the early 3.x versions.

image
image

see https://github.com/netbox-community/netbox/discussions/14819

Use case

This would be useful for modelling network sockets in offices or other unused ports that currently have no end device. In the current implementation, you have to click on the cable trace for each interface to see what device is connected to the other end, which can quickly become tedious.
Of course, this can be circumvented by modelling such sockets as interface types, but if a device is connected there, the interface must then be deleted and the cables have to be connected to the front port and rear port. Also this does not model the real world correctly.

I want to be able to tell immediately which device is connected at the far-end of a cable path.

Database changes

External dependencies

Originally created by @julianstolp on GitHub (Jan 26, 2024). ### NetBox version v3.7.1 ### Feature type Change to existing functionality ### Proposed functionality The "Connection" field in the interface table should show the device connected at the other end, regardless of the interface type. If I remember correctly, this was implemented in the early 3.x versions. ![image](https://github.com/netbox-community/netbox/assets/41152397/1d5870f0-856a-473c-a8fe-b27d545407cd) ![image](https://github.com/netbox-community/netbox/assets/41152397/01f7a0e8-45ae-4ec3-9e23-b9fc8e1c0dec) see https://github.com/netbox-community/netbox/discussions/14819 ### Use case This would be useful for modelling network sockets in offices or other unused ports that currently have no end device. In the current implementation, you have to click on the cable trace for each interface to see what device is connected to the other end, which can quickly become tedious. Of course, this can be circumvented by modelling such sockets as interface types, but if a device is connected there, the interface must then be deleted and the cables have to be connected to the front port and rear port. Also this does not model the real world correctly. I want to be able to tell immediately which device is connected at the far-end of a cable path. ### Database changes ### External dependencies
adam added the type: featurestatus: duplicate labels 2025-12-29 20:46:22 +01:00
adam closed this issue 2025-12-29 20:46:22 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jan 26, 2024):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #14155 for further discussion.

@jeremystretch commented on GitHub (Jan 26, 2024): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #14155 for further discussion.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9159