<?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: ASA IPSec tunnel in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867922#M28238</link>
    <description>&lt;P&gt;This could be many reasons, couple of things to check as below :&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Verify the other end has a route outside for the interesting traffic.&lt;/LI&gt;
&lt;LI&gt;Check that both VPN ACL’s are not mismatched.&lt;/LI&gt;
&lt;LI&gt;Double check NAT’s to make sure the traffic is not NAT’ing correctly.&lt;/LI&gt;
&lt;LI&gt;Is what you are trying to ping even responding back? Often what you’re sending traffic to is not able to accept or is not responding to this traffic. I prefer to put a packet capture on the remote end firewall to see if the traffic is coming back into that firewall.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;until we know&amp;nbsp;&amp;nbsp;how you configured your running config / nat / acl.&amp;nbsp; its hard to tell.&lt;/P&gt;
&lt;P&gt;post configuration of the bot the devices&amp;nbsp; - we asume that tunnel is up and running if so please post also below information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;show crypto ipsec sa (from both the side)&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jun 2019 07:30:26 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2019-06-05T07:30:26Z</dc:date>
    <item>
      <title>ASA IPSec tunnel</title>
      <link>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867910#M28237</link>
      <description>&lt;P&gt;Hi.. I have been facing weird issue where both end ASAs are encrypting packets for eachother end network subnet but not decrypting. Please suggest what could be the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ASA1 - 192.168.19.0/24&lt;/P&gt;&lt;P&gt;ASA2 - 192.168.22.0/24&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2019 07:07:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867910#M28237</guid>
      <dc:creator>Anukalp S</dc:creator>
      <dc:date>2019-06-05T07:07:52Z</dc:date>
    </item>
    <item>
      <title>Re: ASA IPSec tunnel</title>
      <link>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867922#M28238</link>
      <description>&lt;P&gt;This could be many reasons, couple of things to check as below :&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Verify the other end has a route outside for the interesting traffic.&lt;/LI&gt;
&lt;LI&gt;Check that both VPN ACL’s are not mismatched.&lt;/LI&gt;
&lt;LI&gt;Double check NAT’s to make sure the traffic is not NAT’ing correctly.&lt;/LI&gt;
&lt;LI&gt;Is what you are trying to ping even responding back? Often what you’re sending traffic to is not able to accept or is not responding to this traffic. I prefer to put a packet capture on the remote end firewall to see if the traffic is coming back into that firewall.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;until we know&amp;nbsp;&amp;nbsp;how you configured your running config / nat / acl.&amp;nbsp; its hard to tell.&lt;/P&gt;
&lt;P&gt;post configuration of the bot the devices&amp;nbsp; - we asume that tunnel is up and running if so please post also below information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;show crypto ipsec sa (from both the side)&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2019 07:30:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867922#M28238</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2019-06-05T07:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: ASA IPSec tunnel</title>
      <link>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867934#M28239</link>
      <description>Hi Balaji.. Actually ASA-2 has two subnets 192.168.22.0/24 &amp;amp; 192.168.21.0/24 which are in object-group. I am facing issue with subnet 192.168.22.0/24. while 192.168.21.0/24 work fine. Those two are in objectgroup in VPN ACL on both side of ASA. DOnt know why only 192.168.22.0/24 is not reachable. Will share logs.</description>
      <pubDate>Wed, 05 Jun 2019 07:43:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867934#M28239</guid>
      <dc:creator>Anukalp S</dc:creator>
      <dc:date>2019-06-05T07:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: ASA IPSec tunnel</title>
      <link>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867946#M28240</link>
      <description>Hi Balaji.. Also ASA-2 is running ver 8.2 , could you share No NAT config and ACL to apply into VPN.</description>
      <pubDate>Wed, 05 Jun 2019 08:09:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ipsec-tunnel/m-p/3867946#M28240</guid>
      <dc:creator>Anukalp S</dc:creator>
      <dc:date>2019-06-05T08:09:05Z</dc:date>
    </item>
  </channel>
</rss>

