https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4721
Sake <sake@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
--- Comment #6 from Sake <sake@xxxxxxxxxx> 2010-05-08 01:01:20 PDT ---
(In reply to comment #5)
> So I guess there is a little bug in the code that decides whether "Decode
> As..." should be greyed out or not. I'll have a look...
I checked in a fix that enables "Decode As..." for ethertype 0x0000 (SVN
32723).
However, looking deeper into your trace, this will not solve your issue, as it
seems the ethertype field can have random content in your case.
There is a way with wireshark to do what you want. You must change the link
layer type of the file to one of the DLT_USER values (this can be done with
editcap). Then you can use the DLT_USER prorocol preferences to tell wireshark
to skip XXX bytes and start decoding the resulting data as protocol YYY. But
then I guess using bittwiste is a little more convenient ;-)
Closing the bug as FIXED, as "decode as" can now be used on ethertype 0x0000
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
