Azure VPN Gateway Routing Issue

Question

Hello,

We have 2 vNets in different Location, we need to configure interconnection between them.

We configured 2 vNet and 2 VPN Gateways, status is connected but traffic between servers is not passing, as I think issue is in routing side, I tried a lot of routes, but cant fixed issue. How routing should look like in my case? (see please screenshot). I need to configure interconnectin between 10.1.1.10 <-> 10.2.1.10

Answer 1

Hi immm

Greetings!

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

We understand that you are trying to connect two VNets from different locations and need assistance with routing.

We request you to share the error ping details from the servers. Providing a screenshot of the routing table and configurations would help pinpoint any missing details.

Please check the following details and validate them:

• Ensure that both Vnets are set to allow traffic between them.
• Validate that no Network Security Groups (NSGs) or firewall rules are blocking traffic between the vNets.
•  Verify the routes in your route table and make sure you have added the destination IP which is:
• For VNet 1 to VNet 2, the destination would be 10.2.0.0/16.
• For VNet 2 to VNet 1, the destination would be 10.1.0.0/16.
• Add Next Hop Type as Virtual Network if you are routing through VNet peering or choose VPN Gateway if you're routing through the VPN Gateway (for cross-region traffic).
• Repeat these steps to add routes for both directions (i.e., from VNet 1 to VNet 2 and vice versa).

Once you have created the routes, please associate them with the Same subnet in the VNet.

Refer: https://learn.microsoft.com/en-us/azure/virtual-network/manage-route-table#associate-a-route-table-to-a-subnet

Refer: Troubleshoot virtual network peering issues | Microsoft Learn

Since you are using NVA we request you to check the below details.

https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-troubleshoot-peering-issues#the-peering-status-is-connected

---

If the issue persists after checking the above points, feel free to share the routing details to assist you further.