[42703] in North American Network Operators' Group
Re: looping traceroutes
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Wed Sep 19 08:10:01 2001
Date: Wed, 19 Sep 2001 08:09:28 -0400
From: Leo Bicknell <bicknell@ufp.org>
To: nanog@merit.edu
Message-ID: <20010919080928.B80662@ussenterprise.ufp.org>
Mail-Followup-To: Leo Bicknell <bicknell@ussenterprise.ufp.org>,
nanog@merit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.0109190034230.25412-100000@krypton.cs.washington.edu>; from ratul@cs.washington.edu on Wed, Sep 19, 2001 at 12:40:51AM -0700
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, Sep 19, 2001 at 12:40:51AM -0700, Ratul Mahajan wrote:
> 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?
I'd tell you a story, but it would make all of nanog cringe. Put
simply, I know of at least one medium size regional network who
when they couldn't make "bgp work" decided to implement a series
of scripts that logged into all routers and installed statics to
make things work.
Let me just tell you, after a few short weeks of adding and removing
(and missing) such routes there were loops all over the place, many
of which are probably still there. :-(
There are a number of ways long lived loops can occur. I believe
others have pointed out some other methods.
--
Leo Bicknell - bicknell@ufp.org
Systems Engineer - Internetworking Engineer - CCIE 3440
Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
