Created on 06-09-2023 07:58 AM Edited on 08-20-2024 07:34 AM By Stephen_G
Description | This article describes the difference between 'srcintf-filter' and 'extintf' in the VIP settings. |
Scope | FortiOS, FortiProxy. |
Solution |
'srcintf-filter' and 'extintf' definitions in the VIP settings often bring confusion.
'extintf' is intended to be used as a WebGUI improvement tool. Defining an interface as a value of extintf parameter will make sure that the FortiGate will do the DNAT translation based on the configured VIP object for traffic coming from the selected interface.
Example:
config firewall VIP
With this configuration, that VIP will be available in the WebGUI for selection only if WAN1 is configured as a source interface.
extintf will not bind the VIP to the specific interface. That means that the VIP shown as an example above will accept connections from each and every interface.
config firewall VIP
srcintf-filter is helpful in the setup of failover IPSec tunnel with overlapping subnets to prevent creating separate IP pools and VIP objects for each IPsec tunnel.
If the plan is to create multiple VIPs with the same external IP, different mapped IPs, and different mapped Interfaces; use 'srcintf-filter' to map the VIP to a specific interface as below.
VIP 1:
edit "192.168.150.1-192.168.151.1 wan1_2_VIP-test" set uuid 7b9dfb30-19bf-51ef-57a6-4bb00c9f5c07 next
VIP 2:
set uuid e0db38fa-19bf-51ef-e5b7-de4f20f45894 set extip 192.168.150.1 set mappedip "192.168.151.5" set extintf "Wan2 " set srcintf-filter "Wan2 " next
It is necessary to add the respective firewall policies which allow the traffic. |
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.