<?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 Issue with the VPN between AWS and Checkpoint in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Issue-with-the-VPN-between-AWS-and-Checkpoint/m-p/34038#M7168</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are facing a weird issue with the VPN built between Checkpoint and the AWS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue started recently and the VPN was built long back, no changes in the environment made recently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When checked the vpn debug ikeon in ikeview, we can see that the Phase 2 is negotiating with the peer IPs rather than negotiating with the 0.0.0.0/0.0.0.0. This is only when the issue occurs. As a temporary fix we clear the SAs each time the issue occur which helps the Phase 2 negotiate with 0.0.0.0/0.0.0.0 and the tunnel works as normal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please suggest us a solution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Feb 2019 09:01:29 GMT</pubDate>
    <dc:creator>Sanjay_S</dc:creator>
    <dc:date>2019-02-15T09:01:29Z</dc:date>
    <item>
      <title>Issue with the VPN between AWS and Checkpoint</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Issue-with-the-VPN-between-AWS-and-Checkpoint/m-p/34038#M7168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are facing a weird issue with the VPN built between Checkpoint and the AWS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue started recently and the VPN was built long back, no changes in the environment made recently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When checked the vpn debug ikeon in ikeview, we can see that the Phase 2 is negotiating with the peer IPs rather than negotiating with the 0.0.0.0/0.0.0.0. This is only when the issue occurs. As a temporary fix we clear the SAs each time the issue occur which helps the Phase 2 negotiate with 0.0.0.0/0.0.0.0 and the tunnel works as normal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please suggest us a solution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2019 09:01:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Issue-with-the-VPN-between-AWS-and-Checkpoint/m-p/34038#M7168</guid>
      <dc:creator>Sanjay_S</dc:creator>
      <dc:date>2019-02-15T09:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with the VPN between AWS and Checkpoint</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Issue-with-the-VPN-between-AWS-and-Checkpoint/m-p/34039#M7169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I recommend engaging with the TAC so&amp;nbsp;proper troubleshooting can be done.&lt;/P&gt;&lt;P&gt;Also possible this will be fixed by applying a recent JHF or similar, but don't if that's relevant since you supplied no version/JHF information in your message.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.checkpoint.com/message/39214"&gt;How To Open a Case with TAC and/or Account Services&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2019 23:45:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Issue-with-the-VPN-between-AWS-and-Checkpoint/m-p/34039#M7169</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-02-15T23:45:42Z</dc:date>
    </item>
  </channel>
</rss>

