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

Add support for virtual circuit overlays #5536

New Issue
Closed
opened 2025-12-29 19:29:06 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:29:06 +01:00
Owner
Copy Link

Originally created by @mirackle-spb on GitHub (Oct 20, 2021).

NetBox version

v3.0.2

Feature type

Data model extension

Proposed functionality

There is many talking about this feature, but for many years it still the same. All issues about is is closed.
Netbox currently supports physical circuits. There is not enough information right now. I asked to extend model of circuits in #7586, but it was closed. I dont know why. Any circuits it not from one DC to another. It from one port to another.
So if circuits model will be extended - add virtual circuits - will be easy.
Only one difference that we have in virtual circuit - multiple endpoints and that will be enough.

Use case

MPLS/VxLAN/EVPN/VPWS/VPWS documenting and possible provisioning automation.

Database changes

No response

External dependencies

No response

Originally created by @mirackle-spb on GitHub (Oct 20, 2021). ### NetBox version v3.0.2 ### Feature type Data model extension ### Proposed functionality There is many talking about this feature, but for many years it still the same. All issues about is is closed. Netbox currently supports physical circuits. There is not enough information right now. I asked to extend model of circuits in #7586, but it was closed. I dont know why. Any circuits it not from one DC to another. It from one port to another. So if circuits model will be extended - add virtual circuits - will be easy. Only one difference that we have in virtual circuit - multiple endpoints and that will be enough. ### Use case MPLS/VxLAN/EVPN/VPWS/VPWS documenting and possible provisioning automation. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:29:06 +01:00
adam closed this issue 2025-12-29 19:29:06 +01:00
adam commented 2025-12-29 19:29:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 20, 2021):

Per the feature request form:

Describe in detail the new feature or behavior you are proposing. Include any specific changes to work flows, data models, and/or the user interface. The more detail you provide here, the greater chance your proposal has of being discussed. Feature requests which don't include an actionable implementation plan will be rejected.

You haven't provided any detail in your proposal. Are you interested in investing some time into developing a rough model to present for discussion? If not, this FR will be closed.

I asked to extend model of circuits in #7586, but it was closed. I dont know why.

Please re-read my comment explaining why I closed it.

@jeremystretch commented on GitHub (Oct 20, 2021): Per the feature request form: > Describe in detail the new feature or behavior you are proposing. Include any specific changes to work flows, data models, and/or the user interface. The more detail you provide here, the greater chance your proposal has of being discussed. Feature requests which don't include an actionable implementation plan will be rejected. You haven't provided _any_ detail in your proposal. Are you interested in investing some time into developing a rough model to present for discussion? If not, this FR will be closed. > I asked to extend model of circuits in #7586, but it was closed. I dont know why. Please re-read [my comment](https://github.com/netbox-community/netbox/issues/7586#issuecomment-946934970) explaining why I closed it.
adam commented 2025-12-29 19:29:08 +01:00
Author
Owner
Copy Link

@SteveRodrigue commented on GitHub (Oct 28, 2021):

/subscribing

I suppose my closed feature request (#7675) is matching this request. Basically being able to attach LAG or virtual interfaces to a (virtual) circuit would make sense.

There is plenty of exemples:

  • A carrier delivering multiple point-2-point circuits through a single physical circuit (using vlan tagging).
  • VXLAN/L3vpn attached to 1+ sub-interface(s) in many devices.
  • Public Cloud interconnect and SDWAN: multiple layer-3 end-to-end connections passing through 1 physical circuit.

At the moment, it's not possible to terminate a circuit onto any non-physical interface.

@SteveRodrigue commented on GitHub (Oct 28, 2021): /subscribing I suppose my closed feature request (#7675) is matching this request. Basically being able to attach LAG or virtual interfaces to a (virtual) circuit would make sense. There is plenty of exemples: - A carrier delivering multiple point-2-point circuits through a single physical circuit (using vlan tagging). - VXLAN/L3vpn attached to 1+ sub-interface(s) in many devices. - Public Cloud interconnect and SDWAN: multiple layer-3 end-to-end connections passing through 1 physical circuit. At the moment, it's not possible to terminate a circuit onto any non-physical interface.
adam commented 2025-12-29 19:29:08 +01:00
Author
Owner
Copy Link

@mirackle-spb commented on GitHub (Oct 29, 2021):

currently we can attach circuits only to device. Not even to physical interfaces.

@mirackle-spb commented on GitHub (Oct 29, 2021): currently we can attach circuits only to device. Not even to physical interfaces.
adam commented 2025-12-29 19:29:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 29, 2021):

@mirackle-spb circuits do in fact terminate on interfaces, not devices.

I'm going to close this issue as you haven't responded to my request for more detail. If you'd like to rewrite your proposal at a later time, you're welcome to do so.

@jeremystretch commented on GitHub (Oct 29, 2021): @mirackle-spb circuits do in fact terminate on interfaces, not devices. I'm going to close this issue as you haven't responded to my request for more detail. If you'd like to rewrite your proposal at a later time, you're welcome 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 status: revisions needed 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#5536
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?