From owner-freebsd-questions@FreeBSD.ORG Tue Nov 20 18:37:54 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBFCD16A418 for ; Tue, 20 Nov 2007 18:37:54 +0000 (UTC) (envelope-from philip@ridecharge.com) Received: from EXHUB015-4.exch015.msoutlookonline.net (exhub015-4.exch015.msoutlookonline.net [207.5.72.96]) by mx1.freebsd.org (Postfix) with ESMTP id CCFE913C465 for ; Tue, 20 Nov 2007 18:37:54 +0000 (UTC) (envelope-from philip@ridecharge.com) Received: from philip.hq.rws (74.93.213.161) by smtpx15.msoutlookonline.net (207.5.72.103) with Microsoft SMTP Server (TLS) id 8.0.744.0; Tue, 20 Nov 2007 10:37:47 -0800 Message-ID: <4743297A.8060800@riderway.com> Date: Tue, 20 Nov 2007 13:37:46 -0500 From: "Philip M. Gollucci" Organization: Riderway Inc. User-Agent: Thunderbird 2.0.0.6 (X11/20070919) MIME-Version: 1.0 To: "Loren M. Lang" References: <20071120044007.GA12898@alzatex.com> In-Reply-To: <20071120044007.GA12898@alzatex.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: FreeBSD NFS server responds with wrong address X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2007 18:37:54 -0000 Loren M. Lang wrote: > I was attempting to do an NFS mount from a FreeBSD server to a FreeBSD > client over IPv6 and received the error "NFSPROC_NULL: RPC: Timed out." > After doing a packet trace, I noticed that the FreeBSD server was > indeed responding to both a Portmap GATADDR call and a NFS NULL call, > but in both cases it was coming from the IPv6 address closest to the > client making the call and not the address the call was issued to. Why > is this happening and how do I make the server respond with the correct > address? > > The server is FreeBSD 6.2-RELEASE-p7. I might be able to confirm this but not fix it. I had a dual nic NFS server (both nics in the same subnet and physical lan) I was issuing a mount to nic1, but nic0 was responding, so I got the NFS NULL call and a timeout. The fix was to issue it to nic0. (This is very likely due to my same subnet setup) -- ------------------------------------------------------------------------ Philip M. Gollucci (philip@ridecharge.com) o:703.549.2050x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching.