Traceroute: Difference between revisions
Jump to navigation
Jump to search
imported>Howard C. Berkowitz No edit summary |
mNo edit summary |
||
(One intermediate revision by one other user not shown) | |||
Line 11: | Line 11: | ||
| title = Tutorial: How to Accurately Interpret Traceroute Results | | title = Tutorial: How to Accurately Interpret Traceroute Results | ||
| author = Richard Steenbergen |date = 25 January 2009 | | author = Richard Steenbergen |date = 25 January 2009 | ||
| publisher = | | 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. | }}</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== | ==Theory of operation== | ||
Line 17: | Line 17: | ||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
[[Category:Suggestion Bot Tag]] |
Latest revision as of 06:00, 30 October 2024
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
- ↑ G. Malkin (January 1993), Traceroute Using an IP Option, Internet Engineering Task Force, RFC1393
- ↑ Richard Steenbergen (25 January 2009), Tutorial: How to Accurately Interpret Traceroute Results, North American Network Operators Group