<?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 Tunnel to AWS VPC - Sporadically drops after Policy Install in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-Tunnel-to-AWS-VPC-Sporadically-drops-after-Policy-Install/m-p/30488#M2422</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've got a strange, lingering issue. Our R77.30 Gateway has quite a few IPSec Site-to-Site VPN tunnels terminating on it, and a few of them are on AWS. I've played with the settings in the IPSec community and encryption on several of them and still experience the same behavior.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The tunnel can be up, operating normally, passing traffic at an acceptable rate.&lt;/P&gt;&lt;P&gt;2. After I install policy to the gateway, *sometimes*, traffic will no longer traverse the tunnel.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;2a. This is random - I would say 10% of the time, it will happen.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;2b. Pushing policy again fixes it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Disclaimer - I set up the VPN like i've always done with other sites (external site using ASA, Palo, etc) - using an interoperable device/PSK/IPSec Community. I just recently found this sk:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk100726" title="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk100726"&gt;How to configure IPsec VPN tunnel between Check Point Security Gateway and Amazon Web Services VPC using static routes&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could not using VTI's be my issue? I'll be honest, i'm not familiar with VTI's or MSS clamping or dead peer detection.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Feb 2018 17:58:54 GMT</pubDate>
    <dc:creator>Saul_Schwartz</dc:creator>
    <dc:date>2018-02-16T17:58:54Z</dc:date>
    <item>
      <title>IPSec Tunnel to AWS VPC - Sporadically drops after Policy Install</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-Tunnel-to-AWS-VPC-Sporadically-drops-after-Policy-Install/m-p/30488#M2422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've got a strange, lingering issue. Our R77.30 Gateway has quite a few IPSec Site-to-Site VPN tunnels terminating on it, and a few of them are on AWS. I've played with the settings in the IPSec community and encryption on several of them and still experience the same behavior.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The tunnel can be up, operating normally, passing traffic at an acceptable rate.&lt;/P&gt;&lt;P&gt;2. After I install policy to the gateway, *sometimes*, traffic will no longer traverse the tunnel.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;2a. This is random - I would say 10% of the time, it will happen.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;2b. Pushing policy again fixes it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Disclaimer - I set up the VPN like i've always done with other sites (external site using ASA, Palo, etc) - using an interoperable device/PSK/IPSec Community. I just recently found this sk:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk100726" title="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk100726"&gt;How to configure IPsec VPN tunnel between Check Point Security Gateway and Amazon Web Services VPC using static routes&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could not using VTI's be my issue? I'll be honest, i'm not familiar with VTI's or MSS clamping or dead peer detection.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Feb 2018 17:58:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-Tunnel-to-AWS-VPC-Sporadically-drops-after-Policy-Install/m-p/30488#M2422</guid>
      <dc:creator>Saul_Schwartz</dc:creator>
      <dc:date>2018-02-16T17:58:54Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Tunnel to AWS VPC - Sporadically drops after Policy Install</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-Tunnel-to-AWS-VPC-Sporadically-drops-after-Policy-Install/m-p/30489#M2423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you're not using VTIs and Dynamic Routing, it's a definite possibility.&lt;/P&gt;&lt;P&gt;It's a bit more reliable to use VTIs when connecting with Amazon's VPN endpoint.&lt;/P&gt;&lt;P&gt;However, if you're going down this path, I recommend upgrading the Security Gateway to R80.10, so you can fully leverage CoreXL when using VTIs (otherwise, CoreXL is disabled when using VTIs, and performance will take a hit).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Feb 2018 19:35:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-Tunnel-to-AWS-VPC-Sporadically-drops-after-Policy-Install/m-p/30489#M2423</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2018-02-16T19:35:24Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Tunnel to AWS VPC - Sporadically drops after Policy Install</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-Tunnel-to-AWS-VPC-Sporadically-drops-after-Policy-Install/m-p/30490#M2424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I remember a similar issue whose description can be found in&amp;nbsp; &lt;EM&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk116013&amp;amp;partition=Advanced&amp;amp;product=Security" style="max-width: 840px;"&gt;sk116013: NAT fails after policy installation&lt;/A&gt;&lt;/EM&gt;&lt;SPAN class="" style="vertical-align: top; color: #e65785; display: inline-block; margin: 0px 0px;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="" style="vertical-align: top; display: inline-block; margin: 0px 0px;"&gt;I suggest to verify if it is the same - then you can get a fix for it from TAC.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2018 11:53:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-Tunnel-to-AWS-VPC-Sporadically-drops-after-Policy-Install/m-p/30490#M2424</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2018-03-21T11:53:01Z</dc:date>
    </item>
  </channel>
</rss>

