From: Alexander Marx <alexander.marx@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] traceroute: Update to 2.1
Date: Mon, 05 Sep 2016 08:17:30 +0000 [thread overview]
Message-ID: <1473063450-20102-1-git-send-email-alexander.marx@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
The main significant change is new adaptive algorithm for waiting.
Traditional traceroute implementation always waited the whole timeout (default 5.0 second) for any probe.
But if we already have some replies from the same hop, or even from some next hop, we can use the round trip time of such a reply as a hint to determine the actual reasonable amount of time to wait.
Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org>
---
traceroute/traceroute.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/traceroute/traceroute.nm b/traceroute/traceroute.nm
index 5d3a7f8..44c4ecc 100644
--- a/traceroute/traceroute.nm
+++ b/traceroute/traceroute.nm
@@ -4,7 +4,7 @@
###############################################################################
name = traceroute
-version = 2.0.12
+version = 2.1.0
release = 1
groups = Application/Internet
--
2.6.3
reply other threads:[~2016-09-05 8:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473063450-20102-1-git-send-email-alexander.marx@ipfire.org \
--to=alexander.marx@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox