Bug ID |
12022
|
Summary |
wrong tcp stream with a tcp port numbers reused after a TCP/RST
|
Product |
Wireshark
|
Version |
2.1.x (Experimental)
|
Hardware |
x86-64
|
OS |
Windows 7
|
Status |
CONFIRMED
|
Severity |
Normal
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 14250 [details]
full packet capture with two tcp strem mixed together
Build Information:
Version 2.1.0-1522-g6ef2b48 (v2.1.0rc0-1522-g6ef2b48 from master)
Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (with SSE4.2), with 15779MB of
physical
memory.
Built using Microsoft Visual C++ 12.0 build 31101
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
I was working on a big packet capture with a lot of tcp port numbers reused and
I noticed that there was a problem with the tcp.stream.
Server to client packets from the next TCP connection are binded the previous
one, previously closed by a reset.
I didn't find any similar issue already reported.
You are receiving this mail because:
- You are watching all bug changes.