From owner-freebsd-net  Wed Mar 21 16:43:59 2001
Delivered-To: freebsd-net@freebsd.org
Received: from gecko.eric.net.au (gecko.eric.net.au [203.102.228.3])
	by hub.freebsd.org (Postfix) with ESMTP id 287F037B71A
	for <freebsd-net@FreeBSD.ORG>; Wed, 21 Mar 2001 16:43:57 -0800 (PST)
	(envelope-from ghcrompton@gecko.eric.net.au)
Received: (from ghcrompton@localhost)
	by gecko.eric.net.au (8.9.3/8.8.7) id LAA28724;
	Thu, 22 Mar 2001 11:53:54 +1100
Date: Thu, 22 Mar 2001 11:53:54 +1100
From: "Geoffrey Crompton (RMIT Guest)" <ghcrompton@gecko.eric.net.au>
To: FreeBSD-Net <freebsd-net@FreeBSD.ORG>
Cc: Jenni Bushby <jbushby@cs.rmit.edu.au>
Subject: how dies rtallocing with XResolve happen
Message-ID: <20010322115354.A28374@gecko.eric.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3us
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


   What is the goal of the XRESOLVE mechanism. Is it to allow code in the
kernel to inform a userland daemon that a routing lookup was performed
and it failed, or is it to allow code in the kernel to have a userland
daemon resolve a route for it?

  If it is the second, how does the userland daemon get an answer back
to the kernel, considering that the userland daemon may need to do some
network communication to get an answer?

  Thanks

  Geoff Crompton


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message