Skip to main content
New Member
Sep 16, 2026 1:11 PM UTC
Question

IP Pool and the outside interface IP

Hello - 

   We are in the process of migrating from Cisco firewalls to Fortinet.  We support a large medical system with 3 hospitals and many clinics.  We have several NATs where certain subnets exit the firewall with specific external IP addresses based upon the traffic source networks.  That seems pretty straightforward re-creating with the Central SNAT and overload IP Pools.  After those conditions, our default outbound traffic is sent to the internet using a PAT pool of 4 IP addresses and it will also utilize the WAN interface IP address as well for usage and if there is an issue with the PAT pool, traffic will revert to the interface address. This will keep internet traffic flowing although there will be pool exhaustion.  My question is on the Fortinet can I utilize the WAN interface IP address along with the IP Pools, or is the interface address not used at all?

 

Thank you

3 replies

sw2090
SuperUser
SuperUser
Sep 16, 2026 2:20 PM UTC

hm bascialy on a FGT you could do this:

One internet Policy using SNAT with an IP Pool of n addresses and specific source interface and -address.

One internet Policy using SNAT with WAN IP Address of interface and same source interface and -address.

In this exact order.

Since Policies in FortiOS match top->down it will primarily match the one with SNAT and Pool and if it cannto use that it will match the 2nd one.

 

Just since I never used IP Pools on SNAT on internet policies I cannot say if a pool overflow will lead to not matching that policy.

If anyone knows just pleas let us know here.

Translate
Toshi_Esumi
SuperUser
SuperUser
Sep 16, 2026 4:51 PM UTC

You can use both interface IP and ippool but with separate rule/policy on the same interface regardless it’s central NAT or policy based.

Toshi

Translate
osoleimani
Staff
Staff
Sep 16, 2026 5:25 PM UTC

Hi mlaforge14207,

One important distinction regarding the proposed fallback behavior: an IP Pool configured for SNAT does not automatically fall back to the outgoing interface IP simply because the pool becomes exhausted.

A Fortinet Community Technical Tip explains that when a one-to-one IP Pool is exhausted, traffic requiring an available IP address from that pool can be dropped because FortiGate cannot perform the required NAT.

In the example provided in that document, the additional device uses another firewall policy and therefore receives the default SNAT using the FortiGate WAN interface IP. This is because the traffic matches the second policy—not because FortiGate automatically moved to it after the IP Pool was exhausted.

A document on the Fortinet Library also describes the IP Pool/NAT behavior for FortiOS 7.2.

Therefore, if the requirement is “use these four public IPs normally, but automatically use the WAN interface IP when those addresses are exhausted,” I would not rely on two overlapping policies to provide that fallback behavior.

Hope this clarifies the distinction.

Translate
Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024