[42699] in North American Network Operators' Group
Re: looping traceroutes
daemon@ATHENA.MIT.EDU (Ratul Mahajan)
Wed Sep 19 03:41:28 2001
Date: Wed, 19 Sep 2001 00:40:51 -0700 (PDT)
From: Ratul Mahajan <ratul@cs.washington.edu>
To: "Patrick W. Gilmore" <patrick@ianai.net>
Cc: <nanog@merit.edu>
In-Reply-To: <5.1.0.14.2.20010919003918.01c599b0@127.0.0.1>
Message-ID: <Pine.LNX.4.33.0109190034230.25412-100000@krypton.cs.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
>
> >27 208.63.128.3 (208.63.128.3) 111.475 ms 69.670 ms 69.267 ms
> >28 208.63.128.1 (208.63.128.1) 68.883 ms 67.147 ms 72.106 ms
> >29 208.63.128.3 (208.63.128.3) 69.842 ms 67.889 ms 66.944 ms
> >30 208.63.128.1 (208.63.128.1) 70.986 ms 73.124 ms 68.452 ms
>
> This looks exactly like a routing loop to me. Why do you think it is not a
> routing loop?
I was assuming that any routing loop in the system would be transient, but
this one is not (the traceroute is still showing the same behavior). The
extent to which I see this also makes me think that there is something
else going on.
Do you think that it can be a real persistent routing loop (data packets
would actually shuttle between the two interfaces) as against some
wierdness because of traceroute?
thanks,
-- ratul
