Introduction#
Central SNAT lets a FortiGate apply source address translation using a separate NAT table. In this lab, the same client connects to the same external endpoint in two scenarios. The first uses the outgoing interface address. The second uses an overload IP pool.
The tests show how the selected source address changes while the firewall policy remains the same. A temporary TCP listener on port 443 is used as the destination, so the results demonstrate TCP connectivity rather than an HTTPS application or TLS transaction.
Lab Environment#
The lab uses a FortiGate VM64-KVM, security zones, a Win10 client, and a Win7 external test endpoint. The client reaches the FortiGate through an L3 switch. WAN1 connects toward the external endpoint through ISP-1 and an Internet router.
| Component | Lab configuration |
|---|---|
| Client | Win10, 10.10.20.2 |
| FortiGate LAN transit | port2, 10.10.10.1/30, member of Z-LAN |
| L3 switch transit | 10.10.10.2/30 |
| Client network | LAN-NET, 10.10.20.0/24 |
| FortiGate WAN1 | port3, 198.51.100.2/24, member of Z-WAN1 |
| External test endpoint | Win7, 203.0.113.10, TCP port 443 |
| Firewall policy | LAN-WAN1-HTTPS, ID 100 |
| Central SNAT entry | ID 100 |
| Overload IP pool | POOL-WAN1, 198.51.100.100 |

Figure 1. FortiGate interfaces and security zones used in the lab.
Prerequisites#
- Central NAT is enabled on the FortiGate.
- Routing is configured between the client, the FortiGate, ISP-1, and the external endpoint, including the return path.
- The client network is represented by the
LAN-NETaddress object. - The Win7 endpoint has a temporary TCP listener on port 443, and its firewall permits the test traffic.
- The two scenarios are tested sequentially, using a new connection after changing the Central SNAT entry.
How the Policies Work Together#
The firewall policy decides whether the new connection is allowed. After an accepting firewall policy matches, the Central SNAT table determines the source translation. The Central SNAT entry is evaluated separately from the firewall policy. The two IDs happen to be 100 in this lab; they are not linked by their numbers.
The firewall policy matches traffic from Z-LAN to Z-WAN1, with source LAN-NET, destination all, and service HTTPS. The name of the service object identifies the policy's port match. The lab test itself uses TCP connectivity rather than an HTTPS application.
1config firewall policy
2 edit 100
3 set name "LAN-WAN1-HTTPS"
4 set srcintf "Z-LAN"
5 set dstintf "Z-WAN1"
6 set action accept
7 set srcaddr "LAN-NET"
8 set dstaddr "all"
9 set schedule "always"
10 set service "HTTPS"
11 set logtraffic all
12 next
13end
Figure 2. Firewall policy 100 allows the test traffic from the LAN zone to WAN1.
For a new connection, the simplified outbound flow is:
1Win10 10.10.20.2
2 -> port2 / Z-LAN
3 -> route lookup selects port3 / Z-WAN1
4 -> firewall policy 100 accepts the connection
5 -> Central SNAT entry 100 selects the source translation
6 -> port3 toward the external endpointFortiGate uses the session to reverse the translation for the return traffic.
Scenario 1: Outgoing Interface Address#
The first test uses the WAN1 interface IP as the translated source. Central SNAT entry 100 matches Z-LAN to Z-WAN1, with LAN-NET as the original source and all as the destination. NAT is enabled and the entry does not reference an IP pool.
1config firewall central-snat-map
2 edit 100
3 set status enable
4 set srcintf "Z-LAN"
5 set dstintf "Z-WAN1"
6 set orig-addr "LAN-NET"
7 set dst-addr "all"
8 set nat enable
9 unset nat-ippool
10 next
11end
Figure 3. Central SNAT entry 100 before the IP pool is selected.
Test and packet flow
The Win10 client tests TCP port 443 on the external endpoint:
1Test-NetConnection 203.0.113.10 -Port 443The captured test reports TcpTestSucceeded : True. The FortiGate sniffer shows the source address changing to the outgoing interface IP, 198.51.100.2.
| Capture point | Source | Destination |
|---|---|---|
port2 ingress | 10.10.20.2:49761 | 203.0.113.10:443 |
port3 egress | 198.51.100.2:49761 | 203.0.113.10:443 |
port3 reply ingress | 203.0.113.10:443 | 198.51.100.2:49761 |
port2 reply egress | 203.0.113.10:443 | 10.10.20.2:49761 |

Figure 4. The client source is translated to the port3 interface address, and the reply is translated back.
The packet capture shows SYN, SYN-ACK, and ACK. The source port shown is the observed value for this connection; a different connection can use a different port.
Scenario 2: Overload IP Pool#
The second test starts from the first scenario. The firewall policy remains the same. An overload IP pool is created with one translated address, 198.51.100.100, and assigned to Central SNAT entry 100.
1config firewall ippool
2 edit "POOL-WAN1"
3 set type overload
4 set startip 198.51.100.100
5 set endip 198.51.100.100
6 set arp-reply enable
7 set arp-intf "port3"
8 next
9end
Figure 5. POOL-WAN1 uses a single overload address and enables ARP reply on port3.
Assign the pool to the existing Central SNAT entry:
1config firewall central-snat-map
2 edit 100
3 set nat-ippool "POOL-WAN1"
4 next
5end
Figure 6. Central SNAT entry 100 references POOL-WAN1.
Test and packet flow
The client runs the same TCP test using a new connection. This time, the expected translated source is the pool address rather than the interface address.
1Test-NetConnection 203.0.113.10 -Port 443
Figure 7. The Win10 client reports a successful TCP connection to the external endpoint.
The following packet flow comes from the captured connection using source port 49762:
| Capture point | Source | Destination |
|---|---|---|
port2 ingress | 10.10.20.2:49762 | 203.0.113.10:443 |
port3 egress | 198.51.100.100:49762 | 203.0.113.10:443 |
port3 reply ingress | 203.0.113.10:443 | 198.51.100.100:49762 |
port2 reply egress | 203.0.113.10:443 | 10.10.20.2:49762 |

Figure 8. The connection leaves with the IP pool address and receives a reply.
The matching traffic log identifies firewall policy 100, Central NAT Table ID 100, and NAT IP 198.51.100.100 for source port 49762.

Figure 9. Traffic log details for the connection shown in the packet capture.
Comparing the Results#
| Setting | Outgoing interface address | Overload IP pool |
|---|---|---|
| Original source | 10.10.20.2 | 10.10.20.2 |
| Translated source | 198.51.100.2 | 198.51.100.100 |
| Firewall policy | 100 | 100 |
| Central SNAT entry | 100 | 100 |
| TCP test | Successful | Successful |

Figure 10. Traffic logs show the two translated source addresses under the same firewall policy.
The overload pool uses one configured address in this lab. Overload can share an address across connections using port translation, but the lab captures do not test multiple clients or pool exhaustion.
Troubleshooting Notes#
The first TCP test did not receive a reply. The external Win7 endpoint had no listener on TCP port 443. After a temporary TCP listener was started, Test-NetConnection succeeded and the FortiGate capture showed the handshake.
During testing, Windows PowerShell interpreted curl as Invoke-WebRequest, which did not accept the curl -k option. The final lab verification used Test-NetConnection and the packet sniffer instead.
If the translated source is still the WAN interface address after selecting the pool, create a new connection and check the matching Central SNAT entry. If the pool address appears on egress but the reply does not return, check the upstream return path and ARP handling for the pool address.
Security and Operational Notes#
- Restrict firewall policies and NAT rules to the source networks, destinations, and services required by the environment.
- The IP pool is in the WAN1 subnet in this lab. The captured configuration enables ARP reply on
port3; upstream delivery must be appropriate for the address design. - The temporary TCP listener validates TCP connectivity only. A real HTTPS test requires an HTTPS service and its own TLS configuration.
- The captures show the results of this lab. Validate routing, policy order, address ownership, and NAT behavior before applying a similar design elsewhere.
Conclusion#
Both scenarios used the same firewall policy and Central SNAT entry. The packet captures show that the outgoing interface scenario translated the client source to 198.51.100.2, while the overload IP pool scenario translated it to 198.51.100.100. TCP connectivity succeeded in both tests.