Christopher Maynard
changed
bug 11414
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
CONFIRMED
|
| Ever confirmed |
|
1
|
Comment # 4
on bug 11414
from Christopher Maynard
Quite easy to replicate actually. On Windows, I ran "ping -n 1 <host>" while
capturing ICMP traffic to/from that host.
Initially the 1st frame captured (the ICMP echo request packet) showed
consistency between the ICMP packet details and the Info column - both
indicating:
"[No response seen]/(no response found!)" <== speaking of, it might be
nicer to show a more consistent message here.
After selecting frame #2 (the ICMP echo reply packet, which did indicat
"[Request frame: 1]/(request in 1)") and then selecting frame #1 again, the
ICMP packet details changed to "[Response frame: 2]" but the Info column
remained as, "(no response found!)".
On my system, this didn't happen every time though, but it seemed to
consistently happen every *other* time, so it was easy to reproduce with a
Wireshark capture restart followed by the ping command again.
You are receiving this mail because:
- You are watching all bug changes.