Hi list,
>Why creating a new dissector for it? Why not extend the 802.1Q dissector?
Good idea.
>0x9100 isn't default, it's just an _example_ value since it's not>registered at IANA. Therefore we cannot create a dissector like this for
>it.
0x9100 is default in the realization of the most important verdors ,such as cisco.
And,what should we do in this situation:
http://www.ethereal.com/lists/ethereal-users/200605/msg00139.htmlRegards.
DuBingyao
2006/6/30, Jaap Keuter <jaap.keuter@xxxxxxxxx>:
On Fri, 30 Jun 2006, [GB2312] ¶Å±ûÒ¢ wrote:
> Hi list,
>
> I write a dessector for 802.1QinQ packets,whose ethertype field values
> is 0x9100 (default). I hope it will be added in the next version.
0x9100 isn't default, it's just an _example_ value since it's not
registered at IANA. Therefore we cannot create a dissector like this for
it.
>
> This attachments are source files.
>
Why creating a new dissector for it? Why not extend the 802.1Q dissector?
>
> Some Requirement:
> http://www.ethereal.com/lists/ethereal-users/200605/msg00142.html
>
> * The IEEE 802.1Q-in-Q VLAN Tag is purpose to expand the VLAN space
> * by tagging the tagged packets,thus producing a "double-tagged" frame.
> * The expanded VLAN space allows the service provider to provide certain
> * services,such as Internet access on specific VLANs for specific customers,
> * and yet still allows the service provider to provide other types of
> * services for their other customers on other VLANs.
>
> Thanks.
> DuBingyao
>
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
