An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
Hi @Charles Pickering ,
Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are trying to set up routing between your on-premises and Azure via a custom VPN server/gateway.
- You informed the VPN VM is able to ping the OnPrem machines.
- You have attached the route table in all other subnets and then pointed the nextHop as the private IP of this VPN VM.
I suggested we,
- Make sure you have enabled IP forwarding in this VPN VM
- Refer "Turn on IP forwarding" under https://learn.microsoft.com/en-us/azure/virtual-network/tutorial-create-route-table-portal
- Post this, let's consider a TestVM.
- The Effective Route of this VM for the OnPrem address range should point to the VPN VM
- https://learn.microsoft.com/en-us/azure/virtual-network/diagnose-network-routing-problem
- Make sure NSG and OS firewall are not blocking traffic to the OnPrem address range.
- You had certain follow up queries on how Azure selects next Hop.
- I informed Azure implements the longest prefix match algorithm for routing. Refer to "How Azure selects a route" under https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview
You informed you are able to resolve the issue, post recreating the environment.
Cheers,
Kapil.
----------------------------------------------------------------------------------------------------------------
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.