<?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: Palo Alto BGP with AWS Transit Gateway. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-bgp-with-aws-transit-gateway/m-p/424171#M94235</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;This is as simple as creating an redistribution policy explicitly listing the rfc1918 prefixes and configuring the BGP process to use it.&lt;/P&gt;&lt;P&gt;You can also use an export policy to adjust other prefix attributes to be sent to your peers, but since you are using the AS path prepend feature then you will already have this configured. The export policy can also be used as the method to select the rfc1918 prefixes you want to advertise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;cheers,&lt;/P&gt;&lt;P&gt;Seb.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Aug 2021 12:18:06 GMT</pubDate>
    <dc:creator>SebRupik</dc:creator>
    <dc:date>2021-08-03T12:18:06Z</dc:date>
    <item>
      <title>Palo Alto BGP with AWS Transit Gateway.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-bgp-with-aws-transit-gateway/m-p/424146#M94233</link>
      <description>&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;We have a BGP neighbor on our Palo Alto with a Transit Gateway in the AWS. This BGP is formed from our Site A to the AWS TGW.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now, we want to form another BGP from our Site B to the AWS TGW.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Site A should be preferred always and we know we can do that using the AS-path-prepends.&lt;/P&gt;&lt;P&gt;However, one additional requirement is that both the sites should advertise only the RFC 1918 IP's and the default route that we have. How can we achieve that?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The off course we will prepend that from Site B.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards!!&lt;/P&gt;&lt;P&gt;N.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Aug 2021 10:15:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-bgp-with-aws-transit-gateway/m-p/424146#M94233</guid>
      <dc:creator>nson2139</dc:creator>
      <dc:date>2021-08-03T10:15:03Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto BGP with AWS Transit Gateway.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-bgp-with-aws-transit-gateway/m-p/424171#M94235</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;This is as simple as creating an redistribution policy explicitly listing the rfc1918 prefixes and configuring the BGP process to use it.&lt;/P&gt;&lt;P&gt;You can also use an export policy to adjust other prefix attributes to be sent to your peers, but since you are using the AS path prepend feature then you will already have this configured. The export policy can also be used as the method to select the rfc1918 prefixes you want to advertise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;cheers,&lt;/P&gt;&lt;P&gt;Seb.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Aug 2021 12:18:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-bgp-with-aws-transit-gateway/m-p/424171#M94235</guid>
      <dc:creator>SebRupik</dc:creator>
      <dc:date>2021-08-03T12:18:06Z</dc:date>
    </item>
  </channel>
</rss>

