<?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: VN Tunnel is down after installing policy in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VN-Tunnel-is-down-after-installing-policy/m-p/110433#M15168</link>
    <description>&lt;P&gt;When policy is pushed the IKE Phase 1 SAs are cleared depending on the values of&amp;nbsp;&lt;STRONG&gt;ike_keep_child_sa_interop_devices&lt;/STRONG&gt; and&amp;nbsp;&lt;STRONG&gt;keep_IKE_SAs&lt;/STRONG&gt; which are both global; I don't think you can specify these values per VPN peer or community.&amp;nbsp; 3rd party gateways in particular don't like having an SA cleared early since the mechanism to recover (delete SA notification) does not usually work properly between vendors.&amp;nbsp; See Scenario 4 of&amp;nbsp;&lt;A class="cp_link sc_ellipsis" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk108600&amp;amp;partition=Advanced&amp;amp;product=IPSec" target="_blank" rel="noopener"&gt;sk108600: VPN Site-to-Site with 3rd party&lt;/A&gt;.&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only real ramification of setting one or both of these to true is that if you make a change to IKE Phase 1 configuration settings (encryption, hashing, etc), that change will not happen immediately upon policy push.&amp;nbsp; These types of changes don't occur very often once the tunnel is initially set up and tested, but if you do need to change these Phase 1 settings with "true" set you'll just need need to manually reset the IKE Phase 1 tunnel with &lt;STRONG&gt;vpn tu&lt;/STRONG&gt; after pushing policy to make it take effect.&amp;nbsp; That's it.&lt;/P&gt;</description>
    <pubDate>Wed, 10 Feb 2021 12:58:26 GMT</pubDate>
    <dc:creator>Timothy_Hall</dc:creator>
    <dc:date>2021-02-10T12:58:26Z</dc:date>
    <item>
      <title>VN Tunnel is down after installing policy</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VN-Tunnel-is-down-after-installing-policy/m-p/110404#M15164</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am facing issue with VPN tunnel between Check Point gateway and 3rd-party gateway, Sonicwall.&lt;/P&gt;&lt;P&gt;The situation is, the vpn connection is working as usual after the tunnel is up.&lt;/P&gt;&lt;P&gt;However, after we push the policy, the tunnel is coming down again.&lt;/P&gt;&lt;P&gt;What I'VE done next:&lt;/P&gt;&lt;P&gt;1. Confirmed no changes related to VPN settings on both Check Point gateway and Peer Gateway.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Confirmed the configuration on both side is tally with each other.&lt;/P&gt;&lt;P&gt;3. Reset tunnel on vpn tu, option (7).&lt;/P&gt;&lt;P&gt;4. Check vpn status again, still down. Refer to the packet capture on peer: 175.139.242.98 below:&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 806px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/10517i713E5420CB027705/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Supposedly, the vpn tunnel should come up after reset tunnel However, the tunnel is still down.&lt;/P&gt;&lt;P&gt;And, now I'm now checking on the &lt;STRONG&gt;&lt;A title="sk142355" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk142355&amp;amp;partition=Advanced&amp;amp;product=IPSec" target="_blank" rel="noopener"&gt;sk142355&lt;/A&gt;,&amp;nbsp;&lt;/STRONG&gt;however the changes on Global Properties might need to be considered properly as it might affected other vpn tunnels.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Current, our setup is on Standalone mode with R80.10 version with Take 279 hotfix.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hopefully, we have the solutions or workaround on this issue.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2021 08:30:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VN-Tunnel-is-down-after-installing-policy/m-p/110404#M15164</guid>
      <dc:creator>Fatihah</dc:creator>
      <dc:date>2021-02-10T08:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: VN Tunnel is down after installing policy</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VN-Tunnel-is-down-after-installing-policy/m-p/110433#M15168</link>
      <description>&lt;P&gt;When policy is pushed the IKE Phase 1 SAs are cleared depending on the values of&amp;nbsp;&lt;STRONG&gt;ike_keep_child_sa_interop_devices&lt;/STRONG&gt; and&amp;nbsp;&lt;STRONG&gt;keep_IKE_SAs&lt;/STRONG&gt; which are both global; I don't think you can specify these values per VPN peer or community.&amp;nbsp; 3rd party gateways in particular don't like having an SA cleared early since the mechanism to recover (delete SA notification) does not usually work properly between vendors.&amp;nbsp; See Scenario 4 of&amp;nbsp;&lt;A class="cp_link sc_ellipsis" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk108600&amp;amp;partition=Advanced&amp;amp;product=IPSec" target="_blank" rel="noopener"&gt;sk108600: VPN Site-to-Site with 3rd party&lt;/A&gt;.&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only real ramification of setting one or both of these to true is that if you make a change to IKE Phase 1 configuration settings (encryption, hashing, etc), that change will not happen immediately upon policy push.&amp;nbsp; These types of changes don't occur very often once the tunnel is initially set up and tested, but if you do need to change these Phase 1 settings with "true" set you'll just need need to manually reset the IKE Phase 1 tunnel with &lt;STRONG&gt;vpn tu&lt;/STRONG&gt; after pushing policy to make it take effect.&amp;nbsp; That's it.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2021 12:58:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VN-Tunnel-is-down-after-installing-policy/m-p/110433#M15168</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2021-02-10T12:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: VN Tunnel is down after installing policy</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VN-Tunnel-is-down-after-installing-policy/m-p/110974#M15280</link>
      <description>&lt;P&gt;Hi Timothy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your suggestion.&lt;/P&gt;&lt;P&gt;However, after checking all these, I suspected the issue is related to the instability of upstream device (Load Balancer). Hence, I bypass the Load balancer to the peer Gateway, and as a resulted&amp;nbsp;&lt;SPAN&gt;the tunnel was established and communication was successful between both sites.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Fatihah&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2021 00:57:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VN-Tunnel-is-down-after-installing-policy/m-p/110974#M15280</guid>
      <dc:creator>Fatihah</dc:creator>
      <dc:date>2021-02-17T00:57:28Z</dc:date>
    </item>
  </channel>
</rss>

