prestoja1701 / paping

Automatically exported from code.google.com/p/paping
MIT License
0 stars 0 forks source link

Wrong average time calculation on connection timeouts #19

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. ping a server with connection drops (socket timeouts)
2. take a look at the averages
3.

What is the expected output? What do you see instead?

$ paping news.php.net -p 119 -c 10
paping v1.5.5 - Copyright (c) 2011 Mike Lovell

Connecting to pair1.php.net [76.75.200.58] on TCP 119:

Connected to 76.75.200.58: time=114.25ms protocol=TCP port=119
Connection timed out
Connected to 76.75.200.58: time=113.37ms protocol=TCP port=119
Connection timed out
Connected to 76.75.200.58: time=113.92ms protocol=TCP port=119
Connection timed out
Connected to 76.75.200.58: time=113.53ms protocol=TCP port=119
Connection timed out
Connected to 76.75.200.58: time=115.17ms protocol=TCP port=119
Connection timed out

Connection statistics:
    Attempted = 10, Connected = 5, Failed = 5 (50.00%)
Approximate connection times:
    Minimum = 113.37ms, Maximum = 115.17ms, Average = 57.02ms

The average is below the minimum. That should not happen in my universe ;)

What version of the product are you using? On what operating system?
Fedora Linux 20, x86_64

Please provide any additional information below.
Lots of TCP retransmission (seems to be a level3 problem).

Original issue reported on code.google.com by phga...@googlemail.com on 19 Jul 2014 at 4:12