Allow connection of devices between remote sites #30

Closed
opened 2025-12-29 15:30:00 +01:00 by adam · 3 comments
Owner

Originally created by @callumbnz on GitHub (Jun 28, 2016).

not sure if this is by design or a bug - but I am unable to connect devices together that are not in the same location.

Also on the circuits management stuff - it would be good if you could have an A-Port and a B-Port - as we have several leased lines that go between facilities

Originally created by @callumbnz on GitHub (Jun 28, 2016). not sure if this is by design or a bug - but I am unable to connect devices together that are not in the same location. Also on the circuits management stuff - it would be good if you could have an A-Port and a B-Port - as we have several leased lines that go between facilities
adam closed this issue 2025-12-29 15:30:00 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jun 28, 2016):

You're not missing anything. Circuits currently only support a single endpoint, with the other endpoint being "the cloud" (e.g. provider backbone or the public Internet). I'd like to extend this, but it's a fair amount of work and I didn't want to delay the release any longer.

@jeremystretch commented on GitHub (Jun 28, 2016): You're not missing anything. Circuits currently only support a single endpoint, with the other endpoint being "the cloud" (e.g. provider backbone or the public Internet). I'd like to extend this, but it's a fair amount of work and I didn't want to delay the release any longer.
Author
Owner

@callumbnz commented on GitHub (Jun 28, 2016):

Ah - sweet as then!

Feature request ahoy!

On Tue, Jun 28, 2016 at 12:21 PM, Jeremy Stretch notifications@github.com
wrote:

You're not missing anything. Circuits currently only support a single
endpoint, with the other endpoint being "the cloud" (e.g. provider backbone
or the public Internet). I'd like to extend this, but it's a fair amount of
work and I didn't want to delay the release any longer.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/49#issuecomment-228930737,
or mute the thread
https://github.com/notifications/unsubscribe/AMzglyJBBxTo4jCHV9iNowBK4DuJpVMjks5qQIUXgaJpZM4I_oFH
.

Callum Barr
me@callumb.com

@callumbnz commented on GitHub (Jun 28, 2016): Ah - sweet as then! Feature request ahoy! On Tue, Jun 28, 2016 at 12:21 PM, Jeremy Stretch notifications@github.com wrote: > You're not missing anything. Circuits currently only support a single > endpoint, with the other endpoint being "the cloud" (e.g. provider backbone > or the public Internet). I'd like to extend this, but it's a fair amount of > work and I didn't want to delay the release any longer. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > https://github.com/digitalocean/netbox/issues/49#issuecomment-228930737, > or mute the thread > https://github.com/notifications/unsubscribe/AMzglyJBBxTo4jCHV9iNowBK4DuJpVMjks5qQIUXgaJpZM4I_oFH > . ## Callum Barr me@callumb.com
Author
Owner

@mjclancyau commented on GitHub (Aug 18, 2016):

Just adding my support for this feature. Very useful for guys who have a lot of L2 Access tails, or even DF/ME between DCs etc.

@mjclancyau commented on GitHub (Aug 18, 2016): Just adding my support for this feature. Very useful for guys who have a lot of L2 Access tails, or even DF/ME between DCs etc.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#30