https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5770
--- Comment #3 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-03-21 13:21:13 PDT ---
Created an attachment (id=6044)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6044)
Capture file containing ICMP echo request/reply packets.
With the attached patch, all ICMP echo requests/replies are successfully
tracked except for 4 pairs in frames:
1) 39 <--> 42
2) 45 <--> 47
3) 51 <--> 53
4) 57 <--> 59
I have not been able to figure out why those 4 pairs do not track like the
rest. Any ideas?
Some notes about the capture file:
In order to better test the conversation tracking changes, I have multiple
pings going on simultaneously in both directions between a Windows PC and a
Linux PC. The Windows PC is 192.168.4.3 and the Linux PC is 192.168.4.1. A
ping session was initiated on the Windows PC at a cygwin prompt. That can be
seen with id=0x2c12. Pings from the Windows cmd prompt will always carry
id=0x0300, every time pings are started (which I left at the default of 3 pings
per command). The rest of the pings all come from the Linux PC and the id
varies each time a ping session is started (because Linux sticks the process id
of the ping process into that field.)
All 4 of the problematic frames identified above are from the Windows cmd ping.
If the cygwin pings are filtered out, then conversations seem to track fine.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.