https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5938
Bill Meier <wmeier@xxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #3 from Bill Meier <wmeier@xxxxxxxxxxx> 2011-06-01 16:48:10 EDT ---
(In reply to comment #2)
> This is a problem with the way different length fields are parsed. It comes up
> in other fields too. This is reworked in trunk and trunk-1.6 and seems in
> order.
>
> We need a (reference to) a capture file exposing this bug to test the repair.
The reported issue was, indeed, fixed as part of the enhancement provided in
Bug #5227.
The "Example packet for option 60 changes" file attached to that bug shows the
problem with Wireshark 1.4.6 and is dissected properly with the latest SVN.
So: the upcoming Wireshark 1.6 release will properly dissect this
option/suboption.
I'm closing this bug as "fixed" (altho not actually fixed in Wireshark 1.4...).
The fix was part of a significant enhancement to the bootp dissector.
Significant enhancements aren't normally back-ported so the enhancement won't
be ported back to the Wireshark 1.2... & 1.4... releases.
[A fix just for the bug might be done for Wireshark 1.2 & 1.4 if it's possible
and makes sense and can be done with a simple patch and someone actually
submits such a patch].
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.