From routing-discussion-admin@ietf.org  Mon Jun  3 22:11:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06904
	for <routing-discussion-archive@odin.ietf.org>; Mon, 3 Jun 2002 22:11:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA16076;
	Mon, 3 Jun 2002 22:05:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA16046
	for <routing-discussion@ns.ietf.org>; Mon, 3 Jun 2002 22:04:59 -0400 (EDT)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06825
	for <routing-discussion@ietf.org>; Mon, 3 Jun 2002 22:04:29 -0400 (EDT)
Received: from ci1093exch001p.wins.lucent.com (h135-252-12-239.lucent.com [135.252.12.239])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g5424Rx07192
	for <routing-discussion@ietf.org>; Mon, 3 Jun 2002 22:04:27 -0400 (EDT)
Received: by CI1093EXCH001P with Internet Mail Service (5.5.2653.19)
	id <MCB7Z66D>; Tue, 4 Jun 2002 10:04:26 +0800
Message-ID: <31C0F08B0D18D511ACC800508BAE7B4702B9CFF2@CI0026EXCH001U>
From: "Li, Ke Qin (Peter)" <keqinli@lucent.com>
To: routing-discussion@ietf.org
Subject: Loop Detection
Date: Tue, 4 Jun 2002 10:04:25 +0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Hi,

I've the following question:

Given a network with several routers, is there any tool/application to
detect loops in the routing tables?

Keqin Li
Bell Labs Research China
Tel: 86-010-68748088-8438



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-admin@ietf.org  Mon Jun  3 23:11:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08074
	for <routing-discussion-archive@odin.ietf.org>; Mon, 3 Jun 2002 23:11:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA18781;
	Mon, 3 Jun 2002 23:05:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA17873
	for <routing-discussion@ns.ietf.org>; Mon, 3 Jun 2002 22:49:06 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA07847
	for <routing-discussion@ietf.org>; Mon, 3 Jun 2002 22:48:37 -0400 (EDT)
Received: (qmail 1209 invoked from network); 4 Jun 2002 02:53:32 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 4 Jun 2002 02:53:32 -0000
Message-ID: <3CFC2A72.FB43A4EC@cad.zju.edu.cn>
Date: Tue, 04 Jun 2002 10:48:18 +0800
From: Jing Shen <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>, routing-discussion@ietf.org
Subject: Re: Loop Detection
References: <31C0F08B0D18D511ACC800508BAE7B4702B9CFF4@CI0026EXCH001U>
Content-Type: multipart/alternative;
 boundary="------------66A04FEBDC244A1F1DE9DCD9"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


--------------66A04FEBDC244A1F1DE9DCD9
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit

 this  is quite straight.  traceroute will do help in finding such
problem.

> Hi,
>
> I've the following question:
>
> Given a network with several routers, is there any tool/application to
> detect loops in the routing tables?
>
> Keqin Li
> Bell Labs Research China
> Tel: 86-010-68748088-8438

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University (YuQuan)
HangZhou, ZheJiang Province 310027
P.R.China

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************



--------------66A04FEBDC244A1F1DE9DCD9
Content-Type: text/html; charset=gb2312
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;this&nbsp; is quite straight.&nbsp; traceroute will do help in finding
such problem.
<blockquote TYPE=CITE>Hi,
<p>I've the following question:
<p>Given a network with several routers, is there any tool/application
to
<br>detect loops in the routing tables?
<p>Keqin Li
<br>Bell Labs Research China
<br>Tel: 86-010-68748088-8438</blockquote>

<pre>--&nbsp;
Jing Shen

State Key Lab of CAD&amp;CG
ZheJiang University (YuQuan)
HangZhou, ZheJiang Province 310027
P.R.China

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *
*&nbsp; bright all the time&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *
**********************************************************************</pre>
&nbsp;</html>

--------------66A04FEBDC244A1F1DE9DCD9--



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-admin@ietf.org  Tue Jun  4 18:54:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18836
	for <routing-discussion-archive@odin.ietf.org>; Tue, 4 Jun 2002 18:54:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA27502;
	Tue, 4 Jun 2002 18:46:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA12788
	for <routing-discussion@optimus.ietf.org>; Tue, 4 Jun 2002 13:55:22 -0400 (EDT)
