From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: tracepath, traceroute and mtr Date: Fri, 21 May 2021 12:20:50 +0200 Message-ID: <9588a92b-a891-5003-5b59-0e0251f5d2c9@ipfire.org> In-Reply-To: <2E850020-8015-42D2-897D-AA39031326EC@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1504678660664759338==" List-Id: --===============1504678660664759338== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Michael, thanks for your reply. > Hello, >=20 >> On 21 May 2021, at 10:16, Peter M=C3=BCller w= rote: >> >> 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/shoul= d drop one of them. Just >> a minor issue, but having three tools around that basically do the same th= ing does not really seem to >> be necessary to me. :-) >=20 > 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=C3=BCller --===============1504678660664759338==--