Wireshark-bugs: [Wireshark-bugs] [Bug 9522] New: Expert Infos: TCP Out-of-order segment warning:

Date: Sat, 07 Dec 2013 01:11:39 +0000
Bug ID 9522
Summary Expert Infos: TCP Out-of-order segment warning: packets are sorted incorrectly
Classification Unclassified
Product Wireshark
Version 1.10.3
Hardware x86
OS All
Status UNCONFIRMED
Severity Normal
Priority Low
Component Wireshark
Assignee [email protected]
Reporter [email protected]

Created attachment 12254 [details]
Screen dump of problem

Build Information:
Version 1.10.3 (SVN Rev 53022 from /trunk-1.10)

Copyright 1998-2013 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Nov  1 2013), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
       Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, with 8117MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
In Wireshark, open a packet trace of 1M packets of TCP (iSCSI) traffic over
IPv6. 

Expert Infos: 
Out-of-order segments warning:  The list of packets is not sorted by
frame number.  (I tried 100K packets and it was ok.  But 1M fails.)

I have only seen this problem for Out-of-order, and not for the other warnings.

Let me know if I need to submit a pkt trace file.

KH


You are receiving this mail because:
  • You are watching all bug changes.