Wireshark-bugs: [Wireshark-bugs] [Bug 11414] Match conversation tracking on ICMP

Date: Mon, 03 Aug 2015 18:05:54 +0000

Comment # 2 on bug 11414 from
(In reply to Pascal Quantin from comment #1)
> I guess there is no guarantee that a given packet will be analyzed several
> times during a live capture. This would explain why you get the proper
> decoding when opening the pcap file later on (as here multiple passes for
> request / response tracking is done for each packet).

Although the screen shot doesn't show it, it is claimed in comment 0 that:

> what's more in the ICMP of the frame, Wireshark even created a link to the 
> corresponding frame (Reply/Request).

This seems to be indicating that the "Response To" and "Reply In" are correct
in the ICMP packet details during the live capturing, but for some reason the
column information isn't being properly updated for all frames.  If the ICMP
packet details didn't have the request/response tracking information, then it
would make sense to me, but there is an apparent inconsistency here regarding
the Info column.

Is there an updated screen shot showing the "no response found!" in the Info
column but that also shows the expanded ICMP details with the "Request frame:
<N>" details?

See also:
https://ask.wireshark.org/questions/44766/why-wireshark-could-not-match-my-ping-respond-to-the-request


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