1. Firewall policy SNAT
only in NGFW profile mode. for simply NAT deployment.
2. Central SNAT
Can be enabled in NGFW profile mode, NGFW policy mode only supports Central SNAT.
used in complex NAT deployment, has more granular control on NAT.
3. Virtual IP (DNAT), from Internet to internal server
When Central SNAT is disabled, VIP is used firewall policy.
When Central SNAT is enabled, real IP is used firewall policy.
When VIP is created for a server, outbound traffic initiated from the server will:
- if VIP has no port forwarding and Inbound FW rule referring VIP exists, and Firewall policy NAT using outgoing interface as SNAT, the VIP will be used as translated IP, but if Firewall policy NAT using a translation pool, the translation pool will be used as translated IP.
- if VIP has port forwarding, outgoing interface is used as translated IP.
Virtual IP is not Address object.
To enable central NAT, VIP and IP pool reference need be removed. Without removing it, enable Central SNAT in GUI doesn't give error, but couldn't turn on.
FortiGate # config system settings
FortiGate (settings) # set central-nat enable
Cannot enable central-nat with firewall policy using vip (id=2).
FortiGate (settings) #
After enable Central SNAT, two options are available:
1. Central SNAT
2. DNAT & Virtual IPs
4. By default, firewall address objects do not match VIPs.
deny source:all destination:all, this doesn't deny access to a VIP.
The default can be changed in CLI for the specific deny policy
config firewall policy
edit <policy ID>
set match-vip enable
end
or specify VIP as destination.
5. Session Helper
When more advanced application tracking and control is required, ALG can be used.
show system session-helper
6. Session Table
maynot have all sessions if FW has hardware acceleration.
Dashboard > FortiView Sessions
Default:
config system session-ttl
set default 3600
end
Troubleshooting CLIs:
get system session list
diag sys session filter (clear) ; can apply multiple filters
diag sys session list (clear)
Comments
Post a Comment