Ethereal-users: Re: [ethereal-users] Sniffing 802.1Q connections

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Gilbert Ramirez <gram@xxxxxxxxxx>
Date: Wed, 5 Jul 2000 09:55:44 -0500
On Mon, Jul 03, 2000 at 04:25:19PM -0500, Brian Capouch wrote:
> 
> 
> This is more an informational question unless the behavior I'm about to
> describe is identified by a cheese as being a bug.
> 
> Just for s & g, I brought up a couple of Linux boxes using VLANS.  I
> stuck ethereal on the connection, and it nicely decoded the VLAN tag,
> FOR ONE SIDE.
> 
> It identified and displayed the VLAN stuff correctly for the side of the
> connection that was on the host doing the sniffing, but couldn't see it
> (i.e. no 802.1Q stuff anywhere in the packet info) for the other side.

So, you say that there were packets that were not correctly interpreted
by Ethereal? Or perhaps Ethereal needs a special heuristic to identify these
packets? If so, please send a small trace to ethereal-dev@xxxxxxxx and
we'll try our best to make it work.

--gilbert