Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!agate!ucbvax!MCSUN.EU.NET!Piet.Beertema
From: Piet.Beertema@MCSUN.EU.NET
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Long lines...
Message-ID: <9008311421.AA08486@mcsun.EU.net>
Date: 31 Aug 90 14:21:52 GMT
References: <9008311254.AA03868@mcsun.EU.net>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 34


		From: Michel Fingerhut
		Organization: IRCAM, Paris (France)
		Subject: Internet routing Europe -> USA -> Europe...

		While trying to find whether we (in France, Europe) could reach a site
		in Germany (Europe), I got the following route from traceroute:
	
		   >1  ircam-gw (129.102.0.1)  0 ms  0 ms  0 ms
		   >2  fnet-gw.inria.fr (192.44.64.26)  370 ms  550 ms  480 ms
		   >3  sophia-gw.inria.fr (192.5.60.250)  540 ms  350 ms  290 ms
		   .....
		Why this contorted route?  Is it cost-effective?
	
	That's what I see doing a traceroute to 129.102.0.1:
	traceroute to 129.102.0.1 (129.102.0.1), 30 hops max, 38 byte packets
	 1  iracs1.ira.uka.de (129.13.1.1)  20 ms  0 ms  0 ms
	 2  ciscogb5.Informatik.Uni-Dortmund.DE (188.1.132.1)  1020 ms  840 ms 1080 ms
	 3  Amsterdam.NL.EU.NET (134.222.1.1)  4120 ms *  3800 ms
	 4  Paris.FR.EU.NET (134.222.2.2)  4340 ms  4900 ms  3760 ms
	 5  fnet-gw.inria.fr (128.93.36.128)  3880 ms  3740 ms *
	 6  192.44.64.61 (192.44.64.61)  3980 ms  4960 ms *
	
	Arnold Nipper

Right, that's what I expected: it's just a technical problem
(a gateway not announcing a route). In other words: there was
no need to send this problem to an extremely wide-reaching
mailing list. Contacting the managers of the first gateway
(@inria) could have solved the problem...
Anyway, we'll go after it and inform the people involved.


	Piet