<?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: Testing VPN phase1 and phase2 in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112626#M15656</link>
    <description>&lt;P&gt;Simple ping from one GW to the other one will cause that VPN will try to be established with relevant VPN configuration in place on both ends.&lt;/P&gt;</description>
    <pubDate>Sun, 07 Mar 2021 08:29:27 GMT</pubDate>
    <dc:creator>JozkoMrkvicka</dc:creator>
    <dc:date>2021-03-07T08:29:27Z</dc:date>
    <item>
      <title>Testing VPN phase1 and phase2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112623#M15654</link>
      <description>&lt;P&gt;hey,&lt;/P&gt;&lt;P&gt;i think a feature request for testing those configuration can have a good value for troubleshooting.&lt;/P&gt;&lt;P&gt;based on the security policy for example we might need to have someone on the other side to generate traffic, something we dont have 100%.&lt;/P&gt;&lt;P&gt;some test command can be useful to make the GW try to establish the vpn tunnel just for those parameter&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 07 Mar 2021 07:48:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112623#M15654</guid>
      <dc:creator>Dor_Marcovitch</dc:creator>
      <dc:date>2021-03-07T07:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: Testing VPN phase1 and phase2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112626#M15656</link>
      <description>&lt;P&gt;Simple ping from one GW to the other one will cause that VPN will try to be established with relevant VPN configuration in place on both ends.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Mar 2021 08:29:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112626#M15656</guid>
      <dc:creator>JozkoMrkvicka</dc:creator>
      <dc:date>2021-03-07T08:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: Testing VPN phase1 and phase2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112627#M15657</link>
      <description>&lt;P&gt;this should work only if the GW is in the encryption domain&lt;/P&gt;</description>
      <pubDate>Sun, 07 Mar 2021 08:32:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112627#M15657</guid>
      <dc:creator>Dor_Marcovitch</dc:creator>
      <dc:date>2021-03-07T08:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: Testing VPN phase1 and phase2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112630#M15658</link>
      <description>&lt;P&gt;Not really, the peer IP of GW (cluster IP) to be used for VPN itself is considered as valid part of VPN.&lt;/P&gt;
&lt;P&gt;In case of VPN performance and best practises, see:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk105119" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;Best Practices - VPN Performance&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?action=portlets.SearchResultMainAction&amp;amp;eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk73980" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;Relative speeds of algorithms for IPsec and SSL&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk104760" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;ATRG: VPN Core&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 07 Mar 2021 08:45:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112630#M15658</guid>
      <dc:creator>JozkoMrkvicka</dc:creator>
      <dc:date>2021-03-07T08:45:13Z</dc:date>
    </item>
    <item>
      <title>Re: Testing VPN phase1 and phase2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112647#M15672</link>
      <description>&lt;P&gt;There doesn't seem to be a way to simulate a VPN peer initiating a IKE negotiation to your Check Point firewall, at least that I can see.&amp;nbsp; Once the tunnel is up (no matter who initiated it) it is a two-way street, but in an interoperable scenario sometimes there will be a IKEv1 Phase 2 subnet/Proxy-ID negotation failure if one side initiates the tunnel, but the other side can initiate it just fine.&amp;nbsp; Not much you can really do about this except have the VPN peer try to initiate to you and see what happens.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Mar 2021 15:27:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Testing-VPN-phase1-and-phase2/m-p/112647#M15672</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2021-03-07T15:27:58Z</dc:date>
    </item>
  </channel>
</rss>

