Connect SSL vpn to secondary Wan that isn’t active
We have recently been testing some new ISP connections for failover on our Fortigate 200e, the failover is working fine but during testing we have made the secondary wan the primary one. There is no issue with the secondary connection and it is still up and running but users can not connect to it via SSL. Is there a way to make this work?
Posted May 24, 2019, 12:13 AM UTC
22
Sounds like a routing issue. Create two static default routes where they have the same distance but different priority. This way one circuit is preferred outbound but both circuits can be used inbound.
That’s it, my distances were different, now I can talk on them all