<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Security: Common Ethertypes in Vlan Access Maps</title>
	<atom:link href="http://ardenpackeer.com/security/security-common-ethertypes-in-vlan-access-maps/feed/" rel="self" type="application/rss+xml" />
	<link>http://ardenpackeer.com/security/security-common-ethertypes-in-vlan-access-maps/</link>
	<description>Helping You Become a Network Ninja</description>
	<lastBuildDate>Fri, 19 Mar 2010 22:04:51 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arden Packeer, CCIE #20716</title>
		<link>http://ardenpackeer.com/security/security-common-ethertypes-in-vlan-access-maps/comment-page-1/#comment-898</link>
		<dc:creator>Arden Packeer, CCIE #20716</dc:creator>
		<pubDate>Wed, 11 Jun 2008 19:54:58 +0000</pubDate>
		<guid isPermaLink="false">http://ardenpackeer.com/blog/security-common-ethertypes-in-vlan-access-maps/#comment-898</guid>
		<description>Hi Sharath,

Thanks for the correction. I have updated the article.</description>
		<content:encoded><![CDATA[<p>Hi Sharath,</p>
<p>Thanks for the correction. I have updated the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharath</title>
		<link>http://ardenpackeer.com/security/security-common-ethertypes-in-vlan-access-maps/comment-page-1/#comment-897</link>
		<dc:creator>Sharath</dc:creator>
		<pubDate>Wed, 11 Jun 2008 19:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://ardenpackeer.com/blog/security-common-ethertypes-in-vlan-access-maps/#comment-897</guid>
		<description>Hello Arden,

The CAT 3550 and 3560 switches process IP Packets in a different way than the non-IP Packets. So it is Mandatory to use IP access-list.

&quot;In the example above we are using an ip access-list to match ip traffic, but we could have also used a mac access-list to do this&quot;

We cannot use a MAC access-list to allow IP Packets.

Sharath</description>
		<content:encoded><![CDATA[<p>Hello Arden,</p>
<p>The CAT 3550 and 3560 switches process IP Packets in a different way than the non-IP Packets. So it is Mandatory to use IP access-list.</p>
<p>&#8220;In the example above we are using an ip access-list to match ip traffic, but we could have also used a mac access-list to do this&#8221;</p>
<p>We cannot use a MAC access-list to allow IP Packets.</p>
<p>Sharath</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharath Samanth</title>
		<link>http://ardenpackeer.com/security/security-common-ethertypes-in-vlan-access-maps/comment-page-1/#comment-884</link>
		<dc:creator>Sharath Samanth</dc:creator>
		<pubDate>Sat, 07 Jun 2008 19:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://ardenpackeer.com/blog/security-common-ethertypes-in-vlan-access-maps/#comment-884</guid>
		<description>Hi Arden,

This was a really helpful guide on Ether Types. But I am really facing some strange issues.

Objective:
I am trying to make vlan 1 an IP only VLAN.

Configuration:
I have configured the following MAC ACLs.

mac access-list extended IEEE_STP
 permit any any lsap 0x4242 0x0

mac access-list extended IPARP
 permit any any 0x806 0x0

mac access-list extended IPV4
 permit any any 0x800 0x0

The following is the VLAN Access Map

vlan access-map P2F 10
 action forward
 match mac address IEEE_STP
vlan access-map P2F 11
 action forward
 match mac address IPV4
vlan access-map P2F 12
 action forward
 match mac address IPARP
vlan access-map P2F 20
 action drop
!
vlan filter P2F vlan-list 1

The VLAN1 SVI is also configured with an IPV4 and IPV6 address.

interface Vlan1
 ip address 192.168.1.7 255.255.255.0
 no ip route-cache
 ipv6 address 2001:210:10:1::3/64
 ipv6 enable
end

Problem:
Unable to ping IPV4 hosts connected to the Switch.

3560#ping 192.168.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
3560#ping 192.168.1.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

The ARP Cache in the Switch is populated with correct MAC addresses.

3560#sh ip arp
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  192.168.1.9             8   0016.d3e5.d3cb  ARPA   Vlan1
Internet  192.168.1.1             1   cc00.1da0.0000  ARPA   Vlan1
Internet  192.168.1.2             1   cc01.1da0.0000  ARPA   Vlan1
Internet  192.168.1.7             -   001a.e3b5.0140  ARPA   Vlan1

What is surprising me is I can ping the IPV6 address without any issues.

3560#ping ipv6 2001:210:10:1::1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:210:10:1::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/6/17 ms
3560#ping ipv6 2001:210:10:1::2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:210:10:1::2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/13/33 ms

Why is the sequence #20 in the VLAN access-map not droping the IPV6 frames.
I also configured an explicit drop sequence matching the 0x86DD but nothing changes.

The Software image of the 3560 switch is:
System image file is &quot;flash:c3560-advipservicesk9-mz.122-44.SE2.bin&quot;

Please let me know what am I missing in the configuration?

Thanks in Advance
Sharath</description>
		<content:encoded><![CDATA[<p>Hi Arden,</p>
<p>This was a really helpful guide on Ether Types. But I am really facing some strange issues.</p>
<p>Objective:<br />
I am trying to make vlan 1 an IP only VLAN.</p>
<p>Configuration:<br />
I have configured the following MAC ACLs.</p>
<p>mac access-list extended IEEE_STP<br />
 permit any any lsap 0&#215;4242 0&#215;0</p>
<p>mac access-list extended IPARP<br />
 permit any any 0&#215;806 0&#215;0</p>
<p>mac access-list extended IPV4<br />
 permit any any 0&#215;800 0&#215;0</p>
<p>The following is the VLAN Access Map</p>
<p>vlan access-map P2F 10<br />
 action forward<br />
 match mac address IEEE_STP<br />
vlan access-map P2F 11<br />
 action forward<br />
 match mac address IPV4<br />
vlan access-map P2F 12<br />
 action forward<br />
 match mac address IPARP<br />
vlan access-map P2F 20<br />
 action drop<br />
!<br />
vlan filter P2F vlan-list 1</p>
<p>The VLAN1 SVI is also configured with an IPV4 and IPV6 address.</p>
<p>interface Vlan1<br />
 ip address 192.168.1.7 255.255.255.0<br />
 no ip route-cache<br />
 ipv6 address 2001:210:10:1::3/64<br />
 ipv6 enable<br />
end</p>
<p>Problem:<br />
Unable to ping IPV4 hosts connected to the Switch.</p>
<p>3560#ping 192.168.1.1</p>
<p>Type escape sequence to abort.<br />
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:<br />
&#8230;..<br />
Success rate is 0 percent (0/5)<br />
3560#ping 192.168.1.2</p>
<p>Type escape sequence to abort.<br />
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:<br />
&#8230;..<br />
Success rate is 0 percent (0/5)</p>
<p>The ARP Cache in the Switch is populated with correct MAC addresses.</p>
<p>3560#sh ip arp<br />
Protocol  Address          Age (min)  Hardware Addr   Type   Interface<br />
Internet  192.168.1.9             8   0016.d3e5.d3cb  ARPA   Vlan1<br />
Internet  192.168.1.1             1   cc00.1da0.0000  ARPA   Vlan1<br />
Internet  192.168.1.2             1   cc01.1da0.0000  ARPA   Vlan1<br />
Internet  192.168.1.7             &#8211;   001a.e3b5.0140  ARPA   Vlan1</p>
<p>What is surprising me is I can ping the IPV6 address without any issues.</p>
<p>3560#ping ipv6 2001:210:10:1::1</p>
<p>Type escape sequence to abort.<br />
Sending 5, 100-byte ICMP Echos to 2001:210:10:1::1, timeout is 2 seconds:<br />
!!!!!<br />
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/6/17 ms<br />
3560#ping ipv6 2001:210:10:1::2</p>
<p>Type escape sequence to abort.<br />
Sending 5, 100-byte ICMP Echos to 2001:210:10:1::2, timeout is 2 seconds:<br />
!!!!!<br />
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/13/33 ms</p>
<p>Why is the sequence #20 in the VLAN access-map not droping the IPV6 frames.<br />
I also configured an explicit drop sequence matching the 0&#215;86DD but nothing changes.</p>
<p>The Software image of the 3560 switch is:<br />
System image file is &#8220;flash:c3560-advipservicesk9-mz.122-44.SE2.bin&#8221;</p>
<p>Please let me know what am I missing in the configuration?</p>
<p>Thanks in Advance<br />
Sharath</p>
]]></content:encoded>
	</item>
</channel>
</rss>
