> Not sure on the plugin issue, but you may want to consider just adding a
> small amount of support for this to packet-vlan.c, from what I
> understand ISL is _VERY_ similar to 802.1q VLANs.
Similar, but not the same, as far as I know. See
http://www.cisco.com/warp/public/741/4.html
for a discussion of the ISL frame format (it says at the bottom
To inquire about obtaining a license to use this ISL Functional
Specification, please send an e-mail to magaffne@xxxxxxxxx.
but I don't know whether "use" just means "send and receive ISL frames",
or if it includes "dissect ISL frames in a network analyzer" - perhaps
all the different commercial network analyzer vendors who say they
handle ISL had to license it from Cisco, but I'm not sure it'd be in
Cisco's best interest to require that you license it for a *dissector*;
I'd see that being something they'd want makers of switches, protocol
stack software, etc. to license), and see
http://www.cisco.com/univercd/cc/td/doc/product/lan/trsrb/frames.htm#xtocid842874
for information on a Token Ring variant thereof (although I'm probably
counting something wrong, as that page claims
In addition to the fields found in the original ISL frame
format, the ISL Token Ring Frame format includes:
o An extra 6 byte header.
but looking at the two pages in question, I see only 5 added bytes after
the regular ISL header).
