IPsec multi-wan failover
-
Has anyone had any experience configuring this? It is listed as an option: http://doc.pfsense.org/index.php/2.1_New_Features_and_Changes
I have 2 offices with Multi-Wan failover due to problematic internet connections and both locations have IPSEC tunnels going back to the hub(Office) location and need the VPN tunnel to be able to stay up if the WAN fails over.
Any tutorials???
Each location has only one pfsense box. Not Carp
-
It should work fine though for pfSense to pfSense you need both the IPsec tunnel set to a failover gateway group and a DynDNS entry set to the same failover gateway group, and then use that dyndns host as the remote peer address for the other side.
Then when WAN1 fails to WAN2, the dyndns IP changes, so the far side knows to accept the new peer, and that's where IPsec will start connecting from.
-
Are there any tutorials for this process? I have not been able to find one…
-
Not yet. That's really all there is to it though.
Setup DynDNS, set to use a failover gateway group.
Setup IPsec to use the same failover gateway group.
Set the other end to use the dyndns host as the peer address. -
but DynDns uses a name and the gateways require IP addresses so I am not following you.
-
IPsec peers can be hostnames.
The identifier is left as "My IP Address" and "Peer IP Address". The remote gateway for IPsec is the dyndns hostname.
-
jim, what were the changes in 2.1 that facilitated this new IPsec multi-wan failover feature ?
-
I'd have to dig through the code, I don't recall, it's been several months. databeestje originally did the work.
-
Hi.
I have setup this with 2 pfsense 2 dedicated static IP WAN.
Results are not what I expect:
Wen WAN1 goes down on Local PFsense:
Dyn update failovergroup.
Firewall rules using failover group as wan acts correctly.
IPSec tunnel does not UP. Logs show that is trying to use WAN1 IP adress to stablish tunel. Remote pfsense does not permit connections from that peer.Remote PFSense:
IPSec tunnel goes down after timeout, as Dyn hostname has been updated, IPSec tries to stablish tunnel to new IP Address, Remote PFsense does not respond.
IPSec logs shows a unknown peer trying to stablish a connection to local ipsec port.Solution:
I have to restart racoon service on Local PFSense for racoon start using WAN2 IP.Same results if WAN1 goes down on Remote PFSense.
Is there a way to add than when routing changes due multiwan failover, a service(s) can be restarted?
-
Try the patch from this ticket:
http://redmine.pfsense.org/issues/2896 -
Thank you so much.
I will try it.
-
I have the same issue but I don't know how to apply the path
-
Did anyone ever do do this successfully?
Also, has anyone successfully done multi-wan failover with a sonicwall?
I also do not know how to apply the patch mentioned except to manually make the changes which doesn't seem like the best idea.
-
The patch is no longer needed. There is a checkbox to activate the behavior on 2.1 (System > Advanced, Misc tab, under IP Security)
-
Ah, got it. So I guess there's no way to use mutiple gateways for the remote side except to use Dynamic DNS?
-
Flojose, what was the behavior after you appplied the patch code?
Results as expected ?
-
Can this be done if one side of the VPN is not a pfSense? I am going to a Fortigate on Fiber in Atlanta with a pfSense in Michigan with Cable and DSL connections.
Thanks!
-
Can this be done if one side of the VPN is not a pfSense? I am going to a Fortigate on Fiber in Atlanta with a pfSense in Michigan with Cable and DSL connections.
Did you ever get an answer on this? I have a similar scenario and before I bang my head against the wall just wanted to know if you got it working.
-
No unfortunately.
-
Hello guys,
I have the pfSense firewall 2.1.3 and need configure ipsec failover with sonicwall. I know that sonicwall have the option for add the second peer in the configuration ipsec vpn, very easy.
Do you configure failover ipsec vpn?