public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: tracepath, traceroute and mtr
Date: Fri, 21 May 2021 12:20:50 +0200	[thread overview]
Message-ID: <9588a92b-a891-5003-5b59-0e0251f5d2c9@ipfire.org> (raw)
In-Reply-To: <2E850020-8015-42D2-897D-AA39031326EC@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

Hello Michael,

thanks for your reply.

> Hello,
> 
>> On 21 May 2021, at 10:16, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Hello development folks,
>>
>> for tracing back connections, we currently seem to have multiple utilities available in IPFire 2.x:
>>
>> (a) tracepath, which comes as part of the iputils package
>> (b) traceroute, which can be installed as an add-on
>> (c) mtr, being available as an add-on as well
>>
>> While none of these hurt, I would like to ask for opinions if we can/should drop one of them. Just
>> a minor issue, but having three tools around that basically do the same thing does not really seem to
>> be necessary to me. :-)
> 
> Why are you suddenly in such a mood to drop so much functionality?

Because I accidentally opened the same manpage twice, thinking tracepath and traceroute providing exactly
the same functionality. m(

> traceroute and tracepath do totally different things and we should not drop basic operating system tools.

Yes, I have noticed that as well by now. Sorry for the noise.

Thanks, and best regards,
Peter Müller

      reply	other threads:[~2021-05-21 10:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  9:16 Peter Müller
2021-05-21  9:17 ` Michael Tremer
2021-05-21 10:20   ` Peter Müller [this message]

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=9588a92b-a891-5003-5b59-0e0251f5d2c9@ipfire.org \
    --to=peter.mueller@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