<?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 peeering in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/bgp-peeering/m-p/551329#M1592</link>
    <description>&lt;P&gt;Hello Wael.Hedhli,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE class="newpage"&gt;OpenConfirm State:

      In this state, BGP waits for a KEEPALIVE or NOTIFICATION message.&lt;/PRE&gt;
&lt;P&gt;From RFC4271.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Maybe you can check on the peer side for some information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the firewall side, I think you can set a packet capture on tcp/179 (tx/rx/drop).&lt;/P&gt;
&lt;P&gt;And make sure there is no drop capture (that means no packet dropped by the firewall).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Olivier&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jul 2023 11:28:47 GMT</pubDate>
    <dc:creator>ozheng</dc:creator>
    <dc:date>2023-07-27T11:28:47Z</dc:date>
    <item>
      <title>BGP peeering</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/bgp-peeering/m-p/551292#M1588</link>
      <description>&lt;P&gt;Trying to setup a Two BGP session with 2 separate routers that provide internet access.&lt;BR /&gt;The 3 devices (PA, router1 and router2) share the same network 10.9.9.0/25.&lt;BR /&gt;BGP session 1 : PA &amp;lt;--&amp;gt; Router1&lt;BR /&gt;BGP Session 2: PA &amp;lt;--&amp;gt; Router2&lt;BR /&gt;the two sessions seems working fine when activating them individually, however when trying to establish the 2 sessions simultanialsty, one of them is stuck in active/openconfirm&lt;BR /&gt;I can't figure it out&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 08:53:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/bgp-peeering/m-p/551292#M1588</guid>
      <dc:creator>wael.Hedhli</dc:creator>
      <dc:date>2023-07-27T08:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: BGP peeering</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/bgp-peeering/m-p/551329#M1592</link>
      <description>&lt;P&gt;Hello Wael.Hedhli,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE class="newpage"&gt;OpenConfirm State:

      In this state, BGP waits for a KEEPALIVE or NOTIFICATION message.&lt;/PRE&gt;
&lt;P&gt;From RFC4271.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Maybe you can check on the peer side for some information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the firewall side, I think you can set a packet capture on tcp/179 (tx/rx/drop).&lt;/P&gt;
&lt;P&gt;And make sure there is no drop capture (that means no packet dropped by the firewall).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Olivier&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 11:28:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/bgp-peeering/m-p/551329#M1592</guid>
      <dc:creator>ozheng</dc:creator>
      <dc:date>2023-07-27T11:28:47Z</dc:date>
    </item>
  </channel>
</rss>

