IETF Logo Mail Archive

NHRP question

Tony Li <tli@cisco.com> Mon, 16 October 1995 06:26 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05704; 16 Oct 95 2:26 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa05700; 16 Oct 95 2:26 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id BAA24862; Mon, 16 Oct 1995 01:59:06 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id CAA00932 for rolc-out; Mon, 16 Oct 1995 02:07:19 -0400
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id CAA00920 for <rolc@nexen.com>; Mon, 16 Oct 1995 02:07:15 -0400
Received: from greatdane.cisco.com (greatdane.cisco.com [171.69.1.141]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id BAA24858 for <rolc@nexen.com>; Mon, 16 Oct 1995 01:57:47 -0400
Received: (tli@localhost) by greatdane.cisco.com (8.6.8+c/8.6.5) id XAA12678; Sun, 15 Oct 1995 23:03:44 -0700
Date: Sun, 15 Oct 1995 23:03:44 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tony Li <tli@cisco.com>
Message-Id: <199510160603.XAA12678@greatdane.cisco.com>
To: Yakov Rekhter <yakov@cisco.com>
Cc: rolc@nexen.com
Subject: NHRP question
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

   Current NHRP spec allows for multiple next-hop IP address entries
   in NHRP Reply. Could anyone provide some practical examples where
   this feature would be useful ?

I recall two uses:

1) For debugging purposes, you get back a list of possible exit
routers, similar to traceroute.

2) You get a list of possible exit routers which would be useful in
the case of link layer filtering.

Tony

v2.8.7 | Report a Bug | By Email