FortiGate D-NAT with enabled Central-NAT

 Problem

When the Central NAT function is enabled, the behavior and configuration of the NAT changes.
Also this of the Destination NAT. 
The question is, how do I configure an inbound NAT when Central NAT is enabled?

Solution

When Central NAT is enabled, it is not necessary to add the VIP object into the firewall policy as destination address. This is a normal behavior due to the fact that, in a Central NAT status, the DNAT is injected to the kernel since the object is created into the Policy & Objects -> DNAT & Virtual IPs.

The only thing you have to do is to create a Virtual-IP object:

After that we need an appropriate Firewall Policy:

Which IP-Address as Destination is the right one?

Bevor FortiOS 6.4.3: -> Use the internal IP Address as destination (in my case: 172.16.51.12)
After FortiOS 6.4.3 -> Use the external IP Address as destination (in my case: 10.10.10.250)

What's happen with the 'match-vip-only' option?

Starting from 6.2 there is a new feature 'match-vip-only' to applied to a policy when Central NAT is enabled, CLI only (disabled by default).
If it is disabled, traffic from SDWAN to LAN with 172.16.51.12 (internal ip) or 10.10.10.250 (external ip) as destination will be allowed.


If 'match-vip-only' is enabled the policy will be matched only if a DNAT is applied before , so only traffic from SDWAN to LAN with destination 10.10.10.250 (external ip) will match the policy.
This behavior has changed starting from FortiOS 6.4.3 where match-vip-only is not configurable and there are no options to change this config.

Comments

Post a Comment

Popular posts from this blog

FortiGate BGP dual-home with multiple ISP

Image
Problem Design with two ISPs and an RIPE Routed public IP Ranges. How to solve, that the public Range is available over both ISPs but without asymetric Routing and ISP-1 is the primary. Solution FortiGate Basic BGP configuration First start with basic BGP configuration config router bgp set as 65301 set router-id 100.200.100.254 set keepalive-timer 45 set holdtime-timer 120 set bestpath-med-missing-as-worst enable set graceful-restart enable     config redistribution connected          set status enable     end end bestpath-med-missing-as-worst :  The route without MED is automaticly the worst destination. gracefule-restart :  Advertise reboots to neighbors so they don't see the router as offline, wait before declaring them offline, and how long to wait when they reboot before advertising updates. These commands apply to neighbors and are part of the BGP capabilities. This prevents unneeded routing updates. holdtime-timer: How long the router will wait for
Read more

FortiGate as DNS Server or DNS Proxy

Image
 Problem Especially in small networks, sometimes you do not have a dedicated DNS server available. For this purpose, the FortiGate can be used as DNS server. For larger installations, all DNS queries should be proxied for security reasons. The FortiGate can also help here. Solution A detail documentation about the DNS Server functionality is in the offical documentation:  Fortinet Doc In this post I would like to clearly present the most important functions and configuration types of the DNS function. DNS-Server In the following example the FortiGate act as DNS Server: Enable DNS Feature Enable the DNS Feature in the GUI: CLI command: config system settings     set gui-dns-database enable end Configure DNS Server Enable the DNS Feature on the interface on which DNS requests should be answered: Select Network Select DNS Servers Select the listen Interface Select the DNS Server Mode (see delecration below) The same on the CLI: config system dns-server     edit DMZ2          set mode recu
Read more

FortiGate and Windows L2TP / IPsec with Split Tunneling

 Problem In some scenarios, the user does not want to install an additional VPN client on their device, but use the already built-in one from Windows. Thus, the FortiGate SSL VPN solution cannot be used. So that only systems behind the FortiGate unit are accessible, a split tunnel connection must be established. Solution The L2TP over IPsec VPN solution is used for this purpose. First an IPsec connection is established between the client and FortiGate and then an L2TP connection is established. This is authenticated via a PSK and L2TP via username and password. The following steps are necessary to implement this solution. IPsec Connection config vpn ipsec phase1-interface edit "Dialup" set type dynamic set interface " wan " set peertype any set net-device disable set proposal aes256-md5 3des-sha1 aes192-sha1 set dhgrp 2 set wizard-type dialup-windows set psksecret **** next end config vpn ipsec pha
Read more