Will there be asymmetric traffic if two tunnels have the same private address space defined or overlapped ?
Suppose I already have an S2S tunnel A on the vWAN with a private address space of 192.12.0.0/16, provided by the on-prem team, and a link IP address A. now need to create another S2S tunnel B on the same vWAN hub, with link IP address B. However, the private address space for tunnel B is 192.12.5.0/24, which falls within the address range of tunnel A (192.12.0.0/16).
Will this overlap cause any issues with tunnel communication to the Azure VMs or vice versa ? Is there a risk of asymmetric traffic ? Or can this be configured without any issues, assuming traffic from both on-prem locations can still communicate with Azure resources via the vWAN s2s tunnels ?
if not, how to achieve it instead of changing the private address space ?