Talk:Traceroute

From Wikipedia, the free encyclopedia

The information on this page is a bit mixed up. It might take some work to sort out all the small discrepancies here. Kim Bruning 07:55, 4 Aug 2004 (UTC)

As to images, hmm, anyone up for an xtraceroute screenshot? For some reason my xtraceroute database sucks. I wonder if anyone has a nicer one to make a decent image with ;-) Kim Bruning 12:41, 30 Aug 2004 (UTC)

[edit] Matt's Trace Route

There is an article on mtr, "Matt's Trace Route," which should be merged into the traceroute article as a new section unless there's some compelling reason to keep the information in two unsynchronized places. (Or unless, of course, "Matt's Trace Route" turns out to be unencyclopedic; but apparently a bunch of Linux sysadmins use it, so I reserve judgment on that point.) --Quuxplusone 05:10, 21 April 2006 (UTC)

--Dissagree-- No don't do that, tracrt and mtr are completly different tools (they share some similarities in functionality) just reference each of them on both pages

--Disagree-- I concur with the above editor.Shouta 09:54, 4 May 2006 (UTC)

--Disagree-- Functionality is different, btw as one of those Linux sysadmins I recomend this tool as a replacement to tregular traceroute. Htaccess 13:50, 4 May 2006 (UTC)

--Agree-- The functionality is the same, MTR just adds another element (ping) after the initial traceroute. Note MTR often results in poor data, since it probes based on data going "to" the router (slow path / control-plane data which is usually heavily rate limited and cpu processed), not data going "through" the router. Take any such data with a grain of salt, or be prepared to be confused. Humble226 08:18, 8 July 2006 (UTC)

[edit] correct title

Why should the first letter not be capitalized if the name of the program is not traceroute? Mace 11:10, 12 November 2006 (UTC)