We have a VNET (let's call it
VN_MAIN) that is configured to have a S2S VPN connection to our on-premise network. The VMs deployed within subnets of
VN_MAIN are reachable from on-premise.
What I'm trying to do is to create another VNET (
VN_OTHER) and make sure that you can reach on-premise from
VN_OTHER and vice-versa, through
VN_MAIN acting as a hub.
VN_MAIN has an address space of
10.123.128.0/20 (not created by me). I needed a
/16 address space for my new VNET and wanted to avoid overlap, so I created
VN_OTHER with address space
Taking inspiration from the hub-spoke topology described here, I've created a peering on each VNET:
VN_OTHER, forwarded traffic allowed + gateway transit allowed
VN_MAIN, forwarded traffic allowed + use remote gateways checked
Afterwards, to test this, I launched 2 linux machines:
10.230.0.0/16 = the whole space).
According to my understanding of the article I linked, this should be enough for what I'm trying to accomplish. However, it doesn't work properly. Here are the pings I attempted:
machine-2: NOT OK
my-laptop: NOT OK
So, the peering between the VNETs works, but the gateway transit does not, even though I believe I've done everything I was supposed to do to allow it. I am positive this is not an issue with any NSG rules.
Can anyone tell if there's something I am missing here please?