<?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 response from AWS when pining from CheckPoint in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123541#M17747</link>
    <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;Thank you for the response. Should have mentioned we are using static routing.&lt;/P&gt;</description>
    <pubDate>Sun, 11 Jul 2021 23:22:01 GMT</pubDate>
    <dc:creator>ja123</dc:creator>
    <dc:date>2021-07-11T23:22:01Z</dc:date>
    <item>
      <title>No response from AWS when pining from CheckPoint</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123404#M17701</link>
      <description>&lt;P&gt;The client is using CheckPoint R75.x and we have established a site-to-site VPN Connection. The VPN on our end was setup using AWS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Were are able to ping from AWS to Checkpoint and receive a response, however, when the client pings from CheckPoint, the packets pass their firewall and into the tunnel but there is no response from AWS side.&lt;/P&gt;&lt;P&gt;The routing and rules are all setup correctly.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using 1 tunnel and AWS provides an outside and inside IPv4 cidr for the tunnel. The client used the outside cidr but wasn't sure what to do with the inside cidr. Does the inside cidr need to be added somewhere in CheckPoint?&lt;/P&gt;&lt;P&gt;Is there another step or solution we can take to address the above issue in terms of no receiving a response back?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jul 2021 07:21:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123404#M17701</guid>
      <dc:creator>ja123</dc:creator>
      <dc:date>2021-07-09T07:21:43Z</dc:date>
    </item>
    <item>
      <title>Re: No response from AWS when pining from CheckPoint</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123452#M17732</link>
      <description>&lt;P&gt;R75.x has been End of Support for quite a while and your client should upgrade to a supported release.&lt;BR /&gt;The appropriate instructions to configure a VPN to AWS are:&amp;nbsp;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk108958&amp;amp;partition=Basic&amp;amp;product=CloudGuard" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk108958&amp;amp;partition=Basic&amp;amp;product=CloudGuard&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jul 2021 20:10:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123452#M17732</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-07-09T20:10:54Z</dc:date>
    </item>
    <item>
      <title>Re: No response from AWS when pining from CheckPoint</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123454#M17733</link>
      <description>&lt;P&gt;What&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;sent you is best example of how to configure VPN tunnel with AWS. Disregarding the version, which btw is totally unsupported, did you do any capture on the CP firewall to see why packet is not being received? Maybe do fw monitor, zdebug, try turn off securexl as a test?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jul 2021 22:38:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123454#M17733</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2021-07-09T22:38:35Z</dc:date>
    </item>
    <item>
      <title>Re: No response from AWS when pining from CheckPoint</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123541#M17747</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;Thank you for the response. Should have mentioned we are using static routing.&lt;/P&gt;</description>
      <pubDate>Sun, 11 Jul 2021 23:22:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123541#M17747</guid>
      <dc:creator>ja123</dc:creator>
      <dc:date>2021-07-11T23:22:01Z</dc:date>
    </item>
    <item>
      <title>Re: No response from AWS when pining from CheckPoint</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123544#M17749</link>
      <description>&lt;P&gt;While I believe it is possible to make it work in that manner it is far from optimal as the AWS VPN endpoint expects redundancy using VTIs and dynamic routing.&lt;BR /&gt;We do have an SK for configurations without that, but as noted this is not a recommended configuration:&amp;nbsp;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk113840&amp;amp;partition=Advanced&amp;amp;product=IPSec" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk113840&amp;amp;partition=Advanced&amp;amp;product=IPSec&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jul 2021 00:29:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123544#M17749</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-07-12T00:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: No response from AWS when pining from CheckPoint</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123551#M17750</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is the inside IPv4 cidr provided by AWS need to be utilised in CheckPoint?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jul 2021 02:44:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123551#M17750</guid>
      <dc:creator>ja123</dc:creator>
      <dc:date>2021-07-12T02:44:14Z</dc:date>
    </item>
    <item>
      <title>Re: No response from AWS when pining from CheckPoint</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123554#M17752</link>
      <description>&lt;P&gt;In this configuration it seems to be:&amp;nbsp;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk100726" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk100726&lt;/A&gt;&lt;BR /&gt;However, it refers to a later version than you're running.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jul 2021 04:04:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/No-response-from-AWS-when-pining-from-CheckPoint/m-p/123554#M17752</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-07-12T04:04:22Z</dc:date>
    </item>
  </channel>
</rss>

