Bug ID |
10336
|
Summary |
Statistics ! Conversations ! TCP appears to be broken
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
Git
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
Version 1.99.0-ws (v1.99.0-rc1-1117-gb5f4cb5 from master)
Compiled (32-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
WinPcap (4_1_3), with libz 1.2.5, with GLib 2.38.0, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, with GnuTLS 3.1.22, with Gcrypt 1.6.0, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built Jul 3 2014), with AirPcap.
Running on 32-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), with GnuTLS 3.1.22, with Gcrypt 1.6.0, with AirPcap 4.1.1
build 1838.
Intel(R) Core(TM)2 Duo CPU T5250 @ 1.50GHz, with 3062MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Statistics ! Conversations ! TCP incorrectly shows "Port B" as being the same
as "Port A"
<right-click> ! Prepare a Filter ! ... then generates a filter like the
following
and an error popup appears.
INVALID==172.16.76.116 && tcp.port==32777 && INVALID==172.16.76.115 &&
tcp.port==5100
(IP addresses and TCP ports are correct).
Wireshark 1.12.0 seems OK.
You are receiving this mail because:
- You are watching all bug changes.