From owner-freebsd-questions Tue Feb 26 9:11:28 2002 Delivered-To: freebsd-questions@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A473337B400 for ; Tue, 26 Feb 2002 09:11:25 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 Feb 2002 17:11:24 +0000 (GMT) To: Shawn O'Connor Cc: freebsd-questions@freebsd.org Subject: Re: NFS replies with different IP address In-Reply-To: Your message of "Tue, 26 Feb 2002 08:52:21 PST." <20020226083448.B62491-100000@mail.e-perception.com> Date: Tue, 26 Feb 2002 17:11:24 +0000 From: Ian Dowse Message-ID: <200202261711.aa90093@salmon.maths.tcd.ie> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020226083448.B62491-100000@mail.e-perception.com>, Shawn O'Connor writes: >I agree that this is a Solaris problem. I find it disconcerting that >the Solaris box would respond back with it's primary IP address. I was >just wondering if there was an easy work around. If Solaris supports TCP NFS mounts (mount -o -T from the FreeBSD client), then those will not suffer from this problem. It would be relatively hard to work around the UDP mount problem from FreeBSD; the kernel does the equivalent of connect(2) on the client socket, so you would need to stop it from doing that, and then get it to specify the server address explicitly when sending requests. mount_nfs would also need to be changed so that it does not call connect(2) either. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message