ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 5601] "Follow TCP stream" failed to filter out the tcp in

Date: Fri, 21 Jan 2011 10:14:03 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5601

--- Comment #1 from Sake <sake@xxxxxxxxxx> 2011-01-21 10:14:02 PST ---
(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.