Public bug reported: This is what I get :
$ traceroute www.google.com traceroute to www.google.com (74.125.235.20), 30 hops max, 60 byte packets 1 192.168.0.1 (192.168.0.1) 1.545 ms 1.759 ms 2.771 ms 2 10.10.145.1 (10.10.145.1) 11.986 ms 12.214 ms * 3 * * * 4 * * * 5 * * * 6 * 121.240.1.38 (121.240.1.38) 58.080 ms 43.995 ms 7 209.85.241.52 (209.85.241.52) 44.342 ms 44.650 ms 45.224 ms 8 209.85.251.95 (209.85.251.95) 57.145 ms * * 9 * * * 10 * * * 11 * * sin01s04-in-f20.1e100.net (74.125.235.20) 86.774 ms This output is wrong. The * nodes should be shown since they are replying. I have put up wireshark screenshots and more results here : http://www.binarytides.com/blog/traceroute-command-not-working-on- ubuntu/ Silver ** Affects: traceroute (Ubuntu) Importance: Undecided Status: New ** Description changed: - I have put up the results here : + This is what I get : + + $ traceroute www.google.com + traceroute to www.google.com (74.125.235.20), 30 hops max, 60 byte packets + 1 192.168.0.1 (192.168.0.1) 1.545 ms 1.759 ms 2.771 ms + 2 10.10.145.1 (10.10.145.1) 11.986 ms 12.214 ms * + 3 * * * + 4 * * * + 5 * * * + 6 * 121.240.1.38 (121.240.1.38) 58.080 ms 43.995 ms + 7 209.85.241.52 (209.85.241.52) 44.342 ms 44.650 ms 45.224 ms + 8 209.85.251.95 (209.85.251.95) 57.145 ms * * + 9 * * * + 10 * * * + 11 * * sin01s04-in-f20.1e100.net (74.125.235.20) 86.774 ms + + + I have put up more results here : http://www.binarytides.com/blog/traceroute-command-not-working-on- ubuntu/ Silver ** Description changed: This is what I get : $ traceroute www.google.com traceroute to www.google.com (74.125.235.20), 30 hops max, 60 byte packets - 1 192.168.0.1 (192.168.0.1) 1.545 ms 1.759 ms 2.771 ms - 2 10.10.145.1 (10.10.145.1) 11.986 ms 12.214 ms * - 3 * * * - 4 * * * - 5 * * * - 6 * 121.240.1.38 (121.240.1.38) 58.080 ms 43.995 ms - 7 209.85.241.52 (209.85.241.52) 44.342 ms 44.650 ms 45.224 ms - 8 209.85.251.95 (209.85.251.95) 57.145 ms * * - 9 * * * + 1 192.168.0.1 (192.168.0.1) 1.545 ms 1.759 ms 2.771 ms + 2 10.10.145.1 (10.10.145.1) 11.986 ms 12.214 ms * + 3 * * * + 4 * * * + 5 * * * + 6 * 121.240.1.38 (121.240.1.38) 58.080 ms 43.995 ms + 7 209.85.241.52 (209.85.241.52) 44.342 ms 44.650 ms 45.224 ms + 8 209.85.251.95 (209.85.251.95) 57.145 ms * * + 9 * * * 10 * * * 11 * * sin01s04-in-f20.1e100.net (74.125.235.20) 86.774 ms - I have put up more results here : + This output is wrong. The * nodes should be shown since they are replying. I have put up wireshark screenshots and more results here : http://www.binarytides.com/blog/traceroute-command-not-working-on- ubuntu/ Silver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/902749 Title: Traceroute command shows wrong results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/traceroute/+bug/902749/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
