802.1q vlan ids?

[Carter Bullard]

Hey Kevin,
   Yes we're just reporting all 16 bits, as I thought
it would be important to print out all the data.  Knowing
the priority bit might be important, at some point.

   What do you suggest?  We're call it now vlan, I can
leave vlan as both fields, and add vid abd vpri to
the print list to separate the values.  Would this
do it for you?

Carter




> -----Original Message-----
> From: owner-argus-info at lists.andrew.cmu.edu 
> [mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of 
> Kevin C Miller
> Sent: Wednesday, January 29, 2003 10:50 AM
> To: argus-info at lists.andrew.cmu.edu
> Subject: 802.1q vlan ids?
> 
> 
> We were looking into some odd VLAN IDs here (0x2002 when we expected 
> 0x0002). It seems that argus might be misparsing the vlan 
> identifier field. 
> The section of the header used for the vlan ID is 16 bits 
> wide, but the 
> actual VLAN ID is only the low 12 bits:
> 
> See: <http://www.rhyshaden.com/images/eth_c.gif>
> 
> So in this case it seems like we might have a priority of 
> 001, leading to 
> argus reporting a vlan ID of 0x2002.
> 
> Does this seem possible?
> 
> -Kevin
> 
> ---------------------------------------------------
> Kevin C. Miller <kcm at cmu.edu>
> Network Development
> Carnegie Mellon University
>