[Jaap Keuter <jaap.keuter@xxxxxxxxx>]

Hi,

Ethertype 9100 isn't a standard type, just one used in the examples of
Foundry networks. So the dissector in Ethereal can't recognize it as a
QinQ tag. It can see nested 8100 tags (standard 802.1Q tags).
The only thing that can be done is create an prefence value for QinQ tags
that the dissector would use to recognize this.

Thanx,
Jaap

On Mon, 15 May 2006, Tim Smith wrote:

> I'm currently sniffing a stream that is using 802.1QinQ tagging.  As long as
> the outer tag is set to 8100 Ethereal seems to parse the packet correctly,
> showing both outer tag & vlan id as well as inner tag and vlan id.  When the
> outer tag is set to 9100, Ethereal displays all remaining information in the
> packet as data.  Has anyone else seen this behavior??   Is there a solution
> that will cause Ethereal to recognize the packet as an 802.1QinQ with a 9100
> outer tag??