Bug ID |
11414
|
Summary |
Match conversation tracking on ICMP
|
Product |
Wireshark
|
Version |
1.12.4
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Capture file support (libwiretap)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 13770 [details]
capture file and screenshot
Build Information:
Version 1.12.4 (v1.12.4-0-gb4861da from master-1.12)
Copyright 1998-2015 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.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 4 2015),
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 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, with 8105MB 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.
--
Wireshark sais the Ping requests 4 and 7 do not match (Echo (ping) request ...
etc ... no response found). I could not find anything wrong on my frames,
what's more in the ICMP of the frame, Wireshark even created a link to the
corresponding frame (Reply/Request).
I tried to prepare a .pcapng for you but then realized that on opening that
file, "no response found" has dissappeared.
Attachment:
- capture file showing the ping. On ping request 4 (frame number 9) and 7
(frame number 15) it said (no response found) in the "Info" column.
- screenshot showing live capture. The issue appears on frame no. 3
You are receiving this mail because:
- You are watching all bug changes.