From owner-freebsd-arch@FreeBSD.ORG  Sun Apr 12 21:07:36 2009
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 62763106564A;
	Sun, 12 Apr 2009 21:07:36 +0000 (UTC)
	(envelope-from kientzle@freebsd.org)
Received: from kientzle.com (kientzle.com [66.166.149.50])
	by mx1.freebsd.org (Postfix) with ESMTP id 2AE7F8FC1C;
	Sun, 12 Apr 2009 21:07:36 +0000 (UTC)
	(envelope-from kientzle@freebsd.org)
Received: (from root@localhost)
	by kientzle.com (8.14.3/8.14.3) id n3CL7Yh1060529;
	Sun, 12 Apr 2009 14:07:34 -0700 (PDT)
	(envelope-from kientzle@freebsd.org)
Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2])
	by kientzle.com with SMTP id 5mnfiaientg6kqnf57spjmczun;
	Sun, 12 Apr 2009 14:07:34 -0700 (PDT)
	(envelope-from kientzle@freebsd.org)
Message-ID: <49E25816.9010907@freebsd.org>
Date: Sun, 12 Apr 2009 14:07:34 -0700
From: Tim Kientzle <kientzle@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
	rv:1.8.1.21) Gecko/20090409 SeaMonkey/1.1.15
MIME-Version: 1.0
To: Rick Macklem <rmacklem@uoguelph.ca>
References: <Pine.GSO.4.63.0903301733120.17182@muncher.cs.uoguelph.ca>	<alpine.BSF.2.00.0904051826550.12639@fledge.watson.org>	<49D98461.4000002@elischer.org>	<alpine.BSF.2.00.0904061143190.34905@fledge.watson.org>	<Pine.GSO.4.63.0904061132190.19343@muncher.cs.uoguelph.ca>	<BE45DEE0-8D98-4B32-B48A-4D86834DD6E2@rabson.org>	<alpine.BSF.2.00.0904121323220.19879@fledge.watson.org>	<C8A9F5A9-9B82-43A5-818A-3771B1B25CC7@rabson.org>	<Pine.GSO.4.63.0904121357270.15456@muncher.cs.uoguelph.ca>	<alpine.BSF.2.00.0904121906270.19879@fledge.watson.org>
	<Pine.GSO.4.63.0904121515220.27116@muncher.cs.uoguelph.ca>
In-Reply-To: <Pine.GSO.4.63.0904121515220.27116@muncher.cs.uoguelph.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Robert Watson <rwatson@freebsd.org>, Julian Elischer <julian@elischer.org>,
	freebsd-arch@freebsd.org
Subject: Re: getting a callback ip address for nfsv4 client
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Apr 2009 21:07:36 -0000

> The second brings up the question of NAT, which I know diddly about.
> (I vaguely thought that neither rtalloc() nor getsockaddr() would work,
> since they would return 192.168.x.x and you really need the address
> assigned by the isp?) Can someone help w.r.t. what address to use
> when behind a NAT?

In general, the client doesn't know what address to use
in this case.  In fact, I've been a little confused by this
conversation all along.  It sounds like the client is
looking up it's own address in order to tell the server
how to contact the client?  Why?  The server already
knows the source IP address on the incoming packets
from the client; that's much more robust than anything
the client could look up.

Or did I misunderstand something?

Tim