On Fri, Oct 19, 2001 at 04:25:57PM -0500, Nathaniel Couper-Noles wrote: > Is there a way to cause tcpdump to spit out the icmp sequence number of > icmp echo and icmp echo reply messages?
Yes - apply your patch, and recompile. > I can think of a near-trivial change to print-icmp.c to force it, but > I was wondering if I'm missing something and the sequence number is > already in there.... You're not. Output of "tcpdump -v", without your patch, with one capture file I have: 01:34:06.628663 10.10.10.16 > wwwweast2.usec.Sun.COM: icmp: echo request (ttl 255, id 16898, len 84) 01:34:07.623620 10.10.10.16 > wwwweast2.usec.Sun.COM: icmp: echo request (ttl 255, id 16899, len 84) 01:34:07.708454 wwwweast2.usec.Sun.COM > 10.10.10.16: icmp: echo reply (DF) (ttl 241, id 13032, len 84) Output with your patch: 01:34:06.628663 10.10.10.16 > wwwweast2.usec.Sun.COM: icmp: echo request seq 0 (ttl 255, id 16898, len 84) 01:34:07.623620 10.10.10.16 > wwwweast2.usec.Sun.COM: icmp: echo request seq 1 (ttl 255, id 16899, len 84) 01:34:07.708454 wwwweast2.usec.Sun.COM > 10.10.10.16: icmp: echo reply seq 1 (DF) (ttl 241, id 13032, len 84) I've checked it in, with a change to add TCHECK() calls before printing the sequence number, to make sure the sequence number is actually in the packet. - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
