You are not logged in.
when using tracepath after the 7th hop I stop getting replies, the same does not happen with traceroute can someone explain me the difference?
tracepath 8.8.8.8
1?: [LOCALHOST] pmtu 1492
1: easy.box 1.974ms
1: easy.box 2.207ms
2: dslb-084-056-032-001.084.056.pools.vodafone-ip.de 12.454ms
3: 188.111.163.228 10.867ms
4: 88.79.10.4 11.525ms
5: 92.79.212.233 10.400ms asymm 3
6: 145.254.2.193 17.611ms asymm 3
7: 145.254.2.193 17.485ms asymm 3
8: no reply
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1492
Resume: pmtu 1492
traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 easy.box (192.168.2.1) 1.619 ms 2.974 ms 2.957 ms
2 dslb-084-056-032-001.084.056.pools.vodafone-ip.de (84.56.32.1) 9.793 ms 10.442 ms 11.019 ms
3 188.111.163.228 (188.111.163.228) 11.236 ms 12.147 ms 12.721 ms
4 88.79.10.12 (88.79.10.12) 12.698 ms 13.318 ms 88.79.10.4 (88.79.10.4) 12.646 ms
5 92.79.213.101 (92.79.213.101) 13.269 ms 13.254 ms 13.220 ms
6 145.254.2.193 (145.254.2.193) 20.147 ms 145.254.2.177 (145.254.2.177) 14.545 ms 145.254.2.193 (145.254.2.193) 15.823 ms
7 145.254.2.177 (145.254.2.177) 14.380 ms 145.254.2.193 (145.254.2.193) 17.849 ms 145.254.2.177 (145.254.2.177) 14.995 ms
8 72.14.213.64 (72.14.213.64) 17.217 ms 18.080 ms 18.635 ms
9 * * *
10 108.170.232.241 (108.170.232.241) 18.524 ms 216.239.59.113 (216.239.59.113) 19.025 ms 216.239.59.185 (216.239.59.185) 18.494 ms
11 google-public-dns-a.google.com (8.8.8.8) 18.961 ms 14.197 ms 15.941 ms
Offline
The same *does* happen. It's just a matter of how each program formats the output and whether they give up after many hops or continue.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
tracepath and traceroute work fundamentally different, the latter one works more like "ping".
From the tracepath mapage
The situation with IPv4 is worse, because commercial IP routers do not return enough information in ICMP error messages.
Probably, it will change, when they will be updated. For now it uses Van Jacobson's trick, sweeping a range of UDP
ports to maintain trace history.Bottom line is that some hops do not reply to the requests send by tracepath, but do reply to the requests send by traceroute.
Offline