Measuring Round Trip Time

You can also use mtping to measure the time it takes for packets to travel from your client workstation, to the remote application, and back again.  In this mode, it will behave and produce output very much like the traditional "ping" utility.  This mode is activated by using the option "-c" and providing a number of times to repeat the test.  Note that the number of tests is approximate and each test may involve the message being repeated multiple times:

host-15: mtping -c 3 DataExpedition.com 8080 ACT_PING dataexpedition.com (70.164.67.132:8080) 0 bytes from 70.164.67.132: count=0 repeats=0 time=60 ms 0 bytes from 70.164.67.132: count=1 repeats=0 time=17 ms 0 bytes from 70.164.67.132: count=2 repeats=0 time=15 ms 0 bytes from 70.164.67.132: count=3 repeats=0 time=17 ms --- dataexpedition.com mtping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 15/27.250/60 ms

Some servers may return a status code with each ping.  The ExpeDat and SyncDat servers, for example, may return their current load.  This feature can be used to monitor server load over time.

host-15: mtping -c 50 DataExpedition.com 8080 ACT_PING DataExpedition.com (70.164.67.132:8080) 0 bytes from 70.164.67.132: count=0 repeats=0 time=17 ms 0 bytes from 70.164.67.132: count=1 repeats=0 time=40 ms rspn=1 0 bytes from 70.164.67.132: count=2 repeats=0 time=45 ms rspn=1 0 bytes from 70.164.67.132: count=3 repeats=0 time=60 ms rspn=2 0 bytes from 70.164.67.132: count=4 repeats=0 time=57 ms rspn=2 0 bytes from 70.164.67.132: count=5 repeats=0 time=63 ms rspn=2 0 bytes from 70.164.67.132: count=6 repeats=0 time=41 ms rspn=1 ...

Only non-zero response values are displayed and the maximum value is 255.