<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Fortigate Static NAT Configuration</title>
	<atom:link href="http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/</link>
	<description>My Network Playground</description>
	<lastBuildDate>Mon, 06 Sep 2010 01:22:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Roel</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-141</link>
		<dc:creator>Roel</dc:creator>
		<pubDate>Fri, 23 Jul 2010 12:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-141</guid>
		<description>Excellent short guide, works like a charm! Thanks!</description>
		<content:encoded><![CDATA[<p>Excellent short guide, works like a charm! Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-133</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 22 Apr 2010 16:15:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-133</guid>
		<description>&lt;a href=&quot;#comment-128&quot; rel=&quot;nofollow&quot;&gt;@WalkerBoh42 &lt;/a&gt; 
I&#039;m not familiar with the clustering features on the Fortigate units. I am actually in the process of migrating from a single Fortigate 800 to a pair of Juniper SRX240&#039;s.

&lt;a href=&quot;#comment-131&quot; rel=&quot;nofollow&quot;&gt;@Paul Kuhne &lt;/a&gt; 
On the Fortigate 800 you can add multiple IP addresses to an interface. This is done under the System -&gt; Network -&gt; Interface menu. Once you select the interface you wish to configure (probably External), look for the &quot;Secondary IP Address&quot; option. From there you add the needed IP addresses and choose to enable remote administration (HTTP/HTTPS) on one or more of the IP addresses. Note, this may not be available on the 80c.

Using different IPs based on the external service the workstation is attempting to use is a bit tricky. Most likely you will have to get creative with the firewall policies, however you may not be able to accomplish this with the 80c.</description>
		<content:encoded><![CDATA[<p><a href="#comment-128" rel="nofollow">@WalkerBoh42 </a><br />
I&#8217;m not familiar with the clustering features on the Fortigate units. I am actually in the process of migrating from a single Fortigate 800 to a pair of Juniper SRX240&#8242;s.</p>
<p><a href="#comment-131" rel="nofollow">@Paul Kuhne </a><br />
On the Fortigate 800 you can add multiple IP addresses to an interface. This is done under the System -&gt; Network -&gt; Interface menu. Once you select the interface you wish to configure (probably External), look for the &#8220;Secondary IP Address&#8221; option. From there you add the needed IP addresses and choose to enable remote administration (HTTP/HTTPS) on one or more of the IP addresses. Note, this may not be available on the 80c.</p>
<p>Using different IPs based on the external service the workstation is attempting to use is a bit tricky. Most likely you will have to get creative with the firewall policies, however you may not be able to accomplish this with the 80c.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Kuhne</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-131</link>
		<dc:creator>Paul Kuhne</dc:creator>
		<pubDate>Wed, 07 Apr 2010 08:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-131</guid>
		<description>I have an issue with UPC business; we are using a fortigate 80c. UPC provided us with 4 fixed IP-adresses. However, I could only use 1 on the external interface wan-1, and all mapping with NAT. What I would like to do is use different IP&#039;s for HTTP, FTP-access, Audio-streams, Remote administration. So every use it&#039;s own IP xxx.xxx.xxx.250-254. I can&#039;t get all 4 IP&#039;s been seen on the outside (WAN). Can you help me out ?</description>
		<content:encoded><![CDATA[<p>I have an issue with UPC business; we are using a fortigate 80c. UPC provided us with 4 fixed IP-adresses. However, I could only use 1 on the external interface wan-1, and all mapping with NAT. What I would like to do is use different IP&#8217;s for HTTP, FTP-access, Audio-streams, Remote administration. So every use it&#8217;s own IP xxx.xxx.xxx.250-254. I can&#8217;t get all 4 IP&#8217;s been seen on the outside (WAN). Can you help me out ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WalkerBoh42</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-128</link>
		<dc:creator>WalkerBoh42</dc:creator>
		<pubDate>Sun, 14 Feb 2010 12:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-128</guid>
		<description>Thanks for the reply guys. All working perfectly now.

Next question (might not be the right thread for this). I have setup 4 blades into an ELBC cluster. I need to be able enable RIP. I had RIP working on the HA cluster, but when I changed it to the ELBC it got broken!!

Any suggestions.

Thanks</description>
		<content:encoded><![CDATA[<p>Thanks for the reply guys. All working perfectly now.</p>
<p>Next question (might not be the right thread for this). I have setup 4 blades into an ELBC cluster. I need to be able enable RIP. I had RIP working on the HA cluster, but when I changed it to the ELBC it got broken!!</p>
<p>Any suggestions.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-127</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 07 Feb 2010 14:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-127</guid>
		<description>&lt;a href=&quot;#comment-123&quot; rel=&quot;nofollow&quot;&gt;@cdm&lt;/a&gt; 

You will want to have a look at port forwarding as well as the one to many NAT feature. I have not played with these features, so I am unsure of they will accomplish your goal.</description>
		<content:encoded><![CDATA[<p><a href="#comment-123" rel="nofollow">@cdm</a> </p>
<p>You will want to have a look at port forwarding as well as the one to many NAT feature. I have not played with these features, so I am unsure of they will accomplish your goal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-126</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 07 Feb 2010 13:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-126</guid>
		<description>&lt;a href=&quot;#comment-125&quot; rel=&quot;nofollow&quot;&gt;@Walkerboh42&lt;/a&gt; 

Have a look at my &lt;a&gt;Fortigate NAT Overload (PAT)&lt;/a&gt; article. You can use the PAT address that is assigned to your external interface for any other traffic that does not need a dedicated IP (such as DNS forwarding).

Juts be sure you create a policy that allow DNS queries from your internal server to get to the external DNS servers that you are using. I use this method with our Fortigate and it works well.</description>
		<content:encoded><![CDATA[<p><a href="#comment-125" rel="nofollow">@Walkerboh42</a> </p>
<p>Have a look at my <a>Fortigate NAT Overload (PAT)</a> article. You can use the PAT address that is assigned to your external interface for any other traffic that does not need a dedicated IP (such as DNS forwarding).</p>
<p>Juts be sure you create a policy that allow DNS queries from your internal server to get to the external DNS servers that you are using. I use this method with our Fortigate and it works well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walkerboh42</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-125</link>
		<dc:creator>Walkerboh42</dc:creator>
		<pubDate>Sun, 07 Feb 2010 11:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-125</guid>
		<description>Hi

Thanks for the easy to follow steps. I have just one question. How do I configure the VIP for traffic that is initiated inside the private network? DNS for example needs to forward to a server in another network on a natted address.

Thanks</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>Thanks for the easy to follow steps. I have just one question. How do I configure the VIP for traffic that is initiated inside the private network? DNS for example needs to forward to a server in another network on a natted address.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cdm</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-123</link>
		<dc:creator>cdm</dc:creator>
		<pubDate>Tue, 26 Jan 2010 03:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-123</guid>
		<description>Not to be late to the party here - but great article - very easy to follow..

My issue is that I am trying to get one WAN address to forward traffic to multiple LAN addresses..  

So - 4.2.2.2 will have to ports open 80 and 25..  80 needs to route to 192.168.0.5 and 25 needs to route to 192.168.0.10..  

Thanks in advance..</description>
		<content:encoded><![CDATA[<p>Not to be late to the party here &#8211; but great article &#8211; very easy to follow..</p>
<p>My issue is that I am trying to get one WAN address to forward traffic to multiple LAN addresses..  </p>
<p>So &#8211; 4.2.2.2 will have to ports open 80 and 25..  80 needs to route to 192.168.0.5 and 25 needs to route to 192.168.0.10..  </p>
<p>Thanks in advance..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-110</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 03 Sep 2009 23:29:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-110</guid>
		<description>&lt;a href=&quot;#comment-109&quot; rel=&quot;nofollow&quot;&gt;@Dfine&lt;/a&gt; 
I&#039;m not near a computer right now, so i can&#039;t reference a specific page in the Fortigate Administrators manual. However, there is a way to assign multiple IP addresses to an interface. I believe that is what you will want to do in order to perform NAT for multiple IP ranges.

Also, make sure your Fortigate has a route for the other IP range pointing out your external interface.</description>
		<content:encoded><![CDATA[<p><a href="#comment-109" rel="nofollow">@Dfine</a><br />
I&#8217;m not near a computer right now, so i can&#8217;t reference a specific page in the Fortigate Administrators manual. However, there is a way to assign multiple IP addresses to an interface. I believe that is what you will want to do in order to perform NAT for multiple IP ranges.</p>
<p>Also, make sure your Fortigate has a route for the other IP range pointing out your external interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dfine</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-109</link>
		<dc:creator>Dfine</dc:creator>
		<pubDate>Thu, 03 Sep 2009 15:57:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-109</guid>
		<description>Hi Chris,

This seems to work fine if I use an ip that is on the same range as my external interface - however I have a need to NAT another range that is routed to my Fortigate by the ISP - and this seems to not work - any ideas ?

(for example if my external is 192.168.1.1/24, I need to NAT 192.168.2.1/24 - this 192.168.2.1/24 is routed to the 192.168.1.1 and I see the traffic hitting the external interface but it never gets forwarded to the inside)

Look forward to your comment.

Thanks in advance.</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>This seems to work fine if I use an ip that is on the same range as my external interface &#8211; however I have a need to NAT another range that is routed to my Fortigate by the ISP &#8211; and this seems to not work &#8211; any ideas ?</p>
<p>(for example if my external is 192.168.1.1/24, I need to NAT 192.168.2.1/24 &#8211; this 192.168.2.1/24 is routed to the 192.168.1.1 and I see the traffic hitting the external interface but it never gets forwarded to the inside)</p>
<p>Look forward to your comment.</p>
<p>Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-107</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 04 Aug 2009 18:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-107</guid>
		<description>&lt;a href=&quot;#comment-105&quot; rel=&quot;nofollow&quot;&gt;@Doc &lt;/a&gt; 

The screen shots used in both articles are from a Fortigate 800 using the &quot;FGT_800-v400-build0099-FORTINET.out&quot; image. From the time stamp of this file on Fortigate&#039;s FTP site, this image was uploaded on April of 2009. So at the time I wrote this article, the firmware on the Fortigate was only 2 months old).

Thanks for reading my blog!</description>
		<content:encoded><![CDATA[<p><a href="#comment-105" rel="nofollow">@Doc </a> </p>
<p>The screen shots used in both articles are from a Fortigate 800 using the &#8220;FGT_800-v400-build0099-FORTINET.out&#8221; image. From the time stamp of this file on Fortigate&#8217;s FTP site, this image was uploaded on April of 2009. So at the time I wrote this article, the firmware on the Fortigate was only 2 months old).</p>
<p>Thanks for reading my blog!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramkumar C</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-106</link>
		<dc:creator>Ramkumar C</dc:creator>
		<pubDate>Fri, 31 Jul 2009 06:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-106</guid>
		<description>This is very good guide. Its working for good.thanks a lot</description>
		<content:encoded><![CDATA[<p>This is very good guide. Its working for good.thanks a lot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc</title>
		<link>http://www.hiddenone.net/firewalls/fortigate-static-nat-configuration/comment-page-1/#comment-105</link>
		<dc:creator>Doc</dc:creator>
		<pubDate>Fri, 31 Jul 2009 03:18:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenone.net/?p=150#comment-105</guid>
		<description>Would help if you updated your firmware once and a while to get current with the program of options that are current and not 5+ years old!

Get with the program will ya.

5 Years real world experienced, certified Fortigate Specialist.

Doc</description>
		<content:encoded><![CDATA[<p>Would help if you updated your firmware once and a while to get current with the program of options that are current and not 5+ years old!</p>
<p>Get with the program will ya.</p>
<p>5 Years real world experienced, certified Fortigate Specialist.</p>
<p>Doc</p>
]]></content:encoded>
	</item>
</channel>
</rss>
