last-mile latency measurement: traceroute+ping version #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds task `lml-traceroute` (executable `netrics-lml-traceroute`). This task mirrors the `lml-scamper` version already published. It differs in that the endpoint is traced with `traceroute` and then `ping`'d; (and, traceroute output must be specially parsed, which is relatively laborious). As with `lml-scamper`, for speed and niceness, `lml-traceroute` will randomly select an endpoint to trace, from a default set of Google DNS as well as CloudFlare DNS. (The former is generally speedier to respond; regardless, it might be "nice" to round-robin, and for that matter to fall back in the event of response failure.) completes #25 part of #11 part of #3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds task
lml-traceroute(executablenetrics-lml-traceroute).This task mirrors the
lml-scamperversion already published. Itdiffers in that the endpoint is traced with
tracerouteand thenping'd; (and, traceroute output must be specially parsed, which isrelatively laborious).
As with
lml-scamper, for speed and niceness,lml-traceroutewillrandomly select an endpoint to trace, from a default set of Google DNS
as well as CloudFlare DNS. (The former is generally speedier to respond;
regardless, it might be "nice" to round-robin, and for that matter to
fall back in the event of response failure.)
(Also factors ping result-parsing to common module.)
completes #25
part of #11
part of #3