<?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: S2S Vpn in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196330#M36631</link>
    <description>&lt;P&gt;You mean HA mode in Link Selection and Route probing does not work if ISP Redundancy is on with&amp;nbsp; a clear box Apply to VPN ?&lt;/P&gt;</description>
    <pubDate>Thu, 26 Oct 2023 18:32:37 GMT</pubDate>
    <dc:creator>BikeMan</dc:creator>
    <dc:date>2023-10-26T18:32:37Z</dc:date>
    <item>
      <title>S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/195595#M36441</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Not sure to be on the right group... but let's try.&lt;/P&gt;&lt;P&gt;I try to create a s2s vpn between 2 clusters running R81.10 last HFA. Both have 2 internet link, and I want to have a HA between eachlink. It is more or less working, but not as I would like.&lt;/P&gt;&lt;P&gt;So, taking time to read the complete doc (no comment...), I see in the S2S VPN guide I have to add routing information with metric. But when I use the "set static-route", I can't set any metric.&lt;/P&gt;&lt;P&gt;Does, in this case, "metric" means "priority" or there is another way to configure the "metric" ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I also have to define the probing with "set static-route xxxx ping" also ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The idea is to have a complete HA solution, using a first link as primary and a second one as secondary.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks for your help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 07:46:53 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/195595#M36441</guid>
      <dc:creator>BikeMan</dc:creator>
      <dc:date>2023-10-19T07:46:53Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/195680#M36470</link>
      <description>&lt;P&gt;"last HFA" is meaningless now or in the future since that will change.&lt;BR /&gt;Always include the specific JHF in use.&lt;/P&gt;
&lt;P&gt;Yes priority means metric here.&lt;BR /&gt;set static-route xxx monitored-ip x.y.z.w should be correct.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 20:10:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/195680#M36470</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-10-19T20:10:27Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196157#M36595</link>
      <description>&lt;P&gt;Using HFA110.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently the scope is simple. I have 2 clusters. CLA has one ISP (ISPA1). CLB,2 has 2 ISP (ISPB1, ISPB2).&lt;/P&gt;&lt;P&gt;On CLB ISP redundancy is applied without applying settings to VPN. So I have configured the Link selection on CLB to use only ISPB2, and route ISPA1 to ISPB2 (without set probing x.x.x.x/y on the cluster B members).&lt;/P&gt;&lt;P&gt;I have used Route probing, seems ISPB1 was still used for VPN.&lt;/P&gt;&lt;P&gt;Then set to Operating system Table, same result.&lt;/P&gt;&lt;P&gt;But I have checked the result with "Tunnel monitoring" and/or "vpn tu". Involved ISP was ISP1B.&lt;/P&gt;&lt;P&gt;When I check with tcpdump, it seems the right interface is used (no trafic on ethx, trafic on ethy).&lt;/P&gt;&lt;P&gt;If I have to use tcpdump to check, it is not funny at all.&lt;/P&gt;&lt;P&gt;Any idea ?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Oct 2023 14:48:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196157#M36595</guid>
      <dc:creator>BikeMan</dc:creator>
      <dc:date>2023-10-25T14:48:46Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196241#M36620</link>
      <description>&lt;P&gt;So you're not applying ISP Redundancy to VPN and you ARE using VPN?&lt;BR /&gt;Possible this might cause the issues you're seeing.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 04:02:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196241#M36620</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-10-26T04:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196246#M36622</link>
      <description>&lt;P&gt;Yes, this is the set up. Check box in ISP Redundandcy is cleared. Because we don't want to use same link for Internet access and VPN, except in case of failure.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 06:47:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196246#M36622</guid>
      <dc:creator>BikeMan</dc:creator>
      <dc:date>2023-10-26T06:47:48Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196310#M36627</link>
      <description>&lt;P&gt;Problem is, without that option being ticked, the underlying changes needed to make VPN work when failed over to the other ISP link will not be done.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 16:18:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196310#M36627</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-10-26T16:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196330#M36631</link>
      <description>&lt;P&gt;You mean HA mode in Link Selection and Route probing does not work if ISP Redundancy is on with&amp;nbsp; a clear box Apply to VPN ?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 18:32:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196330#M36631</guid>
      <dc:creator>BikeMan</dc:creator>
      <dc:date>2023-10-26T18:32:37Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196346#M36636</link>
      <description>&lt;P&gt;If you want VPN to fail over to a different link with ISP Redundancy, that box must be checked.&lt;BR /&gt;Otherwise, it probably will not work.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 21:01:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/196346#M36636</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-10-26T21:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/200592#M37672</link>
      <description>&lt;P&gt;Hi PhoneBoy,&lt;/P&gt;&lt;P&gt;Following several test, you are right and check box has to be checked. Sad to learn that because that means you can not split traffic (internet / vpn) in an easy way. Target was to have one link "master" for internet and the other link "master" for VPN.&lt;/P&gt;&lt;P&gt;Guessing that if I have 4 isp, I could configure 2 for Internet and 2 for VPN. This should work but it is not in the current scope.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 08:49:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/200592#M37672</guid>
      <dc:creator>BikeMan</dc:creator>
      <dc:date>2023-12-14T08:49:45Z</dc:date>
    </item>
    <item>
      <title>Re: S2S Vpn</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/200672#M37697</link>
      <description>&lt;P&gt;R82 should offer more flexibility in this area.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2023 00:07:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/S2S-Vpn/m-p/200672#M37697</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-12-15T00:07:56Z</dc:date>
    </item>
  </channel>
</rss>

