<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: VPNs in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vpns/m-p/230458#M1060331</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm currently running OSPF on some MGRE crypto networks, and there's a fair bit on the Cisco web site about those sort of features.  As far as load balancing is concerned, my advice would be to use extreme caution as the delay on the VPN will also be affected by crypto performance as well as all the other normal factors, so if you try per-packet things will probably get nasty.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Jan 2004 05:15:33 GMT</pubDate>
    <dc:creator>gmiiller</dc:creator>
    <dc:date>2004-01-19T05:15:33Z</dc:date>
    <item>
      <title>VPNs</title>
      <link>https://community.cisco.com/t5/network-security/vpns/m-p/230456#M1060326</link>
      <description>&lt;P&gt;EIGRP and VPNs.&lt;/P&gt;&lt;P&gt;We have four tunnels.  A connects to our internal network.  B, C and D connect to a VPN.  We want to load balance EIGRP over each of the four paths.  How can we do it?&lt;/P&gt;&lt;P&gt;Also, if A fails we want B, C and D to work.  If B, C and D fail we ant A to work.&lt;/P&gt;&lt;P&gt;What solution mix could help?  Can we consider using variance, offset lists, other?  Please send config samples.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:perronta@hotmail.com" target="_blank"&gt;perronta@hotmail.com&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:10:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpns/m-p/230456#M1060326</guid>
      <dc:creator>tperron</dc:creator>
      <dc:date>2020-02-21T07:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: VPNs</title>
      <link>https://community.cisco.com/t5/network-security/vpns/m-p/230457#M1060329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can define multiple remote peers using crypto maps to allow for load sharing. Should a peer fails, there will be an other protected path. If a transmission attempt fails with the first peer, IKE tries the next peer on the crypto list. The crypto map parameters must be compatible with other peers. If you are not sure how to configure the crypto map parameters, use dynamic crypto maps. This is well described at:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113t/113t_3/ipsec.htm#32276" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113t/113t_3/ipsec.htm#32276&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Dec 2003 16:34:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpns/m-p/230457#M1060329</guid>
      <dc:creator>smalkeric</dc:creator>
      <dc:date>2003-12-29T16:34:13Z</dc:date>
    </item>
    <item>
      <title>Re: VPNs</title>
      <link>https://community.cisco.com/t5/network-security/vpns/m-p/230458#M1060331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm currently running OSPF on some MGRE crypto networks, and there's a fair bit on the Cisco web site about those sort of features.  As far as load balancing is concerned, my advice would be to use extreme caution as the delay on the VPN will also be affected by crypto performance as well as all the other normal factors, so if you try per-packet things will probably get nasty.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jan 2004 05:15:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpns/m-p/230458#M1060331</guid>
      <dc:creator>gmiiller</dc:creator>
      <dc:date>2004-01-19T05:15:33Z</dc:date>
    </item>
  </channel>
</rss>

