So, here's the thing. A customer has a default route using, let's say port1(which is a L2L interface) and is using port2 for SSLVPN.
Since the packet to establish the sslvpn connection arrive at port2 and the default route is using port1, rpf drops the connection.
I tired to create a second default route using port2, with bigger distance, but since it's not active on the routing table, it didn't helped at all.
I tried using PBR to route all the traffic to the SSLVPN custom port to port2, but it also didn't worked.
Have you guys ever done something like this?
Solved with two routes with the same distance and different priorities!
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.