 




<?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: VPN between DLink and Fortinet</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/vpn-between-dlink-and-fortinet/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/vpn-between-dlink-and-fortinet/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 01:41:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: mnemonyss</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/vpn-between-dlink-and-fortinet/#comment-50607</link>
		<dc:creator>mnemonyss</dc:creator>
		<pubDate>Wed, 14 Nov 2007 19:23:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-50607</guid>
		<description><![CDATA[You should decide on your encryption level (DES/3DES/AES) depending on what each of these support. They should both have a user interface to plug in these values to. Possibly even via command line.

Remember for a site to site (as site to site requires an endpoint on each end which is usually a router or firewall) the configuration must match on both sides except for peer ip information will be flipped.

For instance if your Phase 1 is:

3DES
SHA1
DH 2
8600

and Phase 2 is

3DES
SHA1
no PFS

Then it must be the set this way on both ends of the vpn on each device.

You&#039;ll also need to ensure the ACL&#039;s match (the rules to allow traffic to your internal network from the remote network on each side)

I hope this gives you some direction, I can not vouch for compatibility of each unit as I am a Cisco ASA/PIX user, tho I have configured VPN&#039;s through Watchguard&#039;s, Firebox&#039;s, Checkpoint&#039;s, and Netscreen&#039;s. Ipsec VPN&#039;s are pretty much universal everywhere if they are site to site. Dynamic Ipsec VPN&#039;s will be a little different. You&#039;ll need to determine which VPN your firewall/router support.]]></description>
		<content:encoded><![CDATA[<p>You should decide on your encryption level (DES/3DES/AES) depending on what each of these support. They should both have a user interface to plug in these values to. Possibly even via command line.</p>
<p>Remember for a site to site (as site to site requires an endpoint on each end which is usually a router or firewall) the configuration must match on both sides except for peer ip information will be flipped.</p>
<p>For instance if your Phase 1 is:</p>
<p>3DES<br />
SHA1<br />
DH 2<br />
8600</p>
<p>and Phase 2 is</p>
<p>3DES<br />
SHA1<br />
no PFS</p>
<p>Then it must be the set this way on both ends of the vpn on each device.</p>
<p>You&#8217;ll also need to ensure the ACL&#8217;s match (the rules to allow traffic to your internal network from the remote network on each side)</p>
<p>I hope this gives you some direction, I can not vouch for compatibility of each unit as I am a Cisco ASA/PIX user, tho I have configured VPN&#8217;s through Watchguard&#8217;s, Firebox&#8217;s, Checkpoint&#8217;s, and Netscreen&#8217;s. Ipsec VPN&#8217;s are pretty much universal everywhere if they are site to site. Dynamic Ipsec VPN&#8217;s will be a little different. You&#8217;ll need to determine which VPN your firewall/router support.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.035 seconds using memcached
Object Caching 267/273 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-23 04:20:02 -->