From owner-freebsd-bugs Tue Mar 11 15: 7:34 2003 Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BD1737B401 for ; Tue, 11 Mar 2003 15:07:33 -0800 (PST) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 00A3343FEC for ; Tue, 11 Mar 2003 15:07:32 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 11 Mar 2003 23:07:31 +0000 (GMT) To: Eric Anderson Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/22594: NFS can't handle asymmetric server routing In-Reply-To: Your message of "Tue, 11 Mar 2003 14:50:07 PST." <200303112250.h2BMo7IJ056143@freefall.freebsd.org> Date: Tue, 11 Mar 2003 23:07:30 +0000 From: Ian Dowse Message-ID: <200303112307.aa08677@salmon.maths.tcd.ie> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <200303112250.h2BMo7IJ056143@freefall.freebsd.org>, Eric Anderson wr ites: > This fix works for the NFS server side, but from the client side, there > is no way (that I know of) that allows you to allow this behavior. In > other words, if I have a Solaris NFS server (that incorrectly responds > on a different interface with the wrong source address), my FreeBSD NFS > client hangs. I have submitted a PR for this long ago, and was told > "too bad - they didn't follow the specs", but the reality is that the > FreeBSD mount command (and amd for that matter) should have a bypass to > say "I don't care if it comes back from a different source address, take > it anyway" - so it will work. I know it is a security risk, but I > should be able to enable that if I'd like. > > This PR should be re-opened. The "-c" option to mount_nfs should do what you want - does this work for you? I'm not sure if there's a way to do this for amd, though on a recent (less than 6 weeks old) -STABLE you cound try setting the sysctl variable `vfs.nfs.nfs_ip_paranoia' to 0. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message