Will there be asymmetric traffic if two tunnels have the same private address space defined or overlapped ?

$@chin 115 Reputation points
2024-11-07T18:41:45.9766667+00:00

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 ?

Azure Virtual WAN
Azure Virtual WAN
An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.
229 questions
Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,565 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,532 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.