<?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: Advertising a more specific route with BGP in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210219#M34804</link>
    <description>&lt;P&gt;Instead of advertising 10.0.0.0/8 to my EBGP peer, I want to advertise a /32 instead. The next hop on my route table would be the same. The EBGP is on the other side of a VPN tunnel, the tunnel interfaces are on 169. and they are the peer IPs.&lt;/P&gt;</description>
    <pubDate>Mon, 01 Apr 2024 19:49:22 GMT</pubDate>
    <dc:creator>alannnnnnn</dc:creator>
    <dc:date>2024-04-01T19:49:22Z</dc:date>
    <item>
      <title>Advertising a more specific route with BGP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210199#M34798</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a check point receiving 10.0.0.0/8 via BGP, is it possible to advertise 10.0.0.1/32 to a different peer via BGP? 10.0.0.1/32 is not on my route table, only 10.0.0.0/8 is on the route table.&lt;/P&gt;&lt;P&gt;I'm assuming a combination of route maps or aggregation can solve this?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 17:19:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210199#M34798</guid>
      <dc:creator>alannnnnnn</dc:creator>
      <dc:date>2024-04-01T17:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: Advertising a more specific route with BGP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210207#M34800</link>
      <description>&lt;P&gt;Possible, yes, but the route has to come from somewhere. Typically, it comes from a route on the system which you then use a route-map to match and redistribute into BGP.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:21:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210207#M34800</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2024-04-01T19:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: Advertising a more specific route with BGP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210215#M34802</link>
      <description>&lt;P&gt;so, I would have to add a static route then, no other way around that?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:37:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210215#M34802</guid>
      <dc:creator>alannnnnnn</dc:creator>
      <dc:date>2024-04-01T19:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: Advertising a more specific route with BGP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210217#M34803</link>
      <description>&lt;P&gt;Or redistribute an interface route or something, yes. You can't just say "Hey BGP, tell my neighbors I know how to reach 10.20.30.40" if you don't actually know how to reach that address.&lt;/P&gt;
&lt;P&gt;What goal are you trying to accomplish?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:43:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210217#M34803</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2024-04-01T19:43:18Z</dc:date>
    </item>
    <item>
      <title>Re: Advertising a more specific route with BGP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210219#M34804</link>
      <description>&lt;P&gt;Instead of advertising 10.0.0.0/8 to my EBGP peer, I want to advertise a /32 instead. The next hop on my route table would be the same. The EBGP is on the other side of a VPN tunnel, the tunnel interfaces are on 169. and they are the peer IPs.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:49:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/210219#M34804</guid>
      <dc:creator>alannnnnnn</dc:creator>
      <dc:date>2024-04-01T19:49:22Z</dc:date>
    </item>
    <item>
      <title>Re: Advertising a more specific route with BGP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/211365#M35058</link>
      <description>&lt;P&gt;the workaround that i suggest and i usually use is nat pool:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk179549" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk179549&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 08:28:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Advertising-a-more-specific-route-with-BGP/m-p/211365#M35058</guid>
      <dc:creator>CheckPointerXL</dc:creator>
      <dc:date>2024-04-16T08:28:32Z</dc:date>
    </item>
  </channel>
</rss>

