<?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 Layer 2 subinterfaces w/ Vlan interface for routing..... in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/layer-2-subinterfaces-w-vlan-interface-for-routing/m-p/578297#M115995</link>
    <description>&lt;P&gt;Say I want to connect this port to a switch downstream (trunk), with clients hanging off of switch on access ports and use vlan interfaces for routing. Switch is set to trunk allowing relevant vlans, the firewall interface is subinterfaced (layer2) with the respective tag and vlan assigned. This is not working. DHCP does not work at all. Can someone let me know if I am doing this correctly? I am having trouble getting this configured.&lt;/P&gt;
&lt;P&gt;IE:&lt;/P&gt;
&lt;P&gt;FW &amp;lt;trunk&amp;gt;Switch&amp;lt;access&amp;gt;Client&lt;/P&gt;
&lt;P&gt;FW eth1/3 subinterfaced (eth1/3.600 - layer2) with tag and vlan. Vlan exists and is pointing to the vlan.600 interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I have a physical interface assigned to a vlan, and a client directly plugged into the firewall port, DHCP/traffic works as expected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am accustomed to using layer3 subinterfaces, but this had me curious so I wanted to try it.&lt;/P&gt;</description>
    <pubDate>Mon, 26 Feb 2024 06:02:30 GMT</pubDate>
    <dc:creator>VK9H13</dc:creator>
    <dc:date>2024-02-26T06:02:30Z</dc:date>
    <item>
      <title>Layer 2 subinterfaces w/ Vlan interface for routing.....</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/layer-2-subinterfaces-w-vlan-interface-for-routing/m-p/578297#M115995</link>
      <description>&lt;P&gt;Say I want to connect this port to a switch downstream (trunk), with clients hanging off of switch on access ports and use vlan interfaces for routing. Switch is set to trunk allowing relevant vlans, the firewall interface is subinterfaced (layer2) with the respective tag and vlan assigned. This is not working. DHCP does not work at all. Can someone let me know if I am doing this correctly? I am having trouble getting this configured.&lt;/P&gt;
&lt;P&gt;IE:&lt;/P&gt;
&lt;P&gt;FW &amp;lt;trunk&amp;gt;Switch&amp;lt;access&amp;gt;Client&lt;/P&gt;
&lt;P&gt;FW eth1/3 subinterfaced (eth1/3.600 - layer2) with tag and vlan. Vlan exists and is pointing to the vlan.600 interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I have a physical interface assigned to a vlan, and a client directly plugged into the firewall port, DHCP/traffic works as expected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am accustomed to using layer3 subinterfaces, but this had me curious so I wanted to try it.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2024 06:02:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/layer-2-subinterfaces-w-vlan-interface-for-routing/m-p/578297#M115995</guid>
      <dc:creator>VK9H13</dc:creator>
      <dc:date>2024-02-26T06:02:30Z</dc:date>
    </item>
    <item>
      <title>Re: Layer 2 subinterfaces w/ Vlan interface for routing.....</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/layer-2-subinterfaces-w-vlan-interface-for-routing/m-p/578345#M116001</link>
      <description>&lt;P&gt;you need to have 2 "vlans" (it's a bit of unfortunate naming on Palo's side)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;one is a layer2 vlan assigned to your subinterface that determines which interfaces belong to the same vlan and zone regardles of their tag (this is virtual layer 2 inside the chassis)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the other is the vlan interface, which is like a VRF (found in the interfaces &amp;gt; vlan tab). this is where you set a vlan interface up with an ip address so it can function as a default route, and this interface can be used to attach a DHCP server&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2024 13:43:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/layer-2-subinterfaces-w-vlan-interface-for-routing/m-p/578345#M116001</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2024-02-26T13:43:45Z</dc:date>
    </item>
  </channel>
</rss>

