Re: traceroute (was: [BLUG] Did ATT mess up your cell phone, too?)

On Fri, Jul 31, 2009 at 1:52 PM, Jonathan North
Washington<jonwashi@indiana.edu> wrote:
> Ah, wasn't sure if tracert would tell the right stuff about the traffic.
>
> So, a lot of sites I tried tracerting left out too much interesting
> stuff, but I finally got one with most of the interesting stuff:

The default traceroute on Linux uses UDP, which is dropped by lots of
places so you end up with nothing for lots of the hops. Windows
tracert uses ICMP, which seems to make it through a bit more.

On Linux, I'm a big fan of traceroute-nanog (with "-I icmp"):

$ sudo traceroute-nanog -I icmp www.google.com
traceroute to www.l.google.com (209.85.225.99), 64 hops max, 28 byte packets
1 c1811.lab.evilrouters.net (192.168.1.1) 1 ms 1 ms 0 ms
2 border2-col-GE-0-0-802.tls.net (65.124.104.49) 14 ms 13 ms 19 ms
3 border2-indy-GE-0-1-804.tls.net (65.123.104.53) 19 ms 18 ms 18 ms
4 209.120.155.17 (209.120.155.17) 74 ms 20 ms 20 ms
5 76.74.82.30 (76.74.82.30) 22 ms 19 ms 19 ms
6 76.74.82.1 (76.74.82.1) 27 ms 24 ms 23 ms
7 ge-6-7.car2.Chicago1.Level3.net (4.71.183.129) 23 ms 26 ms 24 ms
8 GOOGLE-INC.car2.Chicago1.Level3.net (4.79.66.30) 26 ms 25 ms 24 ms
9 209.85.254.122 (209.85.254.122) 71 ms (TOS=128!) 26 ms 25 ms
10 209.85.241.22 (209.85.241.22) 160 ms 35 ms 72.14.232.141
(72.14.232.141) 35 ms
11 209.85.241.37 (209.85.241.37) 36 ms 89 ms 166 ms
12 209.85.248.106 (209.85.248.106) 120 ms 64 ms 66.249.95.138
(66.249.95.138) 46 ms
13 iy-in-f99.google.com (209.85.225.99) 36 ms 36 ms 36 ms

Try it with and without "-I icmp" and you can see the difference.
traceroute-nanog also has some handy options such as -A and -O.

tcptraceroute and lft can also come in handy at times.

--
Jeremy L. Gaddis
http://evilrouters.net/
_______________________________________________
BLUG mailing list
BLUG@linuxfan.com
http://mailman.cs.indiana.edu/mailman/listinfo/blug