<?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: Effects of Creating a Logical interface VLAN on PIX 535 OS 6 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613298#M497275</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i m not sure of what you re trying to accomplish but i ll explain what you did here and what will happen to the packets  as they pass accross the interface &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*first you are working with a pix under 6.x version, (configuring vlan is simplified a little bit under 7.x specialy when dealing with untagged packets)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*we suppose the port of switch in front of your pix is configured correctly as trunk with dot1q  the only supported method for pix, also remember that the switch will send untagged packet within the native vlan &lt;/P&gt;&lt;P&gt;that default  to one 1 and can be changed to whatever value within the range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*so here every packet that hits the interface ethernet3 of your pix for both direction &lt;/P&gt;&lt;P&gt;(toward the switch or from the switch toward the pix)  that are  untagged or in the native vlan will be dropped (if the native vlan is diffrent from 4), because you forced the pix to do that  by specifying the PHYSICAL keyword and assigning a vlan id of 4 , which mean every packet must be tagged and in the expected defined vlan in order to pass accross the interface otherwise it will be dropped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(your  idea here is to use only VLANs that are defined specifically to pass data to and from the firewall  while eliminating  the possibility that an unexpected VLAN appears on the trunk).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(NOW your physical ethernet3 100full ovelay with the the logical VLAN4)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Sep 2006 02:58:06 GMT</pubDate>
    <dc:creator>kamal-learn</dc:creator>
    <dc:date>2006-09-28T02:58:06Z</dc:date>
    <item>
      <title>Effects of Creating a Logical interface VLAN on PIX 535 OS 6.3(5)</title>
      <link>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613295#M497270</link>
      <description>&lt;P&gt;I would to like clarify if what would the effect if I am to create a logical VLAN interface on a existing and working physical interface?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What would be the effects of this configuration? Would the physical interface be shutdown?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:11:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613295#M497270</guid>
      <dc:creator>terblac</dc:creator>
      <dc:date>2020-02-21T09:11:48Z</dc:date>
    </item>
    <item>
      <title>Re: Effects of Creating a Logical interface VLAN on PIX 535 OS 6</title>
      <link>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613296#M497272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure I exactly understand what you want to do, but logical interfaces require the physical interface to be up - if the physical interface is down then all your logical interfaces will also be down. The act of creating a logical interface does not shutdown the physical interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe you could clarify exactly what you want to accomplish?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Andrew.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 09:42:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613296#M497272</guid>
      <dc:creator>andrew.burns</dc:creator>
      <dc:date>2006-09-27T09:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Effects of Creating a Logical interface VLAN on PIX 535 OS 6</title>
      <link>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613297#M497274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Andrew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, the act of creating a logical interface is what I am asking about if it would affect the physical interface, just like below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface ethernet3 100full&lt;/P&gt;&lt;P&gt;interface ethernet3 vlan4 physical&lt;/P&gt;&lt;P&gt;interface ethernet3 vlan4020 logical&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If ethernet 100full was already connected to a switch and was already in procution. And if I was to create ethernet3 vlan4020 logical, would if affect the ethernet 100full or ethernet vlan4 physical?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will try to do it here on our PIX. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Sep 2006 00:05:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613297#M497274</guid>
      <dc:creator>terblac</dc:creator>
      <dc:date>2006-09-28T00:05:33Z</dc:date>
    </item>
    <item>
      <title>Re: Effects of Creating a Logical interface VLAN on PIX 535 OS 6</title>
      <link>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613298#M497275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i m not sure of what you re trying to accomplish but i ll explain what you did here and what will happen to the packets  as they pass accross the interface &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*first you are working with a pix under 6.x version, (configuring vlan is simplified a little bit under 7.x specialy when dealing with untagged packets)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*we suppose the port of switch in front of your pix is configured correctly as trunk with dot1q  the only supported method for pix, also remember that the switch will send untagged packet within the native vlan &lt;/P&gt;&lt;P&gt;that default  to one 1 and can be changed to whatever value within the range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*so here every packet that hits the interface ethernet3 of your pix for both direction &lt;/P&gt;&lt;P&gt;(toward the switch or from the switch toward the pix)  that are  untagged or in the native vlan will be dropped (if the native vlan is diffrent from 4), because you forced the pix to do that  by specifying the PHYSICAL keyword and assigning a vlan id of 4 , which mean every packet must be tagged and in the expected defined vlan in order to pass accross the interface otherwise it will be dropped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(your  idea here is to use only VLANs that are defined specifically to pass data to and from the firewall  while eliminating  the possibility that an unexpected VLAN appears on the trunk).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(NOW your physical ethernet3 100full ovelay with the the logical VLAN4)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Sep 2006 02:58:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/effects-of-creating-a-logical-interface-vlan-on-pix-535-os-6-3-5/m-p/613298#M497275</guid>
      <dc:creator>kamal-learn</dc:creator>
      <dc:date>2006-09-28T02:58:06Z</dc:date>
    </item>
  </channel>
</rss>

