From owner-freebsd-atm Mon Oct 18 9:31: 2 1999 Delivered-To: freebsd-atm@freebsd.org Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 6FB8314C35 for ; Mon, 18 Oct 1999 09:30:55 -0700 (PDT) (envelope-from salo@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id LAA06914; Mon, 18 Oct 1999 11:30:54 -0500 (CDT) Received: (from salo@localhost) by us.networkcs.com (8.9.2/8.8.7) id LAA20256; Mon, 18 Oct 1999 11:30:53 -0500 (CDT) Date: Mon, 18 Oct 1999 11:30:53 -0500 (CDT) From: Tim Salo Message-Id: <199910181630.LAA20256@us.networkcs.com> To: FreeBSD-ATM@FreeBSD.ORG Subject: Re: [Q] NHRP Implementation In-Reply-To: <380ABF4F.E76C0AB0@etri.re.kr> Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Mon, 18 Oct 1999 15:33:51 +0900 > From: Changhoon Kim > To: FreeBSD ATM > Subject: [Q] NHRP Implementation > > Is there anybody who has already found NHRP implementation code working > over HARP ? We are not aware of any NHRP implementation that works with HARP. NHRP was on our development agenda, but due to changes in the project we were unable to complete this work. We believe that the development of a Next-Hop Client (NHC) should be reasonably straight-forward, although not necessarily trivial. A Next-Hop Server is more involved. You might look at RFC 2583, "Guidelines for Next Hop Client (NHC) Developers", (ftp://ftp.isi.edu/in-notes/rfc2583.txt). -tjs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message