<?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: VTI interface with Cluster XL in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129144#M26473</link>
    <description>&lt;P&gt;Yes sir! So, say fw1 has VTI with IP 169.254.0.10 and fw2 is 169.254.0.11 and VIP is .12 and remote is say 169.254.0.15 (just making that up, but you get the idea, right?). MAKE SURE the peer name when creating vti interface&amp;nbsp; is exactly the same as interoperable object name, otherwise topology will fail.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Sep 2021 19:34:16 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2021-09-10T19:34:16Z</dc:date>
    <item>
      <title>VTI interface with Cluster XL</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129100#M26470</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Based on the R80.30 VPN admin Guide, when doing Route Based VPN with clustered gateways, we need to assign one VTI IP address for each member and one VTI IP adddress for the cluster VIP .&lt;/P&gt;&lt;P&gt;&lt;A href="https://sc1.checkpoint.com/documents/R80.30/WebAdminGuides/EN/CP_R80.30_SitetoSiteVPN_AdminGuide/html_frameset.htm?topic=documents/R80.30/WebAdminGuides/EN/CP_R80.30_SitetoSiteVPN_AdminGuide/13824&amp;amp;anchor=o14011" target="_blank" rel="noopener"&gt;https://sc1.checkpoint.com/documents/R80.30/WebAdminGuides/EN/CP_R80.30_SitetoSiteVPN_AdminGuide/html_frameset.htm?topic=documents/R80.30/WebAdminGuides/EN/CP_R80.30_SitetoSiteVPN_AdminGuide/13824&amp;amp;anchor=o14011&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Most of the time when doing Route Based VPN we get /30 or /31 subnet mask to have point to point with the peer.&lt;/P&gt;&lt;P&gt;- Does it mean that the IP for each member can be "dummy" interface that have nothing to do with the Cluster IP?&lt;/P&gt;&lt;P&gt;- Or should I get an IP in the same range for every VTI interface (Peer GW, member1, member2, and cluster)?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="vti.png" style="width: 900px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/13662i59662FFE101D489A/image-size/large?v=v2&amp;amp;px=999" role="button" title="vti.png" alt="vti.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your help&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Sep 2021 08:47:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129100#M26470</guid>
      <dc:creator>DR_74</dc:creator>
      <dc:date>2021-09-10T08:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: VTI interface with Cluster XL</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129124#M26471</link>
      <description>&lt;P&gt;I can confirm this, and Im 100% positive (no doubt in my mind at all) that everyone I ever worked with and configured this for, we always used IPs from 169.254.x.x subnet and it worked perfectly fine.&lt;/P&gt;
&lt;P&gt;As a matter of fact, you can refer to below article referencing that.&lt;/P&gt;
&lt;P&gt;&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;/P&gt;
&lt;P&gt;BUT, this is really important...MAKE SURE that when adding routes for this, that default gateway is the actual remote VTI interface IP address, otherwise it wont work.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ping me privately if you have issues, I have some guides for this as well. I cant share them with you, but I could show you some screenshots.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Sep 2021 16:54:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129124#M26471</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2021-09-10T16:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: VTI interface with Cluster XL</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129140#M26472</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;Thank you for your message&lt;/P&gt;&lt;P&gt;Just to clarify in our case we have the VTI address for the cluster that looks like 169.254.254.2. The remote peer has 169.254.254.1.&lt;/P&gt;&lt;P&gt;So can I use another 169.254.254.3 and .4 for both members ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or even something that has nothing to do with the VIP address eg 1.1.1.1 and 1.1.1.2&lt;/P&gt;</description>
      <pubDate>Fri, 10 Sep 2021 18:39:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129140#M26472</guid>
      <dc:creator>DR_74</dc:creator>
      <dc:date>2021-09-10T18:39:31Z</dc:date>
    </item>
    <item>
      <title>Re: VTI interface with Cluster XL</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129144#M26473</link>
      <description>&lt;P&gt;Yes sir! So, say fw1 has VTI with IP 169.254.0.10 and fw2 is 169.254.0.11 and VIP is .12 and remote is say 169.254.0.15 (just making that up, but you get the idea, right?). MAKE SURE the peer name when creating vti interface&amp;nbsp; is exactly the same as interoperable object name, otherwise topology will fail.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Sep 2021 19:34:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/129144#M26473</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2021-09-10T19:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: VTI interface with Cluster XL</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/154693#M26474</link>
      <description>&lt;P&gt;I found this very useful, thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2022 03:01:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/154693#M26474</guid>
      <dc:creator>AK2</dc:creator>
      <dc:date>2022-08-08T03:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: VTI interface with Cluster XL</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/154694#M26475</link>
      <description>&lt;P&gt;Thanks for asking this question, I had the same one&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":handshake:"&gt;🤝&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2022 03:03:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VTI-interface-with-Cluster-XL/m-p/154694#M26475</guid>
      <dc:creator>AK2</dc:creator>
      <dc:date>2022-08-08T03:03:38Z</dc:date>
    </item>
  </channel>
</rss>

