You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the round ends due to timeout on max_round_duration without finding the target, only the Probe which responded are published and so the statistics for all other Probe in the round are not updated. Notably, this includes the sent count and so this leads to a "tearing" effect whereby the sent count is not consistent for all hops in the trace.
The text was updated successfully, but these errors were encountered:
The fix is to separate out the size of a round (the number of probes sent in the round, for which statistics should always be updated) from the maximum ttl number of the probe which responded in this round (which can be used to decide how many probes to display).
The "tearing" effect is still possible, though unlikely; if the number of probes actually sent in a round is less than the maximum ttl number of a probe which responded in a previous round.
For example, in round 1 we sent 10 probes (ttl1..10) and received a response for, at least, the probe with ttl=10. In round 2 we only manage to send 9 probes (ttl1..9) before the round expires and so only probes with ttl1..9 are published in round 2 and therefore the stats for ttl=10 will be behind the rest.
The latter problem could potentially be fixed by adjusting the round end logic to ensure round N+1 sends at last as many probes as round N.
When the round ends due to timeout on
max_round_duration
without finding the target, only theProbe
which responded are published and so the statistics for all otherProbe
in the round are not updated. Notably, this includes thesent
count and so this leads to a "tearing" effect whereby thesent
count is not consistent for all hops in the trace.The text was updated successfully, but these errors were encountered: