Skip to main content
chinyu
New Member
Oct 6, 2026 9:50 AM UTC
Question

NAT Behavior on Dual ISP

Currently, I have a FortiGate configured with two ISPs, with WAN1 as the primary connection and WAN2 as the secondary connection.
For the LAN-to-Internet policy, I have a fixed IP pool NAT configured using the usable IP provided by WAN1. When I introduced an additional IP pool NAT on the LAN-to-Internet policies using the WAN2 Interface IP, users reported that they were unable to access the internet.
After reverting the change and removing the WAN2 IP pool, internet connectivity was immediately restored for the users.

My question would be:
- What is the recommended NAT design for a FortiGate with DUAL ISP connectivity when an existing IP pool nat is already in use?
- Are there known considerations or limitations when using fixed IP pool NAT address in a multi-WAN deployent?
- Are there any FortiGate best practices for maintaining internet connectivity while introducing NAT rules in a dual ISP environment?

    2 replies

    funkylicious
    SuperUser
    SuperUser
    Oct 6, 2026 10:14 AM UTC

    are you using active/active setup, when both ISP/WAN links are used at the same time - meaning you have SDWAN configured?

    are you using ip pool for WAN2 for a specific reason?

    is the ip pool you created using a ip that is part of the network allocated/configured to you on WAN2 by the ISP ? i assume that the internet connection for users that are going out using this link to the internet no longer works and those using WAN1 are ok.

    Translate
    "jack of all trades, master of none"
    osoleimani
    Staff
    Staff
    Oct 6, 2026 5:22 PM UTC

    Hi chinyu,

    One important point to check is the relationship between the IP pool and the WAN interface actually used for the session.

    An IP pool defines the source address used for SNAT; it does not by itself determine which WAN connection the traffic uses. If a WAN1 public IP pool is applied to a policy and the same traffic can fail over and exit through WAN2, the session may be NATed to the WAN1 address while being sent through WAN2. That can cause the upstream WAN2 connection to reject the traffic.

    FortiOS supports associating an IP pool with a specific interface so that the pool is only used when traffic exits through that interface. Fortinet documents this behavior in Technical Tip: How to associate a NAT pool (IP pool) to a physical interface of an SD-WAN.

    The current FortiOS CLI reference also documents the associated-interface option for IP pools: config firewall ippool — FortiOS 7.6.6.

    If WAN1/WAN2 are using traditional primary/backup routing rather than SD-WAN, the same principle is worth checking: make sure the SNAT address belongs to the WAN interface through which the session is actually leaving.

    Hope this helps narrow down why adding the WAN2 IP pool changes the Internet connectivity.

    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