Cal Turney
changed
bug 5651
| What |
Removed |
Added |
| Status |
RESOLVED
|
CONFIRMED
|
| Resolution |
NOTABUG
|
---
|
Comment # 9
on bug 5651
from Cal Turney
(In reply to comment #8)
> (In reply to comment #7)
> Over the past months I have heavily modified the
> TCP dissector and the issue
> that I reported here has been resolved in a
> completely different manner. I
> will submit those enhancements and bug
> fixes after my group has thoroughly
> tested them.
Hi Cal. Can you explain
> how this issue has been resolved, as it seems to still exist in Version
> 1.10.2. Perhaps the enhancements to which you refer have not yet made it to
> the stable release code. If so, can you tell me which version does contain
> them? Thanks very much.
Hi Larry. I resolved this issue in my own version of the code and then spent at
least a year adding many improvements, statistics, and a few bug fixes to the
TCP dissector. I wanted my group to test them but by the time that was done to
my satisfaction, the latest version of the TCP dissector had changed so much I
realized that porting my stuff would be a monumental job. Because there were
so many problems with the NFSv4, iSCSI, and SMB2 dissectors; and bugs in the
preferences routines I spent my time there and except for SMB2, I've submitted
most of those changes. I plan to start checking in my TCP changes as soon as I
finish working on the SMB2 dissector and have submitted all those changes.
Now, to answer your question, I decided to close this bug report because I
thought I would be able to submit all the TCP fixes in a timely fashion. I've
reopened 5651 and will try to check in a patch ASAP. I will also submit it to
be backported to v1.10.
You are receiving this mail because:
- You are the assignee for the bug.
- You are watching all bug changes.
