Learn / Answers

How does traceroute work?

Traceroute sends packets with a time-to-live (TTL) of 1, then 2, then 3, and so on. Each router lowers the TTL by one, and the router where it reaches zero replies with an ICMP "time exceeded" message, revealing itself. The destination finally answers, so each reply maps one hop of the path.

What it looks like in the packets

  • Probes with rising TTLs (UDP to ports 33434 and up, or ICMP echo on Windows).
  • ICMP type 11 (time exceeded) replies from routers along the way.
  • An ICMP port unreachable (type 3) or echo reply from the destination itself.

Common causes

  • Hops shown as * are routers that don't answer traceroute, which is normal.
  • A trace that stops early means packets are dropped beyond the last hop that answered.

What to check

  1. Compare round-trip times hop by hop: a jump that persists to the end shows where delay is added.
  2. Ignore a single slow hop if later hops are fast; routers answer traceroute at low priority.

Wireshark display filters

  • icmp.type == 11time exceeded replies
  • udp.dstport >= 33434 && udp.dstport <= 33534traceroute probes

How Blame Finder flags it

Shown as a path in the Services view, one row per hop. Upload a capture and the finding links straight to the packets behind it.