Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
boozely25
New Contributor

Policy set to NAT to IP Pool is still using Outgoing Interface

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

 

 

1 REPLY 1
emnoc
Esteemed Contributor III

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  

PCNSE NSE StrongSwan
Labels
Top Kudoed Authors