0

I have a Virtual Network(VPN Network) with a Virtual Network Gateway, which is connected to VPN instance on AWS using Site-to-Site connection.

Also, I created two networks VNET-A(10.10.0.0/16) and VNET-B(10.20.0.0/16) with peerings connected to VPN Network.

Network Peering connections However, I'm unable to ping instances from AWS network. Is there something I'm missing?

Current setup

My goal is to access instances in VNET-A and VNET-B directly from AWS network.

  • Please show your route tables in AWS and Azure. – Ron Trunk Nov 22 '19 at 20:30
  • Hi @RonTrunk, I created a route table for VPNNW GatewaySubnet and added route to 10.10.0.0/16 network with next hop as virtual network. – Varun Nov 26 '19 at 18:21
0

Azure Peering is not transitive, there from traffic from the VPN will need be able to reach the peered network.

You can overcome this by adding custom routes to direct the traffic to the locations you require.

  • I need to direct traffic coming into the gateway to their respective networks. Sorry for noob questions. I'm totally new to the platform. – Varun Nov 25 '19 at 17:52
  • You’ll need to add custom routes to direct the traffic where you want it to go. – Sam Cogan Nov 25 '19 at 18:07
  • Created a new route table for VPNNW GatewaySubnet and added VNET-A address range to the route table. However, it still doesn't route the traffic. – Varun Nov 26 '19 at 18:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.