Cable connections same device validation missing #2102

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

Originally created by @a31amit on GitHub (Nov 8, 2018).

Environment

  • Python version: 3.7
  • NetBox version: 2.5-beta1

There seems to be some bug in cable connection, It lets a user connect the same device and same port
It should generate some error message for the user, as in the real world someone cannot attach the same cable to the same interface; another side of the cable has to go somewhere.

There are chance's that someone has a cable in one interface and other side doesn't go anywhere but those cases for future planning or some temporary purpose.

Not sure if this behavior exists in API as well.

Steps to Reproduce

Create a Device
Click on Connect a cable
Select same device and interface -> same port

Expected Behavior

It should generate some error message for the user, as in the real world you cannot the same cable to the same interface, another side of the cable has to go somewhere

Observed Behavior

It let me add cable connection to the same device and same interface -

capture

Originally created by @a31amit on GitHub (Nov 8, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7 * NetBox version: 2.5-beta1 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> There seems to be some bug in cable connection, It lets a user connect the same device and same port It should generate some error message for the user, as in the real world someone cannot attach the same cable to the same interface; another side of the cable has to go somewhere. There are chance's that someone has a cable in one interface and other side doesn't go anywhere but those cases for future planning or some temporary purpose. Not sure if this behavior exists in API as well. ### Steps to Reproduce Create a Device Click on Connect a cable Select same device and interface -> same port <!-- What did you expect to happen? --> ### Expected Behavior It should generate some error message for the user, as in the real world you cannot the same cable to the same interface, another side of the cable has to go somewhere <!-- What happened instead? --> ### Observed Behavior It let me add cable connection to the same device and same interface - ![capture](https://user-images.githubusercontent.com/6764613/48179143-7c3a3880-e2d2-11e8-8c2a-95eba30f3d43.JPG)
adam added the type: bugstatus: accepted labels 2025-12-29 17:22:20 +01:00
adam closed this issue 2025-12-29 17:22:21 +01:00
Author
Owner

@jbakklund commented on GitHub (Nov 8, 2018):

This bug/feature could be used to describe a loopback connection. Those are though not part of the intended state in our networks, but you could actually find a use-case for it.

@jbakklund commented on GitHub (Nov 8, 2018): This bug/feature could be used to describe a loopback connection. Those are though not part of the intended state in our networks, but you could actually find a use-case for it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2102