traceroute doesnt display some hops using ICMP method
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| traceroute (Debian) |
Fix Released
|
Unknown
|
|||
| traceroute (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: traceroute
Hello-
traceroute seems to fail to display hops when using the ICMP method after one of the hops does not have a reverse DNS entry. This works correctly when using the default UDP method, and when using ICMP method with "-n" to turn off lookups.
This makes it difficult to use traceroute because you often have to use ICMP to get around filtering.
This may be the same bug as Bug #269749 from Hardy, but I am seeing it in the latest Karmic. I have verified this also fails with the newest traceroute 2.0.13 compiled from source.
Thanks,
John
johns@ghidorah:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10
johns@ghidorah:~$ apt-cache policy traceroute
traceroute:
Installed: 2.0.12-2
Candidate: 2.0.12-2
Version table:
*** 2.0.12-2 0
500 http://
100 /var/lib/
# traceroute fails to report hops 2-5 using ICMP with reverse DNS lookups
johns@ghidorah:
traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 2.221 ms 2.239 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * asn3356-
7 vlan69.
8 ge-10-0.
9 vnsc-bak.
# traceroute works properly using ICMP without reverse DNS lookups
johns@ghidorah:
traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 60 byte packets
1 192.168.1.1 1.298 ms 1.978 ms 2.375 ms
2 151.164.184.117 21.038 ms 23.446 ms 25.356 ms
3 76.246.22.1 26.515 ms 28.838 ms 31.758 ms
4 151.164.93.229 34.303 ms 36.386 ms 39.063 ms
5 151.164.171.196 42.262 ms 44.472 ms 47.266 ms
6 151.164.251.246 49.642 ms 51.204 ms 53.569 ms
7 4.68.18.62 66.261 ms 43.156 ms 43.463 ms
8 4.68.123.6 39.454 ms 34.446 ms 37.031 ms
9 4.2.2.2 39.461 ms 35.520 ms 38.248 ms
# traceroute works properly using default UDP with reverse DNS lookups
johns@ghidorah:
traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.686 ms 1.706 ms 2.304 ms
2 bras36-
3 76.246.22.1 (76.246.22.1) 27.080 ms 29.918 ms 32.980 ms
4 151.164.93.229 (151.164.93.229) 34.144 ms 36.584 ms 39.277 ms
5 151.164.171.196 (151.164.171.196) 42.691 ms 45.238 ms 48.004 ms
6 asn3356-
7 vlan69.
8 ge-11-0.
9 vnsc-bak.
johns@ghidorah:
Modern traceroute for Linux, version 2.0.12, Apr 29 2009
Copyright (c) 2008 Dmitry Butskoy, License: GPL v2 or any later
| john s (eltapado) wrote | #1 |
| john s (eltapado) wrote | #2 |
| Brandon Applegate (vom) wrote | #3 |
| Changed in traceroute (Ubuntu): | |
| status: | New → Confirmed |
| Changed in traceroute (Debian): | |
| status: | Unknown → Fix Released |
| Graham Inggs (ginggs) wrote | #4 |
| Changed in traceroute (Ubuntu): | |
| status: | Confirmed → Won't Fix |
Ive done some more research on this, and it seems similar to a bug in Debian #436804 http://
The Debian bug compains about the same behavior (not printing hops after a failed reverse lookup) when using the -T (tcp syn) method. I have verified this also happens with the Karmic package.
It looks like both the ICMP and TCP traceroute methods have this problem
johns@ghidorah:~$ sudo traceroute -Tn www.cheeseplant.org
traceroute to www.cheeseplant.org (66.34.180.232), 30 hops max, 60 byte packets
1 192.168.1.1 1.690 ms 2.201 ms 2.882 ms
2 151.164.184.117 63.285 ms 63.327 ms 63.390 ms
3 76.246.22.2 63.465 ms 63.570 ms 63.753 ms
4 151.164.43.56 63.713 ms 63.753 ms 63.939 ms
5 12.122.114.17 64.684 ms 64.743 ms 64.808 ms
6 64.125.12.117 64.866 ms 63.837 ms 63.129 ms
7 64.125.30.177 64.149 ms 33.679 ms 33.742 ms
8 64.125.28.13 33.786 ms 33.775 ms 33.826 ms
9 64.125.24.17 41.585 ms 43.878 ms 47.042 ms
10 64.125.26.121 83.784 ms 85.009 ms 95.887 ms
11 64.125.30.58 97.909 ms 99.996 ms 130.661 ms
12 64.124.196.154 130.664 ms 129.182 ms 98.039 ms
13 64.182.161.6 98.054 ms 98.062 ms 98.117 ms
14 66.34.180.232 98.177 ms 95.117 ms 97.577 ms
johns@ghidorah:~$ sudo traceroute -T www.cheeseplant.org
traceroute to www.cheeseplant.org (66.34.180.232), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.423 ms 1.922 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * xe-1-2-
7 xe-3-0-
8 xe-1-0-
9 * * *
10 xe-0-2-
11 xe-7-0-
12 64.124.
13 64.182.161.6 (64.182.161.6) 68.365 ms 63.376 ms 65.979 ms
14 66.34.180.232 (66.34.180.232) 68.304 ms 70.657 ms 73.149 ms
johns@ghidorah:~$ sudo traceroute -I www.cheeseplant.org
traceroute to www.cheeseplant.org (66.34.180.232), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.294 ms 1.628 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * xe-1-2-
7 xe-3-0-
8 xe-1-0-
9 xe-2-3-