<?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: Layer 3 Ethernet Interface vs Layer 3 VLAN interface in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/582973#M116550</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/271836"&gt;@S_Williams901&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;You'd create a layer3 subinterface with the proper tag that matched your trunk VLAN. Unless someone can articulate their actual requirements to utilize layer2 interfaces on their firewall I don't personally see any reason why you'd utilize them. You can configure a trunk up to your firewall and just create layer3 subinterfaces with the proper tag.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Apr 2024 21:16:50 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2024-04-08T21:16:50Z</dc:date>
    <item>
      <title>Layer 3 Ethernet Interface vs Layer 3 VLAN interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/582965#M116546</link>
      <description>&lt;P&gt;Trying to really understand the difference here. I have never made a Layer 3 VLAN interface using the VLAN tab on "interfaces".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I make a layer 3 interface I use Ethernet Layer 3 interface that connects downstream to a switch. From what I can tell Layer 3 VLAN interface is a scenario for when you have physical clients connected to the firewall ports, like a switch. But seems like a hard sell since the availability of ports on most models.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2024 20:30:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/582965#M116546</guid>
      <dc:creator>S_Williams901</dc:creator>
      <dc:date>2024-04-08T20:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: Layer 3 Ethernet Interface vs Layer 3 VLAN interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/582973#M116550</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/271836"&gt;@S_Williams901&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;You'd create a layer3 subinterface with the proper tag that matched your trunk VLAN. Unless someone can articulate their actual requirements to utilize layer2 interfaces on their firewall I don't personally see any reason why you'd utilize them. You can configure a trunk up to your firewall and just create layer3 subinterfaces with the proper tag.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2024 21:16:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/582973#M116550</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2024-04-08T21:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: Layer 3 Ethernet Interface vs Layer 3 VLAN interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/583047#M116566</link>
      <description>&lt;P&gt;That is what I do now. But watching a demo on connecting actual clients to the firewall and assigning the ports to vlans, then using the vlan tab in interfaces, they created a IP created vlan "interface"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2024 14:04:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/583047#M116566</guid>
      <dc:creator>S_Williams901</dc:creator>
      <dc:date>2024-04-09T14:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: Layer 3 Ethernet Interface vs Layer 3 VLAN interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/583094#M116577</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/271836"&gt;@S_Williams901&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;That is what I do now. But watching a demo on connecting actual clients to the firewall and assigning the ports to vlans, then using the vlan tab in interfaces, they created a IP created vlan "interface"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Like&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;has previously mentioned the L3 VLAN can just be a sub-interface of an aggregate-ethernet (AE - Palo Port-Channel.)&amp;nbsp; While you might have seen other videos online that tie a L3 VLAN to a physical port that is ONE way to do it, but not required.&amp;nbsp; You can have 40 L3 VLANs as a "sub-interface" on a single AE or singular port if desired.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2024 19:23:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/layer-3-ethernet-interface-vs-layer-3-vlan-interface/m-p/583094#M116577</guid>
      <dc:creator>Brandon_Wertz</dc:creator>
      <dc:date>2024-04-09T19:23:24Z</dc:date>
    </item>
  </channel>
</rss>

