I'm new to the FortiGate routers (I've always been a Cisco guy), and had a hard time figuring out how to properly configure inbound and outbound static one-to-one NAT rules in the router. After doing a fair amount of searching in the FortiGate documentation and Googling, I found the information available online about this topic was either incomplete or out of date. So I thought I’d pass this along in case it is helpful to anyone who finds this tread in the future. I successfully did the below steps today on a FortiGate 60D running Firmware 5.2.7 build 718, but I’m pretty sure it will work the same on other similar models too. How to create an INBOUND static NAT rule:
[ol]
Navigate to: Policy & Objects > Objects > Virtual IPs[ol]Click the “Create New” buttonName = Anything you want, something descriptive. Remember this, you need it in Step #3.Comments = Optional. Anything you want.Interface = Select the correct external WAN interface that the public IP is connected toSource Address Filter = Defaults to unchecked, which is fine.External IP Address/Range = Just enter one *public* IP address. Put the same IP address in both fields (this means you’re only defining ONE IP address, instead of a RANGE or block of IPs)Mapped IP Address/Range = Just enter one *private* IP address. Put the same IP address in both fields (this means you’re only defining ONE IP address, instead of a RANGE or block of IPs)Port Forwarding = Optional.[ol]If you want to just have a 1-to-1 inbound static NAT map, leave this unchecked. Restrict and control access through IPv4 firewall policies.If you want to control or redirect specific ports, check this and then add custom rules as necessary.[/ol][/ol][/ol] Just because you create an Inbound NAT rule, it doesn’t mean that all outgoing traffic from that internal IP will be NAT’ed to that external Public IP. By default, the FortiGate will do outbound NAT to the external IP address only for *replies* sent by the internal server in response to requests that originated from *outside* the firewall. If you want to ensure that *all* traffic originating from the internal server is always NAT’ed to a specific external public IP address, then you must create a custom Outbound Static NAT IPv4 policy. If no custom outbound policy is created, then the outbound traffic that originates from the internal server will be NAT’ed to the router’s default overload one-to-many NAT public IP address. How to create an Outbound Static NAT rule:
[ol]Create a new address for the INTERNAL (private) device IP Address[ol]Navigate to: Policy & Objects > Objects > AddressesClick the “Create New” buttonName = Anything you want, something descriptive. Remember this, you need it in Step #3.Type = IP/NetmaskSubnet / IP Range = Just enter the single IP addressInterface = Defaults to “any”, which is fineShow in Address List = Defaults to “checked”, which is fineComments = Optional. Anything you want.[/ol]Create a new address for the EXTERNAL (public) device IP Pool[ol]Navigate to: Policy & Objects > Objects > IP PoolsClick the “Create New” buttonName = Anything you want, something descriptive. Remember this, you need it in Step #3.Comments = Optional. Anything you want.Type = Select “One-to-One”External IP Range = Just enter one public IP address. Put the same IP address in both fields (this means you’re only defining ONE IP address, instead of a RANGE or block of IPs)ARP Reply = Uncheck this (defaults to checked)[/ol]Create an outbound policy to connect the two IP addresses[ol]Navigate to: Policy & Objects > Policy > IPv4Click the “Create New” buttonIncoming Interface = internal (or whatever internal VLAN, interface, etc. you need to apply this to)Source Address = Select the name that you specified in Step #1Source User(s) = Normally you’ll want to just leave it blank/defaultSource Device Type = Normally you’ll want to just leave it blank/defaultOutgoing Interface = Select the correct external WAN interface that the public IP is connected toDestination Address = allSchedule = alwaysService = ALLAction = ACCEPTFirewall / Network Options[ol]Make sure NAT is turned “ON”Use Dynamic IP Pool = Select the name that you specified in Step #2[/ol]Make sure that “Enable this policy” is turned “ON”In the IPv4 Policy summary page, drag your new rule up to the top, above the generic “all – all – always – all” outbound allow rule. FortiGate applies policies from top to bottom.[/ol][/ol] NOTE: The FortiGate ARP tables last for quite a while, so if you are testing your outbound IP NAT to an external website (like www.whatismyip.com) then you need to completely close and restart your browser sessions, or reboot your test computer, or reboot the router, or wait for the router’s ARP tables to expire. I just found that visiting multiple different “show your IP” websites was easiest.
