VPN Tunnels #4579

Closed
opened 2025-12-29 18:37:54 +01:00 by adam · 3 comments
Owner

Originally created by @rhys-g-jones on GitHub (Feb 21, 2021).

I know this has been requested in the past and its be turned down rather quickly i believe

In light of the shift to SD-WAN technologies and Tunnels being used to services like Azure and AWS, it would be great to be able to track these connections in Netbox, Circuits i agree are not the correct place for this type of connection but i would like to know peoples thoughts to now considering a dedicated section for Site to Site VPNs or Tunnels

While these don't have guaranteed speeds and fixed mediums they are becoming much more prevalent in todays networking

this is the only major aspect i see missing in netbox

Thanks

Rhys

Originally created by @rhys-g-jones on GitHub (Feb 21, 2021). I know this has been requested in the past and its be turned down rather quickly i believe In light of the shift to SD-WAN technologies and Tunnels being used to services like Azure and AWS, it would be great to be able to track these connections in Netbox, Circuits i agree are not the correct place for this type of connection but i would like to know peoples thoughts to now considering a dedicated section for Site to Site VPNs or Tunnels While these don't have guaranteed speeds and fixed mediums they are becoming much more prevalent in todays networking this is the only major aspect i see missing in netbox Thanks Rhys
adam added the pending closurestatus: revisions needed labels 2025-12-29 18:37:54 +01:00
adam closed this issue 2025-12-29 18:37:54 +01:00
Author
Owner

@xkilian commented on GitHub (Feb 21, 2021):

Maybe this could be a starting point or continuation for your needs: https://github.com/vapor-ware/netbox-virtual-circuit-plugin

@xkilian commented on GitHub (Feb 21, 2021): Maybe this could be a starting point or continuation for your needs: https://github.com/vapor-ware/netbox-virtual-circuit-plugin
Author
Owner

@DanSheps commented on GitHub (Feb 22, 2021):

This issue is pending closure as it does not conform to one of the provided templates as required by the contributing guide. If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).

@DanSheps commented on GitHub (Feb 22, 2021): This issue is pending closure as it does not conform to one of the [provided templates](https://github.com/netbox-community/netbox/issues/new/choose) as required by the [contributing guide](https://github.com/netbox-community/netbox/blob/master/CONTRIBUTING.md). If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).
Author
Owner

@stale[bot] commented on GitHub (Mar 19, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale[bot] commented on GitHub (Mar 19, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4579