Talk:Traceroute
From Wikipedia, the free encyclopedia
traceroute.org isn't updated for a lot of years, half of links are dead and his maintainer takes care of it ! —Preceding unsigned comment added by 91.163.173.59 (talk) 23:23, 14 January 2008 (UTC)
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)
--Disagree-- traceroute is a traditional Unix command, there are dozens of "improved" versions out there, let's not mention them all in the article. Jaho 04:43, 17 March 2007 (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)
Because Unix-like operating systems distinguish between upper and lower case in filenames. Typing "Traceroute" in stead of "traceroute" results in a "command not found" error. Jaho 04:12, 17 March 2007 (UTC)
[edit] Security concerns
"For these reasons, while traceroute was widely used during the early days of Internet, by the 1990s many Internet sites have blocked traceroute requests"
This is somewhat deceptive, as there's no way to directly block traceroute requests, since traceroute just uses one of the standard network protocols (usually UDP, ICMP, or TCP). UDP-based traceroutes merely rely on the the hops and destination hosts sending ICMP_TIME_EXCEEDED and ICMP_PORT_UNREACHABLE, respectively. Standard UNIX traceroute also implements ICMP-based traceroute which uses ICMP ECHO instead of UDP. As mentioned in the article, some traceroutes use TCP.
The quoted text above oversimplifies what would be required to "block" traceroute requests (if it's even really feasible) and is thus deceptive. —Preceding unsigned comment added by Ramorum (talk • contribs) 23:41, 5 February 2008 (UTC)
