Troubleshooting Tip: Traffic continues to match firewall policy after Virtual IP removal
| Description | This article describes a scenario where traffic continues to match a firewall policy on a FortiGate even after the associated Virtual IP (VIP) has been removed. The article provides a step-by-step guide to resolving this issue by clearing existing sessions in the session table. |
| Scope | FortiGate. |
| Solution | To resolve this issue, follow these steps:
In the following example, the Virtual IP sessions were filtered with the internal port:
Collect the debug flow and iprope list output for VIP rules before applying the above; this will make sure that the VIP is not in use for any policy:
diagnose debug reset
Replicate the issue.
diagnose debug disable
diagnose firewall iprope list 100000
The VIP will still be used for source NAT, even when not applied in a policy, to avoid having issues. To avoid issues, the best approach is to delete it and keep the configuration as clean as possible.
By default, VIP gets hit if traffic comes from any source/ any interface, hence source filter with IP or source interface can be configured to limit the VIP usage.
config firewall vip end
Related articles: Technical Tip: iPrope policies group Technical Tip: Mapping VIP outbound connections (Source NAT) |


