Hi,
Currently i have users who are able to connect using our WAN 2, but I am getting server unreachable via the WAN 1 connection. The configuration stopped working today. In the past the IP pool sessions would be clogged up and I would have to kill those manually and it would fix it.
I can ping both DNS for wan1 and wan2 without any issues. When checking internally, it shows as all traffic is going out via WAN 1.
Wan2 is our backup which has lower internet speeds.
Thanks,
EF
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi EF,
Does the route table has active default routes across wan1 as that on wan2? Also, sslvpn settings must have added both the interfaces for listening sslvpn connections.
Best regards,
Jin
Hi jintrah_FTNT,
Under SSL-VPN Settings both (wan1) and (wan2>x_VLAN) are both listening.
Regarding active default routes, when I go to Static Routes, the subnet that my VPN users are obtaining is configured to interface "SSL-VPN tunnel interface (ssl.root)". Which I can see is configured under firewall policies>Incoming interface "SSL-VPN tunnel....".
EF
Hi EF,
I am checking if we have default routes active in the route table, but not sslvpn subnet pointing to ssl.root. Something like below,
S* 0.0.0.0/0 [10/0] via x.x.x.x, wan1 <<<<---
0.0.0.0/0 [10/0] via y.y.y.y, wan2 <<<---
best regards,
Jin
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1634 | |
1063 | |
751 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.