<?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 IPSec VPN with Cisco ASA behind NAT in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-with-cisco-asa-behind-nat/m-p/50883#M37448</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm trying to establish a ipsec VPN tunnel with a Cisco ASA with a peer address behind a NAT fw.&amp;nbsp; We have checked all ike and ipsec crypto parameters, and successfully established vpn with Cisco ASA before.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase 1 is failing due to time out, and we get a log entry that indicate that the private peer address (which is behind NAT) is "visiblie" to the PAN local peer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="screendump.PNG.png" class="jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/8115_screendump.PNG.png" style="width: 620px; height: 80px;" /&gt;&lt;/P&gt;&lt;P&gt;Black strike out is the local gw ip public address, and red is the public peer (NAT) ip &lt;/P&gt;&lt;P&gt;The address in the top event is the private GW address that is behind NAT.&amp;nbsp; I did not expect the PAN box on our side to see this address.&lt;/P&gt;&lt;P&gt;NAT Traversal is on, on both sides.&lt;/P&gt;&lt;P&gt;This is how Phase-1 times out with the following log entries (never mind the time stamp, I did not clip the corresponding log entries)&lt;/P&gt;&lt;P&gt;&lt;IMG alt="screenshot2.PNG.png" class="jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/8116_screenshot2.PNG.png" style="width: 620px; height: 83px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have monitored the mp-log/ikemgr.log with debug on, but get no hints as to why this is failing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate any help resolving this issue&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Sep 2013 11:09:22 GMT</pubDate>
    <dc:creator>arnljot</dc:creator>
    <dc:date>2013-09-09T11:09:22Z</dc:date>
    <item>
      <title>IPSec VPN with Cisco ASA behind NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-with-cisco-asa-behind-nat/m-p/50883#M37448</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm trying to establish a ipsec VPN tunnel with a Cisco ASA with a peer address behind a NAT fw.&amp;nbsp; We have checked all ike and ipsec crypto parameters, and successfully established vpn with Cisco ASA before.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase 1 is failing due to time out, and we get a log entry that indicate that the private peer address (which is behind NAT) is "visiblie" to the PAN local peer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="screendump.PNG.png" class="jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/8115_screendump.PNG.png" style="width: 620px; height: 80px;" /&gt;&lt;/P&gt;&lt;P&gt;Black strike out is the local gw ip public address, and red is the public peer (NAT) ip &lt;/P&gt;&lt;P&gt;The address in the top event is the private GW address that is behind NAT.&amp;nbsp; I did not expect the PAN box on our side to see this address.&lt;/P&gt;&lt;P&gt;NAT Traversal is on, on both sides.&lt;/P&gt;&lt;P&gt;This is how Phase-1 times out with the following log entries (never mind the time stamp, I did not clip the corresponding log entries)&lt;/P&gt;&lt;P&gt;&lt;IMG alt="screenshot2.PNG.png" class="jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/8116_screenshot2.PNG.png" style="width: 620px; height: 83px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have monitored the mp-log/ikemgr.log with debug on, but get no hints as to why this is failing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate any help resolving this issue&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Sep 2013 11:09:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-with-cisco-asa-behind-nat/m-p/50883#M37448</guid>
      <dc:creator>arnljot</dc:creator>
      <dc:date>2013-09-09T11:09:22Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec VPN with Cisco ASA behind NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-with-cisco-asa-behind-nat/m-p/50884#M37449</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you try to set &lt;/P&gt;&lt;P&gt;Local ID&amp;nbsp; on ASA =Public IP of the NAT device &amp;amp;&amp;amp;&lt;/P&gt;&lt;P&gt;Peer Identification on PA firewall = Public IP of the NAT device under ike-gateway on PA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Sep 2013 12:19:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-with-cisco-asa-behind-nat/m-p/50884#M37449</guid>
      <dc:creator>UhMayYeah</dc:creator>
      <dc:date>2013-09-09T12:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec VPN with Cisco ASA behind NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-with-cisco-asa-behind-nat/m-p/50885#M37450</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This was a bug in PANOS.&amp;nbsp; Probably some memory leak.&amp;nbsp; A reboot solved the issue, and I believe this problem has been solved in a later release.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2015 16:43:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-with-cisco-asa-behind-nat/m-p/50885#M37450</guid>
      <dc:creator>arnljot</dc:creator>
      <dc:date>2015-06-11T16:43:39Z</dc:date>
    </item>
  </channel>
</rss>

