<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Re: [Config] Configuring More Than 1 VPN Tunnel (871w)&#x27; in forum &#x27;Cisco&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18687702</link>
<description></description>
<language>en</language>
<pubDate>Fri, 10 Feb 2012 00:05:23 EDT</pubDate>
<lastBuildDate>Fri, 10 Feb 2012 00:05:23 EDT</lastBuildDate>

<item>
<title>Re: [Config] Configuring More Than 1 VPN Tunnel (871w)</title>
<link>http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18702858</link>
<description><![CDATA[DocLarge posted : Thanks for the replies, gents...<br><br>As MSN said, we came to an understanding and all is running.  <br><br>Where MSN calls it "hub and spoke," it (hub and spoke) can also be explained as the "anchor" crypto map (connectivity originates from it).  Said differently, imagine the below map as my "first" crypto map:<br><br><U>crypto map<B><I>anchormap</B></I></U> 110 ipsec-isakmp<br><br>Every other crypto map created needs to include the above crypto map as the <B>"baseline"</B> crypto map for vpn connectivity to take place (example given):<br><BR><br><U>crypto map <B><I>anchormap</B></I></U> <B>111</B> ipsec-isakmp<br>set peer 22.33.44.55<br>match address 120 (Previously configured access-list)<br>etc...<br><BR><br><U>crypto map <B><I>anchormap</B></I></U> <B>112</B> ipsec-isakmp<br>set peer 11.33.55.44<br>match address 140 (Previously configured access-list)<br>etc...<br><BR><br><br>By approaching it from this standpoint, MSN helped bridge the gap :)<br><br>*Heh* it makes since now...<br><br>Jay]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18702858</guid>
<pubDate>Thu, 19 Jul 2007 08:39:48 EDT</pubDate>
</item>

<item>
<title>Re: [Config] Configuring More Than 1 VPN Tunnel (871w)</title>
<link>http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18702797</link>
<description><![CDATA[MSN posted : This was all good advice.  I talked to DocLarge last night and we sorted it out.  I teach this stuff for Cisco and he and I arrived at a good analogy:<br><br>Essentially the crypto map is a virtual IPsec interface.  All VPNs (both site-to-site and remote access) terminate on this virtual interface.  If you think of the crypto map as the hub in a hub-and-spoke arrangement with the spokes being the VPN peers this makes sense.  In the example above (thanks TomS_ !) the IPsec interface is identified as <I><B>"ipsec-maps"</I></B> The different VPN "spokes" are identified by their numbers.  For example, <I>"crypto map ipsec-maps 30 ipsec-isakmp"</I> creates "spoke" 30, and the different components of the IPsec policy for moving traffic to/from the peer are grouped by that number:<br><pre class="brush: text">crypto map ipsec-maps 30 ipsec-isakmp    &#012; description ** Site 2 **   &#012; set peer 3.3.3.3   &#012; set transform-set strong    &#012; set isakmp-profile site-2-prof   &#012; match address site-2-acl&#012; &#012;</pre><!--end code block--><br>The key, then, is remembering that you only have <B>one IPsec interface tied to any one physical interface.</B>  Once you have created this crypto map, you link it to a "reall" interface like this:<br><br>In TomS_ 's config it is done with this command:<br><pre class="brush: text">interface Dialer1&#012; crypto map ipsec-maps&#012; &#012;</pre><!--end code block--><br>/Eric<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18702797</guid>
<pubDate>Thu, 19 Jul 2007 08:22:57 EDT</pubDate>
</item>

<item>
<title>Re: [Config] Configuring More Than 1 VPN Tunnel (871w)</title>
<link>http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18702531</link>
<description><![CDATA[TomS_ posted : DocLarge: Heres a practical example of multiple VPNs. This is probably what youre looking for:<br><br><pre class="brush: text">crypto keyring site-1-keyring &#012;  pre-shared-key address 1.1.1.1 key abcd&#012;  pre-shared-key address 2.2.2.2 key abcd&#012;crypto keyring site-2-keyring &#012;  pre-shared-key address 3.3.3.3 key abcd&#012;!&#012;crypto isakmp policy 1&#012; encr 3des&#012; authentication pre-share&#012; group 2&#012;crypto isakmp profile site-1-a-prof&#012;   keyring site-1-keyring&#012;   match identity address 1.1.1.1 255.255.255.255 &#012;crypto isakmp profile site-1-b-prof&#012;   keyring site-1-keyring&#012;   match identity address 2.2.2.2 255.255.255.255 &#012;crypto isakmp profile site-2-prof&#012;   keyring site-2-keyring&#012;   match identity address 3.3.3.3 255.255.255.255 &#012;!&#012;!&#012;crypto ipsec transform-set strong ah-sha-hmac esp-3des &#012;!&#012;crypto map ipsec-maps 10 ipsec-isakmp &#012; description ** Site 1 VPN A **&#012; set peer 1.1.1.1&#012; set transform-set strong &#012; set isakmp-profile site-1-a-prof&#012; match address site-1-a-acl&#012;crypto map ipsec-maps 20 ipsec-isakmp &#012; description ** Site 1 VPN B **&#012; set peer 2.2.2.2&#012; set transform-set strong &#012; set isakmp-profile site-1-b-prof&#012; match address site-1-b-acl&#012;crypto map ipsec-maps 30 ipsec-isakmp &#012; description ** Site 2 **&#012; set peer 3.3.3.3&#012; set transform-set strong &#012; set isakmp-profile site-2-prof&#012; match address site-2-acl&#012;!&#012;interface Dialer1&#012; crypto map ipsec-maps&#012;!&#012;ip access-list extended site-1-a-acl&#012; permit ip 192.168.0.0 0.0.0.255 192.168.1.0 0.0.0.255&#012;ip access-list extended site-1-b-acl&#012; permit ip 192.168.0.0 0.0.0.255 192.168.2.0 0.0.0.255&#012;ip access-list extended site-2-acl&#012; permit ip 192.168.0.0 0.0.0.255 192.168.3.0 0.0.0.255&#012; &#012;</pre><!--end code block--><br>That should do it for you :-)<br><br><SMALL>I was feeling generous ;-)<br><br>Also, props go out to covenant for showing me how to do this quite a while ago :-)</SMALL><br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18702531</guid>
<pubDate>Thu, 19 Jul 2007 06:47:26 EDT</pubDate>
</item>

<item>
<title>Re: [Config] Configuring More Than 1 VPN Tunnel (871w)</title>
<link>http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18690115</link>
<description><![CDATA[aryoba posted : Multiple policy (for IPSec tunnel Phase 1 establishment) is used usually for encryption method compatibility. As example, one VPN device is VPN tunneling with another using 3DES and with the 3rd device using DES. If all of VPN devices are running the same encryption method, then a single isakmp policy should be sufficient.<br><br>On the other hand, multiple crypto map (for the IPSec tunnel Phase 2 establishment) is used specifically for each individual tunnel between two VPN devices.<br><br>Example<br><br>&raquo;<A HREF="http://www.cisco.com/en/US/products/sw/secursw/ps1018/products_configuration_example09186a008073e078.shtml" >www.cisco.com/en/US/products/sw/&middot;&middot;&middot;78.shtml</A><br><br>The 2nd crypto map for the 2nd tunnel could look something like this<br><br><pre class="brush: text">crypto map mymap 20 ipsec-isakmp&#012;set peer 10.0.2.2&#012;set transform-set myset&#012;match address 101&#012;!&#012;access-list 101 permit ip 10.1.1.0 0.0.0.255 172.16.3.0 0.0.0.255&#012; &#012;</pre><!--end code block--><br>assuming <br><br>* all VPN devices are using the same encryption method for both Phase 1 and Phase 2<br>* the 3rd VPN device is in front of 172.16.3.0/24 network]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18690115</guid>
<pubDate>Tue, 17 Jul 2007 15:38:57 EDT</pubDate>
</item>

<item>
<title>Re: [Config] Configuring More Than 1 VPN Tunnel (871w)</title>
<link>http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18689231</link>
<description><![CDATA[DocLarge posted : Thanks for the response, guys...<br><br>Tom, the tunnel is fine, it's working, so my direction on this hairy vpn ride is good.  :)  I'm just looking for the specific command required to allow more than one tunnel I've got separate policies (i.e., policy 10, policy 20) for both tunnels, I just need them to both run at the same time instead of just one at a time which is the issue at the moment. I'm ploughing through docs and haven't come across the command I need as of yet... <br><br><B>What is the specific syntax</B> I'm looking for on the link you provided, Aryoba, regarding increasing the vpn tunnels? <br><br>'Preciate the help.<br><br>Jay]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18689231</guid>
<pubDate>Tue, 17 Jul 2007 13:48:38 EDT</pubDate>
</item>

<item>
<title>Re: [Config] Configuring More Than 1 VPN Tunnel (871w)</title>
<link>http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18688065</link>
<description><![CDATA[aryoba posted : One of essential part of setting up multiple IPSec tunnels on a single Cisco router is the "crypto map" command. The command is followed by sequence number. This sequence number should be unique to specific remote VPN peer IP address and access list that control the traffic; as indicated by TomS_<br><br>Check out more info of the "crypto map" command on this link<br>&raquo;<A HREF="http://www.cisco.com/en/US/products/ps6350/products_command_reference_chapter09186a008044392c.html#wp1175082" >www.cisco.com/en/US/products/ps6&middot;&middot;&middot;p1175082</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18688065</guid>
<pubDate>Tue, 17 Jul 2007 11:32:29 EDT</pubDate>
</item>

<item>
<title>Re: [Config] Configuring More Than 1 VPN Tunnel (871w)</title>
<link>http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18687719</link>
<description><![CDATA[TomS_ posted : Increase the sequence number in the crypto map command to add additional VPNs.<br><br>Better yet, post your config so we can see what you are doing and point you in the right direction. Just make sure you obfuscate your keys and peer addresses.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Config-Configuring-More-Than-1-VPN-Tunnel-871w-18687719</guid>
<pubDate>Tue, 17 Jul 2007 10:32:38 EDT</pubDate>
</item>

<item>
<title>[Config] Configuring More Than 1 VPN Tunnel (871w)</title>
<link>http://www.dslreports.com/forum/Config-Configuring-More-Than-1-VPN-Tunnel-871w-18687702</link>
<description><![CDATA[DocLarge posted : Does anyon recall waht the command is that allows you to configure more than 1 IPSEC vpn site-to-site tunnel on the 871w?  I get the first tunnel up and running without difficulty, but when I put the second policy in and save the config, the first tunnel stops working...<br><br>Jay]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Config-Configuring-More-Than-1-VPN-Tunnel-871w-18687702</guid>
<pubDate>Tue, 17 Jul 2007 10:29:58 EDT</pubDate>
</item>

</channel>
</rss>

