Traceroute: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Howard C. Berkowitz
(New article generated using Special:MetadataForm)
 
imported>Howard C. Berkowitz
No edit summary
 
Line 1: Line 1:
{{subpages}}
{{subpages}}
An extensively used [[internet operations]] tool, introduced in 1993, <ref>{{citation
|  author = G. Malkin
| id = RFC1393                     
| date = January 1993
| title = Traceroute Using an IP Option
| publisher = [[Internet Engineering Task Force]]
| url = http://www.ietf.org/rfc/rfc1393.txt
}}</ref> '''traceroute''' attempts to determine the hop-by-hop [[routing]] [[connectivity]] between two Internet addreses, or shed light on where connectivity fails. It is often used as a way to estimate network performance, but the user must know its limitations for this purpose, and how to interpret sometimes subtle anomalies.<ref>{{citation
| url = http://www.nanog.org/meetings/nanog45/abstracts.php?pt=MTE4NSZuYW5vZzQ1&nm=nanog45
| title = Tutorial: How to Accurately Interpret Traceroute Results
| author = Richard Steenbergen |date = 25 January 2009
| publisher = [[North American Network Operators Group]]
}}</ref> For example, the sum of hop-by-hop delays between two points may differ from the delay reported by the [[ping]] tool, because both ping and traceroute use different protocols, and router designers handle these differently.
==Theory of operation==
==Factors influencing results==
==References==
{{reflist}}

Latest revision as of 19:17, 2 October 2010

This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
This editable Main Article is under development and subject to a disclaimer.

An extensively used internet operations tool, introduced in 1993, [1] traceroute attempts to determine the hop-by-hop routing connectivity between two Internet addreses, or shed light on where connectivity fails. It is often used as a way to estimate network performance, but the user must know its limitations for this purpose, and how to interpret sometimes subtle anomalies.[2] For example, the sum of hop-by-hop delays between two points may differ from the delay reported by the ping tool, because both ping and traceroute use different protocols, and router designers handle these differently.

Theory of operation

Factors influencing results

References