Hello,
Interested in some feedback on a proposed solution to introduce network virtualisation/VPN in a staged fashion to a Hyper-V 2012R2 Estate.
If we have a virtual machine with 1 x NIC (connected to a VLAN tagged network)
<VM> ----- < NIC TAGGED WITH VLAN > ---- < PUBLIC IP>
We can add a second NIC (utilising NVGRE/Network Virtualisation)
<VM> --- < NIC #1 TAGGED WITH VLAN> ---- < PUBLIC IP>
< NIC #2 TAGGED WITH NVGRE/Private Network> ---- < PRIVATE IP>
This permits the machine to utilise both public facing internet connectivity and also access backend resources via its NVGRE/Private network.
We'd then proceed to have site-to-site VPN's terminating on the NVGRE aware VPN gateway. Virtual machines default gateway would point out of the public Vlan tagged NIC - and we would install static routes on the machine to route traffic towards on-premise network via the VPN gateway (within the virtual network)
Is anyone aware of any reasons why such a solution wouldn't scale/ any issues this would cause?
I can't find any definitive information which suggests this isn't supported and potentially gives us a way to role out/enable NVGRE to our existing customer base without migrating everyone to NVGRE.