I guess this was intentional to make it easier to calculate the averages etc, but we need to have the timeouts in round_trip_ms (multiple loses in a row might indicate something different than one lose every N seconds). Indicate them with 0 or -1. But lose should still not be taken into account when calculating min/max/avg/stdev.
Modification of the result fields:
add round_trip_sent (sent ping requests)
add round_trip_received (received ping replies without lost packets)
This is applicable for Tcp, Udp and System-Ping (the later case might be difficult because a packet loss is not indicated in the output of most ping tools but one has to either parse the sequence numbers or the statistics at the end of the ping-output).
I guess this was intentional to make it easier to calculate the averages etc, but we need to have the timeouts in round_trip_ms (multiple loses in a row might indicate something different than one lose every N seconds). Indicate them with 0 or -1. But lose should still not be taken into account when calculating min/max/avg/stdev.
Modification of the result fields:
This is applicable for Tcp, Udp and System-Ping (the later case might be difficult because a packet loss is not indicated in the output of most ping tools but one has to either parse the sequence numbers or the statistics at the end of the ping-output).