Wireshark-bugs: [Wireshark-bugs] [Bug 5601] "Follow TCP stream" failed to filter out the tcp in
Date: Sun, 23 Jan 2011 06:03:34 -0800 (PST)

--- Comment #2 from Yang Shen <[email protected]> 2011-01-23 06:03:28 PST ---
Yes, I am using a customized version, and I get the same issue when I used a
common version.

If you would like take 1 minutes to open the attachment, I think you will know
what I said. Thanks.

(In reply to comment #1)
> (In reply to comment #0)
> > Created an attachment (id=5756)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5756) [details]
> > The failed pcap file.
> > 
> > Build Information:
> > Version 1.4.2-Spirent (SVN Rev 34981 from /releases/wireshark-1.4.2)
> Are you running a customized version of Wireshark? If so, please use an
> automated build on your capture file to check whether the problem does exist in
> the Wireshark code or the customizations...
> > When right-click and "Follow TCP stream", Wireshark identify the TCP as 2 TCP.
> > But I can confirm it is really one TCP.
> What exactly do you mean with "Identify the TCP as 2 TCP" and "it is really one
> TCP"?
> > Another issue is when enable "Analyze TCP seq number", it failed and mark the
> > wrong seq number on the 4th packets in the attachment.
> What is wrong with the seq in the 4th packet? It looks fine in my version of
> Wireshark (1.5.0 SVN 35073).
> Cheers, Sake

Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.