Score:0

Azure VPN <> Head Office <> OpenVPN - No Communication

br flag

To give some idea of the network architecture and the issue;

Head Office has a Pfsense firewall with a site-to-site IPSec VPN connection to some virtual machines in Azure. When on site (192.168.1.1/22) I have no issues communicating to the Azure VNET (10.0.0.0/16) or its VM's.

Remote users connect to head office using OpenVPN on Pfsense (10.8.0.0/24)and can access site resources but can't see the Azure VNET.

I tried adding the route to the OpenVPN server config (push "route 10.0.0.0 255.255.0.0"), but that made no difference.

Any direction on how to make the AZ VNET visible to remote users would be appreciated.

in flag
10.8.0.0/24 is inside 10.0.0.0/16 so when a packet comes from say 10.8.0.2 > 10.0.0.2 then 10.0.0.2 might think that 10.8.0.2 is on the local net and never go back the IPSec route. Try to write a map of how the traffic should flow, and then consider which routes you need for each packet to reach the destination in each device/router. Remember that it needs to flow both ways.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.