Troubleshooting with Traceroute

Troubleshooting with Traceroute

See: http://en.wikipedia.org/wiki/Traceroute

traceroute is a computer network tool used to determine the route taken by packets across an IP network.

Traceroute works by increasing the "time-to-live" value of each successive batch of packets sent. The first three packets sent have a time-to-live (TTL) value of one (implying that they are not forwarded by the next router and make only a single hop). The next three packets have a TTL value of 2, and so on. When a packet passes through a host, normally the host decrements the TTL value by one, and forwards the packet to the next host. When a packet with a TTL of one reaches a host, the host discards the packet and sends an ICMP time exceeded (type 11) packet to the sender. The traceroute utility uses these returning packets to produce a list of hosts that the packets have traversed en route to the destination. The three timestamp values returned for each host along the path are the delay (aka latency) values typically in milliseconds (ms) for each packet in the batch. If a packet does not return within the expected timeout window, a star (asterisk) is traditionally printed. Traceroute may not list the real hosts. It indicates that the first host is at one hop, the second host at two hops, etc. IP does not guarantee that all the packets take the same route. Also note that if the host at hop number N does not reply, the hop will be skipped in the output.

On modern Unix and Linux-based operating systems, the traceroute utility by default uses UDP datagrams with destination ports number from 33434 to 33534. The traceroute utility usually has an option to specify use of ICMP echo request (type 8) instead, as used by the Windows tracert utility. If you have a firewall and if you want traceroute to work from both machines (Unix/Linux and Windows) you will need to allow both protocols inbound through your firewall (UDP with ports from 33434 to 33534 and ICMP type 8).

Issues with traceroute as a diagnostic tool

  • Return path to the traceroute originator is unknown. To test both directions, you must retrieve a traceroute where your destination is the source and your source is the destination.
  • Routers control planes may treat TTL exceeded message generation as low priority. This can sometimes causes the appearance of packet loss or congestion in the middle of a traceroute that is misunderstood. If packet loss is not represented by the final hop, packet loss or congestion in the middle is generally not a concern and is an artifact of the traceroute process.
MTR is a handy traceroute implementation. MTR runs a continuous traceroute, which is very useful.

See: http://en.wikipedia.org/wiki/My_Trace_Route




Keywords:Troubleshooting with Traceroute   Doc ID:41690
Owner:Michael H.Group:University of Wisconsin System Network
Created:2014-07-08 09:47 CSTUpdated:2017-06-06 07:51 CST
Sites:University of Wisconsin System Network
Feedback:  1   0