Route from Azure VM to spoke of Nebula site-to-site VPN

IctPk
IctPk Posts: 1
edited June 1 in Nebula
Hello,
We created a site-to-site VPN from Azure to a NSG (location 1) with subnet 172.1.0.0/16. I can ping that location from the VM. From location 1 I can ping location 2 (172.5.0.0/16 /a remote vpn participant / hub-and-spoke). How can I ping a device in location 2 from the Azure VM? 
In Azure I made a routetable to route 172.5.0.0/16 to the location 1 NSG gateway address, I tried to route 172.5.0.0/16 through the STS-vpn in Azure. But I don't understand the routing principles in this situation. Do I only need a added route in Azure or do I need added routes in the NSG's too? And how do I route a subnet that is outsite the subnet the STS-vpn? In Azure it was not possible to make a route saying 172.5.0.0/16 next hop is the gateway to location 1. Where to start? I presumed that if I was able to route the traffic to location 1 the routing to location 2 and back to Azure was taken care of by the NSG's, is that correct? 

All Replies

  • Zyxel_Jason
    Zyxel_Jason Posts: 280  Zyxel Employee
    Hi @IctPk,

    Welcome to Zyxel community!

    You will need to configure the following:
    1. Create a new policy route on Azure site gateway to route the Source IP <Azure site> and destination IP 172.5.0.0/16 via Site-to-Site VPN tunnel.
    2. Configure availability as All site in Non-Nebula VPN peer at location 1 site.
    (You may refer to this post)
    3. Create a new policy route on location 2 site to route the Source IP 172.5.0.0/16 and destination IP <Azure site> via Site-to-Site VPN tunnel.

    Hope it helps.
    Jason
Sign In to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click on this button!