<?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: BGP over IPSec using vIPs for VTIs in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/109006#M14776</link>
    <description>&lt;P&gt;Do not have a diagram handy, but the output of the received routes shows correct networks with correct next hops.&lt;/P&gt;
&lt;P&gt;And yes, the routes are clearly labeled as BGP ( with "B" in the Type column).&lt;/P&gt;
&lt;P&gt;Additional tidbit of information: the vIP/VTI interfaces configured as "External". As I do not have access to the environment now, I cannot vouch for it, but I think that anti-spoofing is enabled on that interface.&lt;/P&gt;
&lt;P&gt;Sorry for the sparse data, I have walked-in on this project just now, after client was working with TAC for a while.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Jan 2021 12:56:49 GMT</pubDate>
    <dc:creator>Vladimir</dc:creator>
    <dc:date>2021-01-27T12:56:49Z</dc:date>
    <item>
      <title>BGP over IPSec using vIPs for VTIs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/108930#M14769</link>
      <description>&lt;P&gt;I have to ask for your help on this one:&lt;/P&gt;
&lt;P&gt;Client has a cluster running R80.40.&lt;/P&gt;
&lt;P&gt;Connected to the peer's network via IPSec using VTIs.&lt;/P&gt;
&lt;P&gt;Despite being provided with single IP address for our side of the tunnel(s), TAC recommended using /29 network with vIPs to assign the tunnel IP address, claiming that the peer should not be concerned about it, since they will only see vIP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have seen this approach used for AWS VPN connectivity with Static Routes, but the IPs for VTIs were generated by AWS.&lt;/P&gt;
&lt;P&gt;In the BGP via IPSec implementation guide for AWS there are no references to this approach.&lt;/P&gt;
&lt;P&gt;Tunnel IPs on both sides are in 10.x.x.x range.&lt;/P&gt;
&lt;P&gt;There is also a static route for the 10.0.0.0/8 pointing to the internal gateway on the cluster.&lt;/P&gt;
&lt;P&gt;VPN is established.&lt;/P&gt;
&lt;P&gt;We can see the 19X.XXX.XXX.0/24 networks advertised by the peer via BGP.&lt;/P&gt;
&lt;P&gt;But in the routing table, the peer's network have the same next hop as the one defined for the 10.0.0.0/8.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have never seen VTIs used as the cluster interfaces with vIPs, so please confirm that this is acceptable.&lt;/P&gt;
&lt;P&gt;I would also appreciate the pointers for the reason the BGP routes having incorrect next hop.&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2021 03:05:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/108930#M14769</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2021-01-27T03:05:05Z</dc:date>
    </item>
    <item>
      <title>Re: BGP over IPSec using vIPs for VTIs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/108942#M14772</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Do you have a very brief drawing of the setup ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand you see an advertised network from the peer, but in the routing table it has the wrong gateway ? --&amp;nbsp;the routing table absolutly shows this as a BGP route ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;show ip bgp neighbor &amp;lt;ip&amp;gt; received-routes&amp;nbsp; &amp;nbsp;- what does this show ?&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2021 07:44:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/108942#M14772</guid>
      <dc:creator>vinceneil666</dc:creator>
      <dc:date>2021-01-27T07:44:09Z</dc:date>
    </item>
    <item>
      <title>Re: BGP over IPSec using vIPs for VTIs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/109006#M14776</link>
      <description>&lt;P&gt;Do not have a diagram handy, but the output of the received routes shows correct networks with correct next hops.&lt;/P&gt;
&lt;P&gt;And yes, the routes are clearly labeled as BGP ( with "B" in the Type column).&lt;/P&gt;
&lt;P&gt;Additional tidbit of information: the vIP/VTI interfaces configured as "External". As I do not have access to the environment now, I cannot vouch for it, but I think that anti-spoofing is enabled on that interface.&lt;/P&gt;
&lt;P&gt;Sorry for the sparse data, I have walked-in on this project just now, after client was working with TAC for a while.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2021 12:56:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/109006#M14776</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2021-01-27T12:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: BGP over IPSec using vIPs for VTIs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/114102#M15934</link>
      <description>&lt;P&gt;I am have a similar problem. Did you get bgp peering working. My cluster is send the bgp tcp messages at the Firewall ip and not the Vip of the vpnt interface.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Mar 2021 18:13:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/BGP-over-IPSec-using-vIPs-for-VTIs/m-p/114102#M15934</guid>
      <dc:creator>_zball_</dc:creator>
      <dc:date>2021-03-19T18:13:24Z</dc:date>
    </item>
  </channel>
</rss>

