#7 traceroute shows incorrect ttl for first echo reply

[Andrew Schwartz]

I ran traceroute on a host that is 12 hops away. traceroute says:

$ traceroute -I 164.74.131.21 -s172.17.67.76 -f10 -m12
traceroute to 164.74.131.21 (164.74.131.21), 12 hops max, 60 byte packets
10 164.74.131.21 (164.74.131.21) 13.276 ms 13.663 ms 14.066 ms

This is wrong. Here are some correct results from ping:

$ ping -t12 164.74.131.21 -Ip3p1.3663
PING 164.74.131.21 (164.74.131.21) from 172.17.234.36 p3p1.3663: 56(84) bytes of data.
64 bytes from 164.74.131.21: icmp_req=1 ttl=119 time=10.8 ms
64 bytes from 164.74.131.21: icmp_req=2 ttl=119 time=10.5 ms

$ ping -t11 164.74.131.21 -Ip3p1.3663
PING 164.74.131.21 (164.74.131.21) from 172.17.234.36 p3p1.3663: 56(84) bytes of data.
^C
--- 164.74.131.21 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4031ms

Packet capture from the traceroute is attached.

I am running "Modern traceroute for Linux, version 2.0.19, Dec 10 2012" on Ubuntu 13.04, but 13.10 has the same problem.

[Dmitry Butskoy]

New version 2.0.20 is released.
Please check whether the problem still persist or not.

[Andrew Schwartz]

Looks good on 2.0.20. Thanks Dmitry.