traceroute AS path patch

Leonid Grossman Leonid.Grossman at neterion.com
Wed Feb 20 01:12:10 UTC 2008


Sorry pl ignore this - replied to the wrong message... Blackberry buttons are too small for me :-) 

----- Original Message -----
From: Leonid Grossman
To: 'rpaulo at freebsd.org' <rpaulo at freebsd.org>; 'jhay at meraka.org.za' <jhay at meraka.org.za>
Cc: 'freebsd-net at freebsd.org' <freebsd-net at freebsd.org>
Sent: Tue Feb 19 19:57:58 2008
Subject: Re: traceroute AS path patch

Pl forward him my original e-mail, it is all I got. Last event was not useful, but who knows...

----- Original Message -----
From: owner-freebsd-net at freebsd.org <owner-freebsd-net at freebsd.org>
To: John Hay <jhay at meraka.org.za>
Cc: freebsd-net at freebsd.org <freebsd-net at freebsd.org>
Sent: Tue Feb 19 17:13:34 2008
Subject: Re: traceroute AS path patch


On Feb 18, 2008, at 10:41 AM, John Hay wrote:

> Hi Rui,
>
> On Sun, Feb 17, 2008 at 09:30:44PM +0000, Rui Paulo wrote:
>> Hi,
>> The attached patch ports a traceroute functionality from FreeBSD
>> called AS path.
>> The concept is simple. On each hop we query a whois server to find  
>> the
>> corresponding hop AS number.
>>
>> I think it doesn't hurt if we have this functionality.
>>
>> An example output:
>> traceroute to freebsd.org (69.147.83.40), 64 hops max, 72 byte  
>> packets
>> ...
>> 7  [AS6453] if-2-1.core1.PV9-Lisbon.teleglobe.net (195.219.187.21)
>> 35.105 ms  34.008 ms  35.334 ms
>> 8  [AS6453] 195.219.144.5 (195.219.144.5)  63.880 ms  60.448 ms
>> 60.809 ms
>> 9  [AS6453] 195.219.144.10 (195.219.144.10)  138.593 ms  193.709 ms
>> 173.415 ms
>> 10  [AS7199] if-2-0.core1.NJY-Newark.teleglobe.net (216.6.63.10)
>> 133.912 ms  134.393 ms  144.071 ms
>> 11  [AS9557] if-3-1.mcore3.NJY-Newark.teleglobe.net (216.6.57.1)
>> 135.600 ms  144.979 ms  168.247 ms
>> 12  [AS9557] if-12-0-0-741.core4.AEQ-Ashburn.teleglobe.net
>> (216.6.57.70)  180.346 ms  138.718 ms  138.927 ms
>> 13  [AS6453] 64.86.85.38 (64.86.85.38)  142.745 ms  143.163 ms
>> 143.358 ms
>> 14  [AS26085] so-0-0-0.pat2.pao.yahoo.com (216.115.101.130)  252.417
>> ms  213.377 ms  212.859 ms
>> 15  [AS26085] ge-0-1-0-p301.pat1.sjc.yahoo.com (216.115.106.147)
>> 214.709 ms  213.198 ms  235.253 ms
>> 16  [AS26085] g-1-0-0-p160.msr1.sp1.yahoo.com (216.115.107.61)
>> 219.091 ms
>>    [AS26085] g-0-0-0-p170.msr2.sp1.yahoo.com (216.115.107.81)
>> 217.650 ms
>>    [AS26085] g-1-0-0-p160.msr1.sp1.yahoo.com (216.115.107.61)
>> 286.376 ms
>> 17  [AS36752] ge-1-45.bas-b2.sp1.yahoo.com (209.131.32.49)  213.747  
>> ms
>>    [AS36752] ge-1-41.bas-b2.sp1.yahoo.com (209.131.32.33)  274.140 ms
>>    [AS36752] ge-1-45.bas-b2.sp1.yahoo.com (209.131.32.49)  213.341 ms
>> 18  [AS36752] freebsd.org (69.147.83.40)  214.386 ms  223.515 ms
>> 212.548 ms
>>
>>
>> What do you think?
>
> Would it be difficult to add it to traceroute6 too? It would be great
> if we can keep features in sync.

I will try to do it after committing this patch.

Regards.
--
Rui Paulo

_______________________________________________
freebsd-net at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"


More information about the freebsd-net mailing list