<?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: IPSec VPN issue between Palo and MS Azure in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue-between-palo-and-ms-azure/m-p/98312#M44127</link>
    <description>&lt;P&gt;So, we know the IPSEC tunnell is using IKEv2, as is stated here.&lt;/P&gt;
&lt;P&gt;We also know that the error states "lacks KE Payload", So I looked for that.. and found this from:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://tools.ietf.org/html/rfc4306" target="_blank"&gt;https://tools.ietf.org/html/rfc4306&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE class="newpage"&gt;&lt;SPAN class="grey"&gt;&lt;A href="https://tools.ietf.org/html/rfc4306" target="_blank"&gt;RFC 4306&lt;/A&gt;                         IKEv2                     December 2005&lt;/SPAN&gt;


   A CHILD_SA is created by sending a CREATE_CHILD_SA request.  The
   CREATE_CHILD_SA request MAY optionally contain a KE payload for an
   additional Diffie-Hellman exchange to enable stronger guarantees of
   forward secrecy for the CHILD_SA.  The keying material for the
   CHILD_SA is a function of SK_d established during the establishment
   of the IKE_SA, the nonces exchanged during the CREATE_CHILD_SA
   exchange, and the Diffie-Hellman value (if KE payloads are included
   in the CREATE_CHILD_SA exchange).

   In the CHILD_SA created as part of the initial exchange, a second KE
   payload and nonce MUST NOT be sent.  The nonces from the initial
   exchange are used in computing the keys for the CHILD_SA.&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It talks about there being an Optional KE Payload. &amp;nbsp;.. but the KE is the Key Exchange info..&lt;/P&gt;
&lt;P&gt;And because the PAN is a "responder" in this IPSEC setup, it sounds like the&amp;nbsp;PAN side is looking for the KE packet, but is not seeing it, thus not bringing the tunnel up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would recommend talking with the Azure end, and seeing if they have this configured or not.&lt;/P&gt;
&lt;P&gt;At the same time, I would recommend you checking the Crypto settings and ensure that all values match for Phase 1 - IKE and Phse 2 - IPSEC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like after you confirm this info, that giving support here a call and they can continue working with you if you cannot get the tunnel working.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 18 Jul 2016 18:19:21 GMT</pubDate>
    <dc:creator>jdelio</dc:creator>
    <dc:date>2016-07-18T18:19:21Z</dc:date>
    <item>
      <title>IPSec VPN issue between Palo and MS Azure</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue-between-palo-and-ms-azure/m-p/98286#M44121</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Having problems with a site2site VPN connection on a palo alto firewall. It seems to randomly drop and stop working. Sometimes it will stay up for days then drop and other times it stays up for about an hour and then drop. I have followed various guides from palo and Microsoft (this is a VPN to MS Azure) on how to configure it and as I say it works but seemingly decides to drop for reasons unknown.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="VPN logs.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/4863iCFFC9D82295FCE00/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="VPN logs.png" alt="VPN logs.png" /&gt;&lt;/span&gt;﻿&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jul 2016 11:07:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue-between-palo-and-ms-azure/m-p/98286#M44121</guid>
      <dc:creator>TranceforLife</dc:creator>
      <dc:date>2016-07-18T11:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec VPN issue between Palo and MS Azure</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue-between-palo-and-ms-azure/m-p/98312#M44127</link>
      <description>&lt;P&gt;So, we know the IPSEC tunnell is using IKEv2, as is stated here.&lt;/P&gt;
&lt;P&gt;We also know that the error states "lacks KE Payload", So I looked for that.. and found this from:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://tools.ietf.org/html/rfc4306" target="_blank"&gt;https://tools.ietf.org/html/rfc4306&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE class="newpage"&gt;&lt;SPAN class="grey"&gt;&lt;A href="https://tools.ietf.org/html/rfc4306" target="_blank"&gt;RFC 4306&lt;/A&gt;                         IKEv2                     December 2005&lt;/SPAN&gt;


   A CHILD_SA is created by sending a CREATE_CHILD_SA request.  The
   CREATE_CHILD_SA request MAY optionally contain a KE payload for an
   additional Diffie-Hellman exchange to enable stronger guarantees of
   forward secrecy for the CHILD_SA.  The keying material for the
   CHILD_SA is a function of SK_d established during the establishment
   of the IKE_SA, the nonces exchanged during the CREATE_CHILD_SA
   exchange, and the Diffie-Hellman value (if KE payloads are included
   in the CREATE_CHILD_SA exchange).

   In the CHILD_SA created as part of the initial exchange, a second KE
   payload and nonce MUST NOT be sent.  The nonces from the initial
   exchange are used in computing the keys for the CHILD_SA.&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It talks about there being an Optional KE Payload. &amp;nbsp;.. but the KE is the Key Exchange info..&lt;/P&gt;
&lt;P&gt;And because the PAN is a "responder" in this IPSEC setup, it sounds like the&amp;nbsp;PAN side is looking for the KE packet, but is not seeing it, thus not bringing the tunnel up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would recommend talking with the Azure end, and seeing if they have this configured or not.&lt;/P&gt;
&lt;P&gt;At the same time, I would recommend you checking the Crypto settings and ensure that all values match for Phase 1 - IKE and Phse 2 - IPSEC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like after you confirm this info, that giving support here a call and they can continue working with you if you cannot get the tunnel working.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jul 2016 18:19:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue-between-palo-and-ms-azure/m-p/98312#M44127</guid>
      <dc:creator>jdelio</dc:creator>
      <dc:date>2016-07-18T18:19:21Z</dc:date>
    </item>
  </channel>
</rss>

