183
edits
Path measurement: Difference between revisions
m
→Two-Way-Latency: language improvements
m (→Two-Way-Latency: language improvements) |
|||
| Line 126: | Line 126: | ||
It cannot (due to asynchronous local time sources) measure the one-way latency of a single packet but only the duration of packets going in both directions. | It cannot (due to asynchronous local time sources) measure the one-way latency of a single packet but only the duration of packets going in both directions. | ||
Example: Assume a packet A is seen from main to remote device and another packet B is seen from remote to main device. | Example: Assume a packet A is seen from main to remote device and another packet B is seen from remote to main device. | ||
The time difference when packet A is seen on main and on remote device plus the time difference of packet B being seen on remote and main device is taken into account to determine the two-way latency. Packet A and packet B | The time difference when packet A is seen on main and on remote device plus the time difference of packet B being seen on remote and main device is taken into account to determine the two-way latency. Packet A and packet B do not need to be related in any way. | ||
If traffic is going only in one direction, the measurement will not show any time result (even though packet loss is still visible). | If traffic is going only in one direction, the measurement will not show any time result (even though packet loss is still visible). | ||
For each second, the average, minimum, and maximum two-way-latency is accounted and shown the graph. | For each second, the average, minimum, and maximum two-way-latency is accounted and shown in the graph. | ||
To the left of the graph the statistics for the visible time range is shown, changing the zoom level or time interval will update the values accordingly. | To the left of the graph the statistics for the visible time range is shown, changing the zoom level or time interval will update the values accordingly. | ||