<?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: VRRP on routers connected to Palo Alto Firewalls in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/vrrp-on-routers-connected-to-palo-alto-firewalls/m-p/416291#M93406</link>
    <description>&lt;P&gt;Please see the articles below as palo alto can be anabled to accept untagged traffic and Vlan 0 is considered untagged:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For vwire:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/configure-interfaces/virtual-wire-interfaces/vlan-tagged-traffic.html" target="_blank" rel="noopener"&gt;https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/configure-interfaces/virtual-wire-interfaces/vlan-tagged-traffic.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For layer 3:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClE2CAK" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClE2CAK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClYMCA0" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClYMCA0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClMFCA0" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClMFCA0&lt;/A&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;If you want interface layer 2 communication (not vwire) between the firewalls you may need to check if you can tag the native vlan on the routers before being send to palo alto:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/general-topics/native-vlan-for-trunk-ports/td-p/251564" target="_blank" rel="noopener"&gt;https://live.paloaltonetworks.com/t5/general-topics/native-vlan-for-trunk-ports/td-p/251564&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jul 2021 07:42:27 GMT</pubDate>
    <dc:creator>NikolayDimitrov</dc:creator>
    <dc:date>2021-07-01T07:42:27Z</dc:date>
    <item>
      <title>VRRP on routers connected to Palo Alto Firewalls</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vrrp-on-routers-connected-to-palo-alto-firewalls/m-p/416261#M93400</link>
      <description>&lt;P&gt;I have 2 Palo Alto Firewalls each connecting to Peplink Balance 310x routers. HA is configured between the two Balance 310x routers. What I am trying to achieve is communication between these 2 routers via the 2 FWs. The HA (VRRP) interface is in the untagged VLAN on the router. It is Layer 2 between the routers and FW's. I have the FW interfaces with an untagged interface ready to pass this traffic between them but this is not working.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="nickvardy76_0-1625050522210.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/34666i52F1F7DA8410F547/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="nickvardy76_0-1625050522210.png" alt="nickvardy76_0-1625050522210.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;See quick drawing above. I need to be able to pass the VRRP packets from the Peplink Balances via the 2 Palo Alto FW's. Is this possible using this design? I do not see any untagged traffic traversing the Palo's.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jun 2021 10:56:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vrrp-on-routers-connected-to-palo-alto-firewalls/m-p/416261#M93400</guid>
      <dc:creator>nickvardy76</dc:creator>
      <dc:date>2021-06-30T10:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: VRRP on routers connected to Palo Alto Firewalls</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vrrp-on-routers-connected-to-palo-alto-firewalls/m-p/416291#M93406</link>
      <description>&lt;P&gt;Please see the articles below as palo alto can be anabled to accept untagged traffic and Vlan 0 is considered untagged:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For vwire:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/configure-interfaces/virtual-wire-interfaces/vlan-tagged-traffic.html" target="_blank" rel="noopener"&gt;https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/configure-interfaces/virtual-wire-interfaces/vlan-tagged-traffic.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For layer 3:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClE2CAK" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClE2CAK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClYMCA0" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClYMCA0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClMFCA0" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClMFCA0&lt;/A&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;If you want interface layer 2 communication (not vwire) between the firewalls you may need to check if you can tag the native vlan on the routers before being send to palo alto:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/general-topics/native-vlan-for-trunk-ports/td-p/251564" target="_blank" rel="noopener"&gt;https://live.paloaltonetworks.com/t5/general-topics/native-vlan-for-trunk-ports/td-p/251564&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jul 2021 07:42:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vrrp-on-routers-connected-to-palo-alto-firewalls/m-p/416291#M93406</guid>
      <dc:creator>NikolayDimitrov</dc:creator>
      <dc:date>2021-07-01T07:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: VRRP on routers connected to Palo Alto Firewalls</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vrrp-on-routers-connected-to-palo-alto-firewalls/m-p/416437#M93422</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have already deployed (many times) such kind (almost) of configuration (PA L3 mode + Pelink in front in our case) but we uses a L2 switch (two in fact to provide HA) between the external interface of the PA and internal interface of the Peplink... If you use L2 mode (VWIRE) on PA interface,&amp;nbsp; just be careful with Spanning-Tree..&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HA&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jul 2021 07:10:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vrrp-on-routers-connected-to-palo-alto-firewalls/m-p/416437#M93422</guid>
      <dc:creator>slp-security</dc:creator>
      <dc:date>2021-07-01T07:10:01Z</dc:date>
    </item>
  </channel>
</rss>

