<?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: Access-list in layer 2 interface in Routing and SD-WAN</title>
    <link>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028934#M329414</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/459403"&gt;@sivam siva&lt;/a&gt;&amp;nbsp;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;This is applied under a physical interface that belongs to a vlan and is perfect valid.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"&lt;STRONG&gt;The port ACL (PACL&lt;/STRONG&gt;) feature provides the ability to perform access control on specific Layer 2 ports. A Layer 2 port is a physical LAN or trunk port that belongs to a VLAN. Port ACLs are applied only on the ingress traffic. The port ACL feature is supported only in hardware (port ACLs are not applied to any packets routed in software)."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"&lt;STRONG&gt;VLAN ACLs (VACLs)&lt;/STRONG&gt; can provide access control for all packet s that are bridged within a VLAN or that are routed into or out of a VLAN or a WAN interface for VACL capture. Unlike Cisco IOS ACLs that are applied on routed packets only, VACLs apply to all packets and can be applied to any VLAN or WAN interface. VACLs are processed in the ACL TCAM hardware. VACLs ignore any Cisco IOS ACL fields that are not supported in hardware."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Look here more detail: &lt;A href="https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/vacl.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/vacl.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Feb 2020 11:46:11 GMT</pubDate>
    <dc:creator>Jaderson Pessoa</dc:creator>
    <dc:date>2020-02-13T11:46:11Z</dc:date>
    <item>
      <title>Access-list in layer 2 interface</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028886#M329408</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/0/1&lt;/P&gt;&lt;P&gt;&amp;nbsp;switchport access vlan 17&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;STRONG&gt;switchport mode access&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;switchport voice vlan 710&lt;/P&gt;&lt;P&gt;&amp;nbsp;switchport port-security violation restrict&lt;/P&gt;&lt;P&gt;&amp;nbsp;switchport port-security aging time 2&lt;/P&gt;&lt;P&gt;&amp;nbsp;switchport port-security aging type inactivity&lt;/P&gt;&lt;P&gt;&amp;nbsp;switchport port-security&lt;/P&gt;&lt;P&gt;&amp;nbsp;device-tracking attach-policy xxxxxxxx&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;ip access-group 102 in&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;authentication event fail action next-method&lt;/P&gt;&lt;P&gt;&amp;nbsp;authentication host-mode multi-auth&lt;/P&gt;&lt;P&gt;&amp;nbsp;authentication open&lt;/P&gt;&lt;P&gt;&amp;nbsp;authentication order dot1x mab&lt;/P&gt;&lt;P&gt;&amp;nbsp;authentication priority mab dot1x&lt;/P&gt;&lt;P&gt;&amp;nbsp;authentication port-control auto&lt;/P&gt;&lt;P&gt;&amp;nbsp;authentication timer reauthenticate server&lt;/P&gt;&lt;P&gt;&amp;nbsp;authentication timer inactivity server&lt;/P&gt;&lt;P&gt;&amp;nbsp;authentication violation restrict&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;can anyone tell why this ACL is applied in layer 2 interface, I studied VACL in which I learned that ACL will not work in the layer 2 interface.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;Siva&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2020 10:10:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028886#M329408</guid>
      <dc:creator>sivam siva</dc:creator>
      <dc:date>2020-02-13T10:10:05Z</dc:date>
    </item>
    <item>
      <title>Re: Access-list in layer 2 interface</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028902#M329409</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;
&lt;P&gt;This is a 'Port ACL' and is perfectly valid.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/en/US/docs/switches/lan/catalyst3850/software/release/3se/consolidated_guide/b_consolidated_3850_3se_cg_chapter_0111001.html#ID90" target="_blank"&gt;https://www.cisco.com/en/US/docs/switches/lan/catalyst3850/software/release/3se/consolidated_guide/b_consolidated_3850_3se_cg_chapter_0111001.html#ID90&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;cheers,&lt;/P&gt;
&lt;P&gt;Seb.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2020 10:30:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028902#M329409</guid>
      <dc:creator>Seb Rupik</dc:creator>
      <dc:date>2020-02-13T10:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: Access-list in layer 2 interface</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028924#M329411</link>
      <description>&lt;P&gt;Perhaps you are confused because a L3/L4 ACL is applied on a L2-switch. But L2-switch only refers to the forwarding decision which is done based on L2 information. The switch can look into the packets more deeply to do some security-control like these Access-Lists.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2020 11:16:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028924#M329411</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2020-02-13T11:16:08Z</dc:date>
    </item>
    <item>
      <title>Re: Access-list in layer 2 interface</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028934#M329414</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/459403"&gt;@sivam siva&lt;/a&gt;&amp;nbsp;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;This is applied under a physical interface that belongs to a vlan and is perfect valid.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"&lt;STRONG&gt;The port ACL (PACL&lt;/STRONG&gt;) feature provides the ability to perform access control on specific Layer 2 ports. A Layer 2 port is a physical LAN or trunk port that belongs to a VLAN. Port ACLs are applied only on the ingress traffic. The port ACL feature is supported only in hardware (port ACLs are not applied to any packets routed in software)."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"&lt;STRONG&gt;VLAN ACLs (VACLs)&lt;/STRONG&gt; can provide access control for all packet s that are bridged within a VLAN or that are routed into or out of a VLAN or a WAN interface for VACL capture. Unlike Cisco IOS ACLs that are applied on routed packets only, VACLs apply to all packets and can be applied to any VLAN or WAN interface. VACLs are processed in the ACL TCAM hardware. VACLs ignore any Cisco IOS ACL fields that are not supported in hardware."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Look here more detail: &lt;A href="https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/vacl.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/vacl.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2020 11:46:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/access-list-in-layer-2-interface/m-p/4028934#M329414</guid>
      <dc:creator>Jaderson Pessoa</dc:creator>
      <dc:date>2020-02-13T11:46:11Z</dc:date>
    </item>
  </channel>
</rss>

