<?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 Phase 2 issue-Peer Checkpoint in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-phase-2-issue-peer-checkpoint/m-p/325442#M82993</link>
    <description>&lt;P&gt;I have 15 proxy-ids in the&amp;nbsp; vpn tunnel whose peer is checkpoint firewall. Just one out of 15 usually remains really busy and lot of traffic get encap/decap on it. Remote users accessing resources within other 14 proxy-ids have absolutely no issues but they occasionally loose connectivity to those that are in the busiest proxy id and it recovers back automatically after 45-60mins.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My VPN settings are as below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Phase 2: No PFS, No lifesize , Lifetime:1hr&lt;/P&gt;&lt;P&gt;Phase 1: Group 5, Lefiteime:24hrs&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I started to assume it's because the bytes inside the proxy id is reaching the max limit and fails until a phase 2 rekey(1hr) happens. can someone let me know if I'm right in my assumption?&lt;/P&gt;&lt;P&gt;if it's so, I can think of 2 solutions:&lt;/P&gt;&lt;P&gt;1.enforce lisize settings to say 1000MB so tunnel rekeys automatically.&lt;/P&gt;&lt;P&gt;2. bifurcate the local network (/24) in the proxy id into smaller chunks( two /25s) .&lt;/P&gt;&lt;P&gt;Pls validate.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Thu, 30 Apr 2020 03:21:46 GMT</pubDate>
    <dc:creator>SThatipelly</dc:creator>
    <dc:date>2020-04-30T03:21:46Z</dc:date>
    <item>
      <title>IPSEC VPN Phase 2 issue-Peer Checkpoint</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-phase-2-issue-peer-checkpoint/m-p/325442#M82993</link>
      <description>&lt;P&gt;I have 15 proxy-ids in the&amp;nbsp; vpn tunnel whose peer is checkpoint firewall. Just one out of 15 usually remains really busy and lot of traffic get encap/decap on it. Remote users accessing resources within other 14 proxy-ids have absolutely no issues but they occasionally loose connectivity to those that are in the busiest proxy id and it recovers back automatically after 45-60mins.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My VPN settings are as below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Phase 2: No PFS, No lifesize , Lifetime:1hr&lt;/P&gt;&lt;P&gt;Phase 1: Group 5, Lefiteime:24hrs&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I started to assume it's because the bytes inside the proxy id is reaching the max limit and fails until a phase 2 rekey(1hr) happens. can someone let me know if I'm right in my assumption?&lt;/P&gt;&lt;P&gt;if it's so, I can think of 2 solutions:&lt;/P&gt;&lt;P&gt;1.enforce lisize settings to say 1000MB so tunnel rekeys automatically.&lt;/P&gt;&lt;P&gt;2. bifurcate the local network (/24) in the proxy id into smaller chunks( two /25s) .&lt;/P&gt;&lt;P&gt;Pls validate.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2020 03:21:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-phase-2-issue-peer-checkpoint/m-p/325442#M82993</guid>
      <dc:creator>SThatipelly</dc:creator>
      <dc:date>2020-04-30T03:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: IPSEC VPN Phase 2 issue-Peer Checkpoint</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-phase-2-issue-peer-checkpoint/m-p/325485#M82997</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/70284"&gt;@SThatipelly&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before making any other changes, i would recommend you to cross verify encryption domains at both ends and check if it matches. Make sure strictly same encryption domains are configured at both ends. Checkpoint is very naughty device in such cases.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mayur&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2020 10:29:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-phase-2-issue-peer-checkpoint/m-p/325485#M82997</guid>
      <dc:creator>SutareMayur</dc:creator>
      <dc:date>2020-04-30T10:29:40Z</dc:date>
    </item>
    <item>
      <title>Re: IPSEC VPN Phase 2 issue-Peer Checkpoint</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-phase-2-issue-peer-checkpoint/m-p/325511#M83009</link>
      <description>&lt;P&gt;yes, they match on both ends.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2020 12:39:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-phase-2-issue-peer-checkpoint/m-p/325511#M83009</guid>
      <dc:creator>SThatipelly</dc:creator>
      <dc:date>2020-04-30T12:39:59Z</dc:date>
    </item>
  </channel>
</rss>