Received: from mailman.sprintlabs.com (mx.sprintlabs.com [199.2.53.192])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07801
	for <routing-discussion@ietf.org>; Tue, 4 Jun 2002 13:54:52 -0400 (EDT)
Received: by mailman.sprintlabs.com with Internet Mail Service (5.5.2653.19)
	id <25KAKQ5S>; Tue, 4 Jun 2002 10:55:21 -0700
Received: from kimchi.sprintlabs.com ([199.2.53.19]) by mailman.sprintlabs.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 25KAKQ5M; Tue, 4 Jun 2002 10:53:22 -0700
From: Sue Moon <Sbmoon@sprintlabs.com>
To: Jing Shen <jshen@cad.zju.edu.cn>
Cc: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>, routing-discussion@ietf.org,
        Christophe Diot <cdiot@sprintlabs.com>
Date: Tue, 4 Jun 2002 10:53:22 -0700 (PDT)
Subject: Re: Loop Detection
In-Reply-To: <3CFC2A72.FB43A4EC@cad.zju.edu.cn>
Message-ID: <Pine.LNX.4.33.0206041051490.22286-100000@kimchi.sprintlabs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


On Tue, 4 Jun 2002, Jing Shen wrote:

> Given a network with several routers, is there any tool/application to
> detect loops in the routing tables?

As far as I know, there isn't.
Also if the loop is due to a misconfiguration which does not show up
in BGP updates, then it's harder to detect.

-Sue

-- 
Sue B. Moon                                sbmoon@sprintlabs.com
Sprint ATL                                    (tel) 650-375-4121
1 Adrian Court                                (fax) 650-375-4079
Burlingame, CA 94010     http://www.sprintlabs.com/People/sbmoon



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-admin@ietf.org  Tue Jun  4 22:25:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22422
	for <routing-discussion-archive@odin.ietf.org>; Tue, 4 Jun 2002 22:25:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07935;
	Tue, 4 Jun 2002 22:16:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07909
	for <routing-discussion@ns.ietf.org>; Tue, 4 Jun 2002 22:16:15 -0400 (EDT)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22285
	for <routing-discussion@ietf.org>; Tue, 4 Jun 2002 22:15:44 -0400 (EDT)
Received: from ci1093exch001p.wins.lucent.com (h135-252-12-239.lucent.com [135.252.12.239])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g552FQi23205
	for <routing-discussion@ietf.org>; Tue, 4 Jun 2002 22:15:27 -0400 (EDT)
Received: by CI1093EXCH001P with Internet Mail Service (5.5.2653.19)
	id <MCB75PBQ>; Wed, 5 Jun 2002 10:15:25 +0800
Message-ID: <31C0F08B0D18D511ACC800508BAE7B4702B9CFF6@CI0026EXCH001U>
From: "Li, Ke Qin (Peter)" <keqinli@lucent.com>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>,
        Mailing List
	 <OSPF@DISCUSS.MICROSOFT.COM>,
        routing-discussion@ietf.org
Subject: RE: Loop Detection
Date: Wed, 5 Jun 2002 10:15:20 +0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C20C36.D7DC46E0"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C20C36.D7DC46E0
Content-Type: text/plain;
	charset="gb2312"

But even every destinations in the network have been tracerouted from one
router A, there can still be loops. In that case, the loop is not in any
paths from A to other nodes.
 
Is there any other approach?
 
Keqin Li

-----Original Message-----
From: Jing Shen [mailto:jshen@cad.zju.edu.cn]
Sent: Tuesday, June 04, 2002 10:48 AM
To: Mailing List; routing-discussion@ietf.org
Subject: Re: Loop Detection


 this  is quite straight.  traceroute will do help in finding such problem. 

Hi, 

I've the following question: 


Given a network with several routers, is there any tool/application to 
detect loops in the routing tables? 


Keqin Li 
Bell Labs Research China 
Tel: 86-010-68748088-8438

-- 

Jing Shen



State Key Lab of CAD&CG

ZheJiang University (YuQuan)

HangZhou, ZheJiang Province 310027

P.R.China



Email: jshen@cad.zju.edu.cn



**********************************************************************

* The SunShine of life is made up of very little beams which is      *

*  bright all the time                                               *

**********************************************************************
  


------_=_NextPart_001_01C20C36.D7DC46E0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dgb2312">


