Return route to appliance from peered network

Question

Hi All,
I have two vnets peered together, one has an openvpn appliance providing p2s vpn services. I'm trying to connect to a resource in the remote vnet across the vpn and I'm getting connection timeouts. For resources in the same vnet as the openvpn setup we added a customer route to route the vpn's ip pool addresses back to the appliance. This works. I associated this same route table with the remote vnet but this hasn't resolved the issue. After creating a vm in the remote vnet to get a view of the effective routes I realise that the next hop when in the remote vnet is probably not accessible without the next hop address needing to being routed. Is there some way to get the returning traffic for a specific range of non-vnet addresses back to an ip peered network? If so, how?

Regards,

Ashley

Answer 1

Hello @Ashley

Thank your for your post.

I was reading at your scenario description, I could see that you need some help on this one.

For instance, I would like to get more familiar if possible so, read below:

-Is this just 2 spokes instances or do you have hub-and-spoke Vnet design?
-You were mentioning that a customer route was added on the P2S pool range but the question is.... Do you configure any UDR(User Defined routes) routing table?
-When you said that there is a OpenVPN appliance... Are your referring to a Network Virtual Appliance(NVA)??

Furthermore, This brought my attention ...

After creating a vm in the remote vnet to get a view of the effective routes I realise that the next hop when in the remote vnet is probably not accessible without the next hop address needing to being routed.

For that same statement, I was asking you if you have a hub-and-spoke design as well as UDR routing table...

Looking forward to your feedback,

Best Regards,

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.