Configuring VIPs
Virtual IPs can be configured for IPv4 and IPv6. After creating the VIP, add it to a firewall policy.
FortiOS does not check whether VIPs overlap. As a result, you can configure multiple VIPs with the same external interface and IP. However, you can view overlapping VIPs in the security rating report. See Viewing VIP overlap in security rating reports.
To configure a VIP in the GUI:
-
Go to Policy & Objects > Virtual IPs and select Virtual IPs.
- Click Create New.
-
Configure the following settings:
Type
Select IPv4 or IPv6.
Name
Enter a name for the VIP.
Comments
Enter a description of the VIP.
Color
Click Change to select a color for the VIP.
Network
Interface (
extintf
)The external interface that the firewall policy source interface must match.
For example, if the external interface is port1, then the VIP can be used in a policy from port1 to port3, but not in a policy from port2 to port3.
If the external interface is any, then the VIP can be used in any firewall policy.
Type (
type
)-
Static NAT - Use an external IP address or address range.
-
FQDN - Use an external IP or FQDN address.
-
load-balance (CLI only) - Load balance traffic.
-
server-load-balance - Load balance traffic across multiple servers. SSL processing can be offloaded to the FortiGate. This type of VIP is configure from Policy & Objects > Virtual Servers.
-
dns-translation (CLI only) - DNS translation.
-
access-proxy - Used for ZTNA. See ZTNA HTTPS access proxy example for details.
External IP address/range (
extip
)In a static NAT VIP, the external IP address is the IP address that the FortiGate listens for traffic on.
When the external interface is not any, 0.0.0.0 can be used to make the external IP address equivalent to the external interface's IP address.
The external IP address is also used to perform SNAT for the mapped server when the server outbound traffic with a destination interface that matches the external interface. The firewall policy must also have NAT enabled.
Map to
IPv6 address/range (
ipv6-mappedip
)The IPv6 address or range that the internal resource is being mapped to.
IPv4 address/range (
mappedip
)The IPv4 address or range that the internal resource is being mapped to.
Optional Filters
Enable to access additional options.
Source address (
src-filter
)Restrict the source IP address, address range, or subnet that is allowed to access the VIP.
Services (
service
)Set the services that are allowed to be mapped.
Port Forwarding (
portforward
)Enable port forwarding and display additional options.
Protocol ( protocol
)Select the protocol to use when forwarding packets to the port.
Port Mapping Type
-
One to one - Each external service port is mapped to one port. A range is allowed, but the number of ports should be the same.
-
Many to Many - The port mapping can be one to one, one to many, or many to one. There are no restrictions on how many external ports must map to internal ports.
External service port (
extport
)Enter the external service port range to be mapped to a port range on the destination network.
Map to IPv6 port (
ipv6-mappedport
)Enter the mapped IPv6 port range on the destination network.
Map to IPv4 port (
mappedport
)Enter the mapped IPv4 port range on the destination network.
-
- Click OK to save the VIP.
Viewing VIP overlap in security rating reports
There is no overlap check for VIPs, so there are no constraints when configuring multiple VIPs with the same external interface and IP. A new security rating report alerts users of any VIP overlaps.
To configure two VIPs with the same external interface and IP:
config firewall vip edit "test-vip44-1" set extip 10.1.100.154 set mappedip "172.16.200.156" set extintf "port24" next edit "test-vip44-1_clone" set extip 10.1.100.154 set mappedip "172.16.200.156" set extintf "port24" set src-filter 10.1.100.11 next end
No error message appears regarding the overlapping VIPs. |
To view the security rating report:
-
Go to Security Fabric > Security Rating and click the Optimization scorecard.
-
Expand the Failed section. The Virtual IP Overlap results show an overlap (test-vip44-1 and test-vip44-1_clone) on the root FortiGate.