<?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 impact expected when adding tunnel gateway in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/impact-expected-when-adding-tunnel-gateway/m-p/2006017#M439495</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Charlie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically this command will force the ASA to send the VPN trafifc to 10.22.16.1 after it is decrypted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It depends on your bussiness needs, if the router 10.22.16.1 knows how to get to the all the required destinations it will be a good approch and will reduce the routing table size on the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 13 Jul 2012 16:43:10 GMT</pubDate>
    <dc:creator>Luis Silva Benavides</dc:creator>
    <dc:date>2012-07-13T16:43:10Z</dc:date>
    <item>
      <title>impact expected when adding tunnel gateway</title>
      <link>https://community.cisco.com/t5/network-security/impact-expected-when-adding-tunnel-gateway/m-p/2006016#M439493</link>
      <description>&lt;P&gt;What impact can we expect when we add a tunneled command to an existing firewall configuration?&lt;/P&gt;&lt;P&gt;I have attached my configuration to TAC case&amp;nbsp;&amp;nbsp;&amp;nbsp; #622427385&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; but if you advise I can share it with you?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route inside 0 0 10.22.16.1 tunneled&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Especially concerned about the 50 or so IPSec tunnels and the Employee SSL/IPSec. We have some Employee VPN routing issues with a company we just acquired and we must keep the VPN tunnel to then as a backup until a (backup) circuit is installed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This firewall is our VPN gateway and our default gateway to the Internet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps best practice is to have a tunnel gateway in the first place?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:30:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/impact-expected-when-adding-tunnel-gateway/m-p/2006016#M439493</guid>
      <dc:creator>charlie.ford</dc:creator>
      <dc:date>2019-03-11T23:30:49Z</dc:date>
    </item>
    <item>
      <title>impact expected when adding tunnel gateway</title>
      <link>https://community.cisco.com/t5/network-security/impact-expected-when-adding-tunnel-gateway/m-p/2006017#M439495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Charlie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically this command will force the ASA to send the VPN trafifc to 10.22.16.1 after it is decrypted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It depends on your bussiness needs, if the router 10.22.16.1 knows how to get to the all the required destinations it will be a good approch and will reduce the routing table size on the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Luis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jul 2012 16:43:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/impact-expected-when-adding-tunnel-gateway/m-p/2006017#M439495</guid>
      <dc:creator>Luis Silva Benavides</dc:creator>
      <dc:date>2012-07-13T16:43:10Z</dc:date>
    </item>
  </channel>
</rss>

