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

Remove limitation for circuit connections to interface only #4297

New Issue
Closed
opened 2025-12-29 18:34:30 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:34:30 +01:00
Owner
Copy Link

Originally created by @dejantep on GitHub (Nov 23, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9.4

Proposed Functionality

Allow for connections of circuits to devices with front/rear ports where rear port is connected to another device with front/rear ports.

circuit 1 - front port 1 - device A - rear port - rear port - device B - front port 1 - circuit 2

Use Case

We provide circuits to customers in different sites. Each site has device with front and rear ports. Sites are interconnected via rear port. Devices are CWDM filters. Customers are buying wavelengths as needed.

When at Site A we provide circuit to customer with side A termintated to a front port of device A.
When at Site B we provide circuit to customer with side A terminated to a front port of device B

Database Changes

Not sure

External Dependencies

None

Originally created by @dejantep on GitHub (Nov 23, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/g/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. 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.6.9 * NetBox version: 2.9.4 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Allow for connections of circuits to devices with front/rear ports where rear port is connected to another device with front/rear ports. > circuit 1 - front port 1 - device A - rear port - rear port - device B - front port 1 - circuit 2 <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case We provide circuits to customers in different sites. Each site has device with front and rear ports. Sites are interconnected via rear port. Devices are CWDM filters. Customers are buying wavelengths as needed. When at Site A we provide circuit to customer with side A termintated to a front port of device A. When at Site B we provide circuit to customer with side A terminated to a front port of device B <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Not sure <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam closed this issue 2025-12-29 18:34:30 +01:00
adam commented 2025-12-29 18:34:30 +01:00
Author
Owner
Copy Link

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

The cable tracing logic and validation have been completely overhauled for v2.10 (see #4900). This should no longer be an issue once v2.10 is released, but you can try the beta now if you'd like to help test.

@jeremystretch commented on GitHub (Nov 23, 2020): The cable tracing logic and validation have been completely overhauled for v2.10 (see #4900). This should no longer be an issue once v2.10 is released, but you can try [the beta](https://github.com/netbox-community/netbox/releases/tag/v2.10-beta1) now if you'd like to help test.
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#4297
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?