How would NetBox model this virtual circuit between containers?

[grinapo]

How should I model a scenario like this, considering the newly introduced Virtual Circuits?
"VPN virtual circuit" is an OpenVPN connection for the sake of example, but wireguard & co. would be the same for VMs.

(Some of my problems:

• I cannot seem to be able to connect Virtual Circuit to interfaces of Virtual machines (Container1 and 2) since the interface cannot be set to virtual type?
• Not clear how eth0 is related to veth100. Parent? Sub-interface (which is not possible I believe on a VM interface)?
• Not clear how to connect eth0/veth100 to bridge2; eth0 is in container, veth100 is in the host, the other end of its pipe.
• Or bridge2 to eth1.99, though I guess the vlan is not a problem.)

[candlerb]

At first glance, I think the "VPN" model (e.g. L2VPN or tunnel) is more suited to what you're trying to do.

"Virtual Circuits" are intended for external provider connections, where one physical cable carries multiple WAN circuits to different destinations.

[grinapo]

Can "VPN" model describe not point-to-point connections? Like openvpn using /22 or similar.
I'll check the vpn models as well, thanks.

[candlerb]

For a multipoint connection use "L2VPN" instead of "Tunnel". An L2VPN can have multiple endpoints (terminations) all joining the same L2VPN.

My only experience of OpenVPN is using it to make point-to-point tunnels.