[11820] in bugtraq

home help back first fref pref prev next nref lref last post

the morning after: VLAN Security

daemon@ATHENA.MIT.EDU (llynch@JORSM.COM)
Fri Sep 10 13:31:02 1999

Message-Id:  <19990908032713.28351.qmail@securityfocus.com>
Date:         Wed, 8 Sep 1999 03:27:13 -0000
Reply-To: llynch@JORSM.COM
From: llynch@JORSM.COM
X-To:         bugtraq@securityfocus.com
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To:  <Pine.BSF.3.96.990903214623.4067A-100000@peabody>


>>The following is a stereo (2 Mikes) message
>>[Mike <A 
HREF="mailto:S=strange@cultural.com">S=strange@cultural.com<
/A> -
>>Mike <A 
HREF="mailto:F=frantzen@expert.cc.purdue.edu">F=frantzen@exp
ert.cc.purdue.edu</A>]....

>>[Mike F:]
>>I tested this feature on a 2924 Enterprise switch with a 
Cisco 2514 
>>(IOS 12.0 IP Enterprise feature set) recently, and it 
appears indeed
>>to provide protection against directly writing to the MAC 
of the target.
>>

Pretty good for having blading on the brain... 
If I recall correctly, 2514's are unable to support 
Trunking.  So it was a
Cisco 45xx with FastEthernet card, but you already knew 
that.  Just trying
to confuse us, once again, I see...

-LLL

>>To further confuse the reader, I must point out that the 
802.10 frame spec
>>(for use on the trunk line) includes a boolean flag for 
fragmented ether
>>frames.  Cisco's documentation claims to ignore the 
fragmentation field...
>>
>>I'm going roller blading now :)
>>
>>.....
>>
>>[Mike S]:
>>And there you have it.
>>
>>      -MS


home help back first fref pref prev next nref lref last post