Some packets are reported with negative intervals, example output at
bottom. These are clearly not correct. Version 1.13.
tping.exe -n 10 -w 1 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data from [192.168.1.111]:
Reply from 192.168.1.1: bytes=32 time 0.64 ms, TTL=64, Hop=0, Jitter=0.00
ms
Request timed out.
Reply from 192.168.1.1: bytes=32 time 0.57 ms, TTL=64, Hop=0, Jitter=0.00
ms
Reply from 192.168.1.1: bytes=32 time 0.95 ms, TTL=64, Hop=0, Jitter=0.03
ms
Reply from 192.168.1.1: bytes=32 time 1.95 ms, TTL=64, Hop=0, Jitter=0.09
ms
Reply from 192.168.1.1: bytes=32 time -145.57 ms, TTL=64, Hop=0,
Jitter=0.09 ms
Reply from 192.168.1.1: bytes=32 time 1.93 ms, TTL=64, Hop=0, Jitter=0.09
ms
Reply from 192.168.1.1: bytes=32 time 0.95 ms, TTL=64, Hop=0, Jitter=0.14
ms
Reply from 192.168.1.1: bytes=32 time 1.93 ms, TTL=64, Hop=0, Jitter=0.20
ms
Reply from 192.168.1.1: bytes=32 time 0.95 ms, TTL=64, Hop=0, Jitter=0.25
ms
Ping statistics for 192.168.1.1
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 0.95ms, Maximum = 1.93ms, Average = 0.64ms, Jitter
Statistical = 51.70ms
The jitter values around the 6th ping are all 0.09ms, which conflicts with
my understanding of the algorithm. The minimum doesn't appear to reflect
that ping. The average doesn't match any possibility that I can come up
with.
wcoole@aperiogroup.com
Nobody/Anonymous ( nobody ) - 2007-10-25 18:46
5
Open
None
Nobody/Anonymous
None
None
Public