differences between NANOG traceroute and NetBSD's traceroute

From: Igor Sobrado (sobrado_at_string1.ciencias.uniovi.es)
Date: 11/18/03

Next message: sam: "Re: SELinux Installation"

Previous message: Rudolf Polzer: "Re: How large is the NetBSD user base ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: 18 Nov 2003 12:34:24 +0100

The NANOG traceroute provides a different information about autonomous
systems that the traceroute implementation in NetBSD. This is the output
of NANOG traceroute from my laptop (in a WLAN) to a machine at MIT:

$ traceroute -A aros.ron.lcs.mit.edu
traceroute to aros.ron.lcs.mit.edu (206.197.119.141), 30 hops max, 40 byte packets
1 156.35.3.3 (156.35.3.3) [AS766] 6 ms 6 ms 5 ms
2 156.35.3.3 (156.35.3.3) [AS766] 16 ms 6 ms 4 ms
3 FE0-2-0.EB-Oviedo0.red.rediris.es (130.206.196.37) [AS766] 4 ms 7 ms 7 ms
4 AST.SO2-1-0.EB-Santiago0.red.rediris.es (130.206.240.93) [AS766] 13 ms 15 ms 13 ms
5 GAL.SO2-0-0.EB-IRIS4.red.rediris.es (130.206.240.33) [AS766] 22 ms 24 ms 22 ms
6 * mad-val-i1-pos3-0.telia.net (213.248.71.29) [AS1299] 22 ms 24 ms
7 prs-b1-pos12-0.telia.net (213.248.70.77) [AS1299] 50 ms * 51 ms
8 prs-bb1-pos0-3-0.telia.net (213.248.70.1) [AS1299] 47 ms 46 ms 46 ms
9 ldn-bb1-pos0-2-0.telia.net (213.248.64.157) [AS1299] 56 ms 58 ms *
10 * nyk-bb1-pos0-2-0.telia.net (213.248.65.90) [AS1299] 158 ms *
11 * sl-gw27-nyc-10-0.sprintlink.net (144.232.230.29) [AS1239] 153 ms *
12 sl-bb23-nyc-15-1.sprintlink.net (144.232.7.21) [AS1239] 163 ms 223 ms *
13 * * sl-bb20-nyc-8-0.sprintlink.net (144.232.7.13) [AS1239] 153 ms
14 sl-bb22-nyc-8-0.sprintlink.net (144.232.7.106) [AS1239] 194 ms 247 ms *
15 * * sl-bb21-chi-9-0.sprintlink.net (144.232.9.149) [AS1239] 263 ms
16 * * sl-st20-chi-15-1.sprintlink.net (144.232.20.80) [AS1239] 223 ms
17 * sl-eleclight-14-0.sprintlink.net (144.223.241.18) [AS1239] 189 ms *
18 p11-0.cr01.chcg.eli.net (207.173.114.97) [AS5650] 262 ms 171 ms 248 ms
19 p10-0.cr02.slkc.eli.net (207.173.115.53) [AS5650] 222 ms 240 ms 222 ms
20 srp0-0-0.gw03.slkc.eli.net (208.186.20.55) [AS5650] 224 ms 224 ms 286 ms
21 gw-cust-AROS-NET.slkc.eli.net (209.210.44.106) [AS5650] 317 ms 204 ms 204 ms
22 zeus.aros.net (66.219.192.111) [AS6521] 235 ms 205 ms 242 ms
23 aros.ron.lcs.mit.edu (206.197.119.141) [AS6521/AS5650] 214 ms 207 ms 301 ms

and this is the output of the standard traceroute tool provided with
NetBSD with the same source and destination hosts:

$ traceroute -a aros.ron.lcs.mit.edu
traceroute to aros.ron.lcs.mit.edu (206.197.119.141), 30 hops max, 40 byte packets
1 [AS766] 156.35.3.3 (156.35.3.3) 5.956 ms 4.695 ms 6.527 ms
2 [AS766] 156.35.3.3 (156.35.3.3) 4.662 ms 6.639 ms 5.722 ms
3 [AS766] FE0-2-0.EB-Oviedo0.red.rediris.es (130.206.196.37) 5.255 ms 5.002 ms 5.197 ms
4 [AS766] AST.SO2-1-0.EB-Santiago0.red.rediris.es (130.206.240.93) 13.088 ms 13.525 ms 14.094 ms
5 [AS766] GAL.SO2-0-0.EB-IRIS4.red.rediris.es (130.206.240.33) 21.953 ms 22.060 ms 28.064 ms
6 * * [AS1299] mad-val-i1-pos3-0.telia.net (213.248.71.29) 28.178 ms
7 * * [AS1299] prs-b1-pos12-0.telia.net (213.248.70.77) 49.213 ms
8 [AS1299] prs-bb1-pos0-3-0.telia.net (213.248.70.1) 48.593 ms * *
9 [AS1299] ldn-bb1-pos0-2-0.telia.net (213.248.64.157) 57.352 ms * *
10 [AS1299] nyk-bb1-pos0-2-0.telia.net (213.248.65.90) 159.481 ms * 157.746 ms
11 * * *
12 [AS1239] sl-bb23-nyc-15-1.sprintlink.net (144.232.7.21) 156.752 ms * *
13 * [AS1239] sl-bb20-nyc-8-0.sprintlink.net (144.232.7.13) 154.203 ms *
14 * * [AS1239] sl-bb22-nyc-8-0.sprintlink.net (144.232.7.106) 187.084 ms
15 [AS1239] sl-bb21-chi-9-0.sprintlink.net (144.232.9.149) 192.346 ms 177.867 ms 211.500 ms
16 [AS1239] sl-st20-chi-15-1.sprintlink.net (144.232.20.80) 177.909 ms 180.889 ms 174.781 ms
17 [AS1239] sl-eleclight-14-0.sprintlink.net (144.223.241.18) 174.358 ms 170.962 ms 169.977 ms
18 [AS5650] p11-0.cr01.chcg.eli.net (207.173.114.97) 276.489 ms 169.681 ms 240.378 ms
19 [AS5650] p10-0.cr02.slkc.eli.net (207.173.115.53) 224.477 ms 224.277 ms 222.692 ms
20 [AS5650] srp0-0-0.gw03.slkc.eli.net (208.186.20.55) 272.012 ms 224.793 ms 223.446 ms
21 [AS5650] gw-cust-AROS-NET.slkc.eli.net (209.210.44.106) 320.091 ms * 204.323 ms
22 [AS6521] zeus.aros.net (66.219.192.111) 203.975 ms 205.412 ms 203.963 ms
23 [AS6521] aros.ron.lcs.mit.edu (206.197.119.141) 204.972 ms * *

>From the output of both traceroute variants, it looks like NetBSD's
one fails showing all the autonomous systems. In short, where
entries in RADB are equally specific yet list different autonomous
systems, it should list ALL autonomous systems separated by a slash (/).

Should we open a PR on this issue?

Cheers,
Igor.

-- 
Igor Sobrado, UK34436 - sobrado@acm.org

Next message: sam: "Re: SELinux Installation"

Previous message: Rudolf Polzer: "Re: How large is the NetBSD user base ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Relevant Pages

Re: Cant traceroute to my box
... > I am new to FreeBSD. ... I have been using NetBSD for about 9 years. ... > I can't traceroute to the box. ... If it is _not_ 0 it means that UDP ports that are not in use ...
(freebsd-questions)
Re: Cant traceroute to my box
... I have been using NetBSD for about 9 years. ... > I can't traceroute to the box. ... If the firewall is blocking UDP, ...
(freebsd-questions)
Re: OpenBSD box returning wrong IP
... The PC from which I'm running the traceroute is Windows XP. ... also tried traceroute from a NetBSD box on the internal network with ...
(comp.unix.bsd.openbsd.misc)
Re: More techy help required!
... > boxes, however, laptop cannot get a connection to news. ... > problems and to test out using "traceroute". ... > followed the instructions for this but simply got a black rectangle ... How is the laptop connecting to t'internet? ...
(uk.media.radio.archers)
Re: SSH between computers on LAN
... But a traceroute from the laptop works to this computer. ... Try the IP of the wired port instead. ... second router gets Internet from the first. ...
(Ubuntu)