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

Interface Connections to Virtual interfaces should not be allowed #2120

New Issue
Closed
opened 2025-12-29 17:22:27 +01:00 by adam · 0 comments
adam commented 2025-12-29 17:22:27 +01:00
Owner
Copy Link

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

Environment

  • Python version: 3.7.1
  • NetBox version: 2.5 Develop

Steps to Reproduce

Create Two devices one with the physical interface and another with the virtual interface
Connect Physical interface device port to another device which has the virtual interface and chooses virtual interface name

Expected Behavior

  • The user should not be able to select interfaces and as well able to connect to the virtual interface
  • This should also be validated in API
  • This also be validate for Rear-Port/Front Port Connection.

Observed Behavior

I was able to connect Physical Interface to Virtual Interface. this is also true if someone is trying connect using Front/Rear Ports

capture

Originally created by @a31amit on GitHub (Nov 13, 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.1 * NetBox version: 2.5 Develop <!-- 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). --> ### Steps to Reproduce Create Two devices one with the physical interface and another with the virtual interface Connect Physical interface device port to another device which has the virtual interface and chooses virtual interface name <!-- What did you expect to happen? --> ### Expected Behavior - The user should not be able to select interfaces and as well able to connect to the virtual interface - This should also be validated in API - This also be validate for Rear-Port/Front Port Connection. <!-- What happened instead? --> ### Observed Behavior I was able to connect Physical Interface to Virtual Interface. this is also true if someone is trying connect using Front/Rear Ports ![capture](https://user-images.githubusercontent.com/6764613/48382691-0e598c80-e697-11e8-886e-c67566214ea8.JPG)
adam added the type: bugstatus: accepted labels 2025-12-29 17:22:27 +01:00
adam closed this issue 2025-12-29 17:22:27 +01:00
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 status: accepted type: bug
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#2120
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?