Difference between revisions of "Traceroute"
| Line 29: | Line 29: | ||
This example shows 3 trace packets being sent, resulting in 3 columns of time between each hop. When the trace fails to reach its destination or expires, an asterisk appears in the appropriate column. Also note that in this example, there are 11 hops with the first being the router and the last being the destination (google.com). | This example shows 3 trace packets being sent, resulting in 3 columns of time between each hop. When the trace fails to reach its destination or expires, an asterisk appears in the appropriate column. Also note that in this example, there are 11 hops with the first being the router and the last being the destination (google.com). | ||
| − | =Options for Tracert= | + | ==Options for Tracert== |
* -d | * -d | ||
** Do not resolve addresses of router interfaces to host names. | ** Do not resolve addresses of router interfaces to host names. | ||
| Line 48: | Line 48: | ||
** Force IPV6 | ** Force IPV6 | ||
| + | ==Example of Traceroute== | ||
| + | {{LinuxCMD|traceroute domain.com}} | ||
| + | ==Options for Traceroute== | ||
[[Category:Protocols]] | [[Category:Protocols]] | ||
Revision as of 16:34, 2 May 2012
| This article contains too little information, it should be expanded or updated. |
|---|
Things you can do to help:
|
Traceroute is a command-line tool that can be used to identify all of the routing hops between two hosts by intentionally exceeding response time from every gateway to a destination. It's usefulness is shown when you need to find an intermediate server for information gathering, or for checking where in a network a site is failing or bottlenecking.
Contents
Performing a Traceroute
To perform from windows: from a command prompt type
| C:\WINDOWS\System32\cmd.exe |
| C:\WINDOWS\> tracert domain.com |
To perform in a Linux/Unix Terminal type
| Terminal |
| localhost:~ $ traceroute domain.com |
Example of Tracert
| C:\WINDOWS\System32\cmd.exe |
| C:\WINDOWS\> tracert google.com
Tracing route to google.com [74.125.237.9] over a maximum of 30 hops: 1 6 ms 4 ms 1 ms 192.168.0.1 2 49 ms 33 ms 40 ms 123.123.123.123 3 84 ms 173 ms 107 ms 172.11.11.11 4 43 ms 84 ms 57 ms 172.22.22.22 5 * 70 ms 136 ms 110.110.110.110 6 86 ms 31 ms 33 ms 203.203.11.11 7 170 ms * 83 ms 203.203.22.22 8 117 ms 68 ms 88 ms 74.125.50.1 9 109 ms 69 ms 73 ms 66.249.50.1 10 85 ms 73 ms 152 ms 72.14.237.47 11 * 123 ms 107 ms 74.125.237.9Trace complete. |
This example shows 3 trace packets being sent, resulting in 3 columns of time between each hop. When the trace fails to reach its destination or expires, an asterisk appears in the appropriate column. Also note that in this example, there are 11 hops with the first being the router and the last being the destination (google.com).
Options for Tracert
- -d
- Do not resolve addresses of router interfaces to host names.
E.g: wwwcomcast-vip.westchester.pa.bo.comcast.net [69.241.45.4] becomes 69.241.45.4.
- -h < maximum_hops >
- Limits number of hops to get to the specified domain.
- -j < host_list >
- Loose source routing along the host-list (IPV4-only).
- -w < timeout >
- Wait timeout milliseconds for each reply.
- -R
- Trace round-trip path (IPV6-only).
- -S < srcaddr >
- Source address to use (IPV6-only).
- -4
- Force IPV4
- -6
- Force IPV6
Example of Traceroute
| Terminal |
| localhost:~ $ traceroute domain.com |
