Description |
This article describes a possible scenario where a user might have a virtual IP configured on the FortiGate to map traffic to the internal server while having a an upstream FortiSwitch in place. |
Scope | FortiSwitch, FortiGate. |
Solution |
See the topology below for reference:
ISP -> port3-FSW -> port6-FGT -> VIP in FGT-> Internal server
In this case, the user has 'L2-WAN1-HA' configured under Port 6, which is acting as a WAN interface.
edit "L2-WAN1-HA" set vdom "root" set allowaccess ping set role wan set snmp-index 155 set interface "flink-dmz" set vlanid 888
The VIP is configured with an ext interface set to any:
set uuid 873d4482-21cc-51ee-3c68-f8ebcfa6bf71
However, periodically, the VIP stops working as traffic is coming into the FortiGate via L2-WAN1-HA and not port 6. As a result, the debug flow output may show 'reverse path check fail, drop' since FortiGate has set the default to the internet route going through port 6.
9.349172 L2-WAN1-HA in 73.10.10.10.10.63804 -> 1.1.1.1.443: syn 3230948464
To avoid this issue, modify the virtual IP address as follows:
edit "Server_HTTPS" set uuid 873d4482-21cc-51ee-3c68-f8ebcfa6bf71 |
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.