https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4721
Jaap Keuter <jaap.keuter@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #3 from Jaap Keuter <jaap.keuter@xxxxxxxxx> 2010-05-04 07:27:26 CEST ---
(In reply to comment #2)
> Thanks for the information on Bittwist. I was able to get the mac header
> modified with it and it now reads properly in WireShark.
Great!
> Adding this functionality to WireShark would be very handy. I do not get a lot
> of traces like this but I do see them often enough that I get frustrated when I
> need to analyze a trace and the decodes do not work because the mac header is
> not valid.
I never see them fortunately. And yet, it's still better to address this at the
source of the captures.
> Having WireShark ignore the real mac header type field and use whatever you
> decided to put in it instead without actually modifying the trace itself would
> be a more elegant solution.
The question is do we need to modify the file (edit frame contents) or
manipulate dissection? The first option is always considered out-of-scope, the
last one maybe can already be addressed using 'Decode as...', but I haven't
verified if that works in this case as well.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
