[42724] in North American Network Operators' Group
Re: looping traceroutes
daemon@ATHENA.MIT.EDU (Nick Feamster)
Wed Sep 19 17:47:03 2001
Date: Wed, 19 Sep 2001 17:46:14 -0400 (EDT)
From: Nick Feamster <feamster@lcs.mit.edu>
To: Ratul Mahajan <ratul@cs.washington.edu>
Cc: <nanog@merit.edu>
In-Reply-To: <Pine.LNX.4.33.0109190034230.25412-100000@krypton.cs.washington.edu>
Message-ID: <Pine.LNX.4.33.0109191741060.10140-100000@ginseng.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
> 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?
Seems like a persistent routing loop. One possibility I've
heard about is the persistent routing loops that can occur if an internal
router is not situated topologically close to its BGP route reflector:
http://www.globecom.net/ietf/draft/draft-dube-route-reflection-harmful-00.html
Does anyone have any idea of if/how often these types of persistent loops
occur in practice? I guess there would be no way to really tell if this
was the cause without having some knowledge about the internal topology...
Nick
