Hi All,
Has anyone run into a problem with Fortigate(60E v 6.23) where an outgoing policy is set to use Dynamic NAT but still leaves the FW NATed with the IP of the Outgoing Interface.
This is the Policy:
set name "Out_Test" set uuid xxxxxxxxxxxxxx set srcintf "internal2" set dstintf "wan1" set srcaddr "Internal_IPs" set dstaddr "Test_IP" set action accept set schedule "always" set service "ALL_ICMP" "Custom Send" set logtraffic all set ippool enable set poolname "Nat_Test" set comments " Test Out"
set nat enable
Internal2 - x.x.3.15
Wan1 - x.x.54.12
Internal IPs - x.x.3.61, x.x.3.62, x.x.3.63, x.x.3.64,
Test_ip - x.x.1.33
ippool - Nat_Test - x.x.48.36 -->x.x.48.36
Custom Send - port 50500
Would having ippool set to One to One instead of Overload possible cause the issue we are seeing?
Thank you for any input
Did you run "diag debug flow" and ensure your hiiting the desired fwpolicyid ?
And no, I have never ran into this issues unless I mistakenly apply the cfg to the wrong policy.
Ken Felix
PCNSE
NSE
StrongSwan
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1743 | |
1114 | |
760 | |
447 | |
241 |
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 2025 Fortinet, Inc. All Rights Reserved.