Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,454 questions
PFSense ipsec tunnel network access issue
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 5%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Sourish Ghosh
0
Reputation points
We created ipsec tunnel in PFSense on Azure cloud. The tunnel is connected & from the remote network (192.9.200.0/24) we are able to ping the WAN & LAN ports of the PFSense but unable to ping/connect to any VM (10.100.0.0/16) on azure cloud.
IP forwarding is turned on pfsense wan & lan interface.
{count} votes
-
KapilAnanth-MSFT 45,451 Reputation points Microsoft Employee2024-08-07T05:46:27.04+00:00 Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
From your verbatim, you are using a 3rd party solution to establish S2S between Azure VNET and OnPrem.
While Community members in Q&A have expertise over Azure Products, the same cannot be said for 3rd party devices and configuration.
I would suggest you to reach out to the 3rd party Support / forums to get assistance on troubleshooting guides.
With that said,
- How are you directing traffic from other VMs in the VNET to go to OnPrem via the 3rd party NVA
- Did you create UDRs on the VMs' subnets so the return traffic can be routes to the 3rd party NVA ?
- If not, consider using a UDR with nextHop as NVA IP and route as the OnPrem address range.
- If the above doesn't help, please verify the OS Configuration on the NVA
Cheers,
Kapil
Sign in to comment
Sign in to answer