What I do is use OSPF between the two so when the ISP's fail over, and the tunnel changes, the routes are updated. However you could setup a Policy Base Forwarding rule on the 820 and monitor the ISP A interface. I also use /32 addresses with static routes to make sure the systems monitor the proper path.
Hope that helps.
I want to do the same thing from the sound of your description. Is there anything special you had to do once you specified you wanted to use failover? Where in the configuration do you configure the failover to point to the secondary vpn tunnel or does it failover to the secondary automatically since there are only two tunnels configured?
@Raido I have an ip address assigned to the tunnel interface on each side of the vpn tunnel. Example, tunnel.113 is assigned 18.104.22.168/32 and the other side, tunnel.17 is assigned 22.214.171.124/32. They're also advertising/receiving routes across the tunnel vial ospf. Would the static routes take the place of the ip addresses assigned to the ipsec tunnel ends? I'll read up on the configuration options you mentioned. Thanks!
I guess you are not using Cloudflare DNS if you use 126.96.36.199 in firewall config :)
If you have OSPF configured already then go ahead with that. Not all smaller environments have dynamic routing so static routes could work as well monitoring tunnel failover. That was the reason I mentioned it.
Also if you want to make sure all traffic goes down one tunnel rather than both, you can set the second tunnel interface metric to something like 10000. That way the traffic will prefer the first ISP and if there is a failover event, it'll go down the second.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!