<?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: No proposal chosen ikev1 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262647#M126909</link>
    <description>&lt;P&gt;that is very unfortunate!&lt;/P&gt;
&lt;P&gt;I've heard of this issue before on PAN-OS 12, maybe a bug or a QA oversight due to the sheer age of these protocols. You could open up a support case to have that investigated, but i would recommend trying to upgrade the crypto profile.&lt;/P&gt;</description>
    <pubDate>Mon, 24 Aug 2026 11:38:47 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2026-08-24T11:38:47Z</dc:date>
    <item>
      <title>No proposal chosen ikev1</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262544#M126904</link>
      <description>&lt;P&gt;After upgrading to panos preffered version 12.1.7-h3 my ikev1 ipsec tunnel with ipsec crypto md5,3des,nopfs is not coming up , knowing that ike phase 1 is successful but ike phase 2 is giving no proposal chosen error , the algorithms matches the other peer and i tried downgrading the tunnel came up, i would appreciate any help&lt;/P&gt;</description>
      <pubDate>Sun, 23 Aug 2026 10:43:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262544#M126904</guid>
      <dc:creator>Esameldin</dc:creator>
      <dc:date>2026-08-23T10:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: No proposal chosen ikev1</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262639#M126907</link>
      <description>&lt;P&gt;Is there a reason you're using these deprecated protocols?&lt;/P&gt;
&lt;P&gt;Unless your peer device is something ancient, it would be better to switch to modern crypto profiles and see if that not automatically fixes your issue&lt;/P&gt;</description>
      <pubDate>Mon, 24 Aug 2026 11:08:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262639#M126907</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2026-08-24T11:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: No proposal chosen ikev1</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262643#M126908</link>
      <description>&lt;P&gt;We are forced to use these old algorithms as the peer seems like a very old device. cisco i believe.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Aug 2026 11:19:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262643#M126908</guid>
      <dc:creator>Esameldin</dc:creator>
      <dc:date>2026-08-24T11:19:56Z</dc:date>
    </item>
    <item>
      <title>Re: No proposal chosen ikev1</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262647#M126909</link>
      <description>&lt;P&gt;that is very unfortunate!&lt;/P&gt;
&lt;P&gt;I've heard of this issue before on PAN-OS 12, maybe a bug or a QA oversight due to the sheer age of these protocols. You could open up a support case to have that investigated, but i would recommend trying to upgrade the crypto profile.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Aug 2026 11:38:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/no-proposal-chosen-ikev1/m-p/1262647#M126909</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2026-08-24T11:38:47Z</dc:date>
    </item>
  </channel>
</rss>

