<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Abi Rendon - Sysadmin &#187; cisco</title>
	<atom:link href="http://www.abirendon.com/index.php/tag/cisco/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.abirendon.com</link>
	<description>The trials and tribulations of a web developer and sysadmin.</description>
	<lastBuildDate>Fri, 16 Apr 2010 18:51:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>VPN Tunnel Between Cisco ASA and Juniper SSG Firewalls</title>
		<link>http://www.abirendon.com/index.php/2009/11/03/vpn-tunnel-between-cisco-asa-and-juniper-ssg-firewalls/</link>
		<comments>http://www.abirendon.com/index.php/2009/11/03/vpn-tunnel-between-cisco-asa-and-juniper-ssg-firewalls/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 20:03:42 +0000</pubDate>
		<dc:creator>Abi Rendon</dc:creator>
				<category><![CDATA[Labor]]></category>
		<category><![CDATA[Sysadmin]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[juniper]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.abirendon.com/?p=205</guid>
		<description><![CDATA[Recently at work I was tasked with configuring a VPN tunnel between Cisco ASA 5505 to a Juniper SSG 320M. After hearing that it wasn&#8217;t compatible from many sources including our partners I just could not believe that this was the case, ipsec tunnels are a standard protocol and both Juniper and Cisco should be [...]]]></description>
			<content:encoded><![CDATA[<p>Recently at work I was tasked with configuring a VPN tunnel between Cisco ASA 5505 to a Juniper SSG 320M. After hearing that it wasn&#8217;t compatible from many sources including our partners I just could not believe that this was the case, ipsec tunnels are a standard protocol and both Juniper and Cisco should be compatible with ipsec.</p>
<p>After a day of google searches and troubleshooting I couldn&#8217;t find a proper solution that was easy and explained properly for my type of standard setup. Here is how I configured an ipsec VPN tunnel between the SSG and ASA.</p>
<p><strong>Cisco ASA 5505</strong></p>
<ul>
<li>IP: 1.1.1.1</li>
<li>Network: 192.168.1.0/24</li>
</ul>
<p><strong>Juniper SSG 320M</strong></p>
<ul>
<li>IP: 2.2.2.2</li>
<li>Network: 192.168.2.0/24</li>
</ul>
<blockquote><p>
192.168.1.0/24 < -> 1.1.1.1 < --VPN Tunnel--> 2.2.2.2 < -> 192.168.2.0/24
</p></blockquote>
<p>Here is the actual configuration including all the access list to allow all traffic through, you will probably want to lock this down as it will allow all traffic through.</p>
<p><strong>Cisco ASA 5505 Configuration</strong></p>
<blockquote><p>
object-group network local_cisco_network<br />
 network-object 192.168.1.0 255.255.255.0<br />
object-group network remote_juniper_network<br />
 network-object 192.168.2.0 255.255.255.0</p>
<p>access-list ciscovpn_nat_junipervpn extended permit ip object-group local_cisco_network object-group remote_juniper_network<br />
access-list ciscovpn_nat_junipervpn extended permit ip object-group remote_juniper_network object-group local_cisco_network</p>
<p>access-list ciscotojuniper_cryptomap extended permit ip 192.168.1.0 255.255.255.0 192.168.2.0 255.255.255.0</p>
<p>crypto map outside_map 1 match address ciscotojuniper_cryptomap<br />
crypto map outside_map 1 set pfs<br />
crypto map outside_map 1 set peer 2.2.2.2<br />
crypto map outside_map 1 set transform-set ESP-3DES-SHA</p>
<p>tunnel-group 2.2.2.2 type ipsec-l2l<br />
tunnel-group 2.2.2.2 ipsec-attributes<br />
 pre-shared-key <mypresharedkey><br />
</mypresharedkey></p></blockquote>
<p><strong>Juniper SSG 320M Configuration</strong></p>
<blockquote><p>
set address &#8220;Trust&#8221; &#8220;192.168.2.0/24&#8243; 10.248.1.0 255.255.255.0<br />
set address &#8220;Untrust&#8221; &#8220;192.168.1.0/24&#8243; 10.0.10.0 255.255.255.0</p>
<p>set ike gateway &#8220;1.1.1.1&#8243; address 1.1.1.1 Main outgoing-interface &#8220;ethernet0/1&#8243; preshare &#8220;<mypresharedkey>&#8221; proposal &#8220;pre-g2-3des-sha&#8221;</p>
<p>set vpn &#8220;1.1.1.1&#8243; gateway &#8220;1.1.1.1&#8243; no-replay tunnel idletime 0 proposal &#8220;g2-esp-3des-sha&#8221;<br />
set policy id 2 name &#8220;1.1.1.1&#8243; from &#8220;Trust&#8221; to &#8220;Untrust&#8221;  &#8220;192.168.2.0/24&#8243; &#8220;192.168.1.0/24&#8243; &#8220;ANY&#8221; tunnel vpn &#8220;1.1.1.1&#8243; id 0xa pair-policy 1<br />
set policy id 2<br />
exit<br />
set policy id 1 name &#8220;1.1.1.1&#8243; from &#8220;Untrust&#8221; to &#8220;Trust&#8221;  &#8220;192.168.1.0/24&#8243; &#8220;192.168.2.0/24&#8243; &#8220;ANY&#8221; tunnel vpn &#8220;1.1.1.1&#8243; id 0xa pair-policy 2<br />
set policy id 1<br />
exit<br />
</mypresharedkey></p></blockquote>
<p>This configuration will allow traffic from 192.168.1.0/24 to 192.168.2.0/24 and vice versa. On the Juniper side the name of the vpn and gateway I think are important otherwise the Phase 1 negotiation will not work. If I&#8217;ve missed something or if you don&#8217;t understand something please let me know.</p>
<p>I will probably need to configure this against a Cisco router in the near future so stay tuned for an update for the cisco side.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.abirendon.com/index.php/2009/11/03/vpn-tunnel-between-cisco-asa-and-juniper-ssg-firewalls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
