This is running on Scientific Linux 6.2 (a clone of Redhat Enterprise)
- its not the distributed rpm version that we are using, but compiled
4.1.1 - I wasn't the one who compiled the binary, so I'm not sure what
options, etc. were selected, but can try compiling current and see if
it can be reprodu
Jim Mellander wrote:
Jim> Hi:
Jim> On tcpdump 4.1.1, printing from a saved standard format pcap
Jim> file:
Jim> $ tcpdump -nn -tt -s 0 -r 128.XX.XX.197.icmp.trace |head -3
Jim> reading from file 128.XX.XX.197.icmp.trace, link-type EN10MB
Jim> (Ethernet) 18:45:55.9661231
> The final 3 digits of the timestamp are bogus and always the same
> throughout the run. Since the timestamps are stored in microsecond
> precision, shouldn't the last 3 digits be 0's?
Which OS are you on? Tried this on FreeBSD 8-STABLE, both 32 and 64
bit. Only 6 digits are printed, not 9 - and
Hi:
On tcpdump 4.1.1, printing from a saved standard format pcap file:
$ tcpdump -nn -tt -s 0 -r 128.XX.XX.197.icmp.trace |head -3
reading from file 128.XX.XX.197.icmp.trace, link-type EN10MB (Ethernet)
18:45:55.966123176 IP 128.XX.XX.197 > 78.186.239.143: ICMP host
128.XX.XX.33 unreachable, leng
