Wireshark-bugs: [Wireshark-bugs] [Bug 5125] New: SEQ/ACK Analysis not working correctly
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5125
Summary: SEQ/ACK Analysis not working correctly
Product: Wireshark
Version: 1.4.0
Platform: x86-64
OS/Version: Windows Server 2008
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: enfiniti27@xxxxxxxxxxx
Build Information:
Version 1.5.0-SVN-33881 (SVN Rev 33881 from /trunk)
This also occurs in 1.4.0rc2 but I installed this to verify the bug still
existed.
--
Problem Description:
=============================
I'm not sure if this is specific to the capture file or not but reproducing the
bug is very strange. I used to be able to open the file and have the SEQ/ACK
analysis work (as can be seen from the screenshots) but after opening it a few
times in a few different ways I am now unable to get it to analyze the file at
all.
I unfortunately can't filter the traffic without it breaking the analysis of
the trace file altogether and I cannot upload the data for security reasons. I
have created screen shots of the "double click" load and the "drag file to
load" methods which are linked below. If there is some specific information
required please let me know and I will try to get you what you need.
Working:
http://i87.photobucket.com/albums/k144/enfiniti27/WiresharkBefore.jpg
Failing:
http://i87.photobucket.com/albums/k144/enfiniti27/WiresharkAfter.jpg
I did notice in the Working scenario that frame #135 was displayed as a
"Malformed Packet" whereas in the failing scenario it appears to have been
parsed correctly.
If you look at the now unmarked frames in the "Failing" trace there is no
"SEQ/ACK Analysis" section on most of the ACK packets that were marked
previously.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
