How to Connect pfSense to an Azure Virtual Network Gateway Using an IPSec VPN

Discover how to seamlessly connect your pfSense to an Azure Virtual Network Gateway in our latest tutorial. This video guides you step-by-step through the process of integrating pfSense, a powerful open-source firewall and router software, with Azure's Virtual Network Gateway, enabling secure and efficient IPSec VPN connections. Whether you're looking to enhance your network security or expand your cloud-based resources, this tutorial covers all the essentials to setup. Perfect for network administrators and IT professionals, this video will ensure you leverage the full potential of pfSense with a cloud environment. Tune in now to elevate your network connectivity!
#Azure #pfsense #ipsec #vpn #virtualnetworkgateway
00:00 -- Introduction
00:36 -- Understanding the Pieces
02:30 -- Create a Virtual Network Gateway
06:08 -- Create a Local Network Gateway
08:47 -- Create a Connection
11:26 -- Configure and Connect pfSense
15:28 -- Test your VPN
---------------------------------
Blaize’s Website: www.blaize.net
Blaize’s Twitter: / theonemule

[@roxxas5]

This is awesome I'm able to establish the tunnel, but for some reason I can't reach any VMs. Everything has been mimicked perfectly but I still can't access Azure VMs and vise versa

[@BlaizeTech]

That's usually a firewall issue where you're blocking traffic between the networks. Make sure you have allow for traffic to and from the VPN.

[@IrlymMylros]

This really is excellent video. Many thanks for sharing your knowledge.

[@BlaizeTech]

Glad it was helpful!

[@SkillnoMusic]

when i ping the windows server there is always a 50% loss. Do you know why that happens? I did exactly the same as you except that my VPN is a basic SKU, so i put the basic settings in pfsense.

[@BlaizeTech]

What is your ping time looking like for the packets that do make it? Also, try a traceroute to see where the packets are getting dropped in the mix.

[@EJ-gc6os]

I am currently in my office and setting this up because I have a different issue happening (TLDR) where my OpenVPN between two offices stops working when connecting to Azure VPN, so I can't print between offices when connecting to shared drives. When I do "What's My IP" I of course get the public IP for my office. Would that cause conflict since the public IP is being used for my office firewall has the same public IP as the Azure local network gateway?

[@EJ-gc6os]

And then to add to that, if I add my local network (again I am in the office right now) that would be my office LAN. Is the idea that the Azure public IP and local network should mirror my office's?

[@BlaizeTech]

No, I don't think so. The local network gateway is a resource on Azure that tells Azure where to connect the VPN, not an IP address on Azure.

[@BlaizeTech]

@@EJ-gc6os the local network gateway just tells Azure where to find the endpoint. It's not an IP address on Azure. It's the public IP address for your office.

[@EJ-gc6os]

@@BlaizeTech I appreciate the quick response. I just set those and my IPsec is connecting now

[@BlaizeTech]

@@EJ-gc6os Glad it's working for youj!

[@casperghst42]

Interesting, but I'm sorry IPSec VPN is not secure and should be avoided.

[@BlaizeTech]

Not sure if you're talking about a particular IPSec implementation or aspect of it, but generally speaking, IPSec is considered secure and is widely used as the industry standard for site to site connectivity.