Default Route with next-hop type as VPN_S2S_Gateway missing from Effective Routes

2022-11-04T07:12:38.163+00:00

I have setup a vWAN with One HUB inside. In addition, two VPN gateways have been configured as Site-to-Site to connect with On-premise Gateway.
I have already attached the required vNET to this hub and vNET subnet is visible on my on-premise gateway,

257094-image.png

Tunnel/VPN site Status shows up,

257151-image.png

vWAN Topology for reference,

257133-image.png

I have setup routing on-premise to use this Tunnel and I am able to reach the VM hosted in Azure from VM hosted on-premise. Now, comes the main issue, although Azure VM is responding to the Ping packets, response ping packets are not able to make it out of Azure as a default Route entry is missing from 'effective route' entries inside the Hub.

257086-image.png

Is there a way whereby I can add entries[default Route/Specific Route] inside effective route table manually using next-hop type as VPN_S2S_Gateway so that Hub can route back

Azure Virtual WAN
Azure Virtual WAN
An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.
196 questions
{count} votes