<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT color=3D#0000ff face=3D=CB=CE=CC=E5 size=3D2><SPAN =
class=3D991230902-05062002>But even=20
every destinations in the network have been tracerouted from one router =
A, there=20
can still be loops. In that case, the loop is not in any paths from A =
to other=20
nodes.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
class=3D991230902-05062002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3D=CB=CE=CC=E5 size=3D2><SPAN =
class=3D991230902-05062002>Is there=20
any other approach?</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
class=3D991230902-05062002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3D=CB=CE=CC=E5 size=3D2><SPAN =
class=3D991230902-05062002>Keqin=20
Li</SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Jing Shen=20
  [mailto:jshen@cad.zju.edu.cn]<BR><B>Sent:</B> Tuesday, June 04, 2002 =
10:48=20
  AM<BR><B>To:</B> Mailing List; =
routing-discussion@ietf.org<BR><B>Subject:</B>=20
  Re: Loop Detection<BR><BR></DIV></FONT>&nbsp;this&nbsp; is quite=20
  straight.&nbsp; traceroute will do help in finding such problem.=20
  <BLOCKQUOTE TYPE=3D"CITE">Hi,=20
    <P>I've the following question:=20
    <P>Given a network with several routers, is there any =
tool/application to=20
    <BR>detect loops in the routing tables?=20
    <P>Keqin Li <BR>Bell Labs Research China <BR>Tel:=20
  86-010-68748088-8438</P></BLOCKQUOTE><PRE>--&nbsp;
Jing Shen

State Key Lab of CAD&amp;CG
ZheJiang University (YuQuan)
HangZhou, ZheJiang Province 310027
P.R.China

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which =
is&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *
*&nbsp; bright all the =
time&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *
**********************************************************************</=
PRE>&nbsp;=20
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C20C36.D7DC46E0--

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-admin@ietf.org  Thu Jun 13 22:03:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08087
	for <routing-discussion-archive@odin.ietf.org>; Thu, 13 Jun 2002 22:03:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA05469;
	Thu, 13 Jun 2002 21:54:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA05439
	for <routing-discussion@optimus.ietf.org>; Thu, 13 Jun 2002 21:54:39 -0400 (EDT)
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07908
	for <routing-discussion@ietf.org>; Thu, 13 Jun 2002 21:54:03 -0400 (EDT)
Received: from 12-234-73-224.client.attbi.com ([12.234.73.224])
	by psg.com with esmtp (Exim 3.36 #1)
	id 17IgIR-0005Di-00
	for routing-discussion@ietf.org; Thu, 13 Jun 2002 18:54:39 -0700
Date: Thu, 13 Jun 2002 18:53:26 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: "Alex Zinin <zinin@psg.com>; Bill Fenner" <fenner@research.att.com>
X-Priority: 3 (Normal)
Message-ID: <16918958541.20020613185326@psg.com>
To: routing-discussion@ietf.org
Subject: Routing Area Meeting in Yokohama
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Folks,

 We're planning on having an open Routing Area meeting in Yokohama. It
 is currently scheduled for the 1930-2200 slot on Monday, July 15,
 subject to possible changes due to the meeting planning.

 The first draft of the agenda is given below; a more concrete version
 with slot lengths will be announced later. If you have a topic you
 believe should be discussed at this meeting and you would like to
 request a slot, please send a message to Bill and myself.

   1. Agenda bashing
   2. AD mumbling
   3. WG updates
   4. "Midnight Sun" routing workshop update
   5. IRTF RRG update
   6. Open mike

 As you can see, we will hold an open mike session. If you know you
 have a question you'd like to raise there, you might consider sending
 us an e-mail so we can give you a better answer.

 The late session on Monday was chosen for this meeting intentionally.
 Right after the meeting, we will have a "Bar BOF"--an informal
 gathering of routing geeks at a nearby place (TBD) to give people a
 chance to meet each other and chat. Everyone is welcome, so please
 consider yourself invited. We believe that a friendly atmosphere is
 essential for productive technical work, and considering the growing
 number of IETF participants in general and routing area members in
 particular, Bill and I felt that as the ADs we need to make a move in
 this direction. This is the good news. Bad news is that you guys will
 have to pay for your food and drinks there :).

 See you in Yokohama.
 
-- 
Alex & Bill



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


