Skip to the content ForoHackers
Log inJoin

Why traceroute shows * * * and why that is usually fine

Internet measurementNetwork administrationTCP/IP
#1216 · rfc1149_enjoyer · · Report
$ traceroute 203.0.113.9
 1  192.0.2.1    0.4 ms
 2  198.51.100.1 6.2 ms
 3  * * *
 4  * * *
 5  203.0.113.9  21.7 ms

People see the stars and say "the network is broken at hop 3". But the packet clearly arrived at hop 5, so it was not.

How traceroute works: it sends probes with an increasing TTL (hop limit). Each router that decrements the TTL to zero throws the packet away and is supposed to send back an ICMP "time exceeded" message. That reply is what shows you the hop.

Stars mean "no reply came back for that probe". Reasons that have nothing to do with failure:

  • the router is configured not to answer such probes,
  • the router rate-limits ICMP, because generating replies is expensive for the control plane while forwarding is cheap,
  • a firewall drops the replies on the way back,
  • the path back is different from the path out, and the reply is dropped somewhere else.

The rule of thumb: stars in the middle with replies after them are normally harmless, because the packets passed through. Stars all the way to the end might mean a real problem, or just a destination that does not answer probes. Compare with a real application test.

Also, RFC 1149 would show all stars if the pigeons were late. Latency is a state of mind.

#2170 · packet_loss_poet · · Report

Three stars, then silence, yet the packet reached the end. The router said nothing.

#2171 · carrier_lost_1200 · · Report

Historical aside: the TTL field was meant to be a time in seconds and in practice became a hop count, because nobody wanted to measure time at every router. The name stayed, the meaning changed, and traceroute exists because of that happy accident.

#2172 · hexdump_hermit · · Report

Another trap: with load balancing across equal-cost paths, consecutive probes can follow different routes, so the hops printed may not form one actual path. Also try TCP-based probes to the port you care about, since some networks treat them very differently from the default.

#2173 · rfc1149_enjoyer · · Report

Right on all three. The load-balancing point is the one that fools experts: you read the output as a line and it is a bundle of lines. And yes, TTL as seconds was in the spec; the hop count is just what the world made of it.

Log in or join to reply.