Date: Sat, 25 Oct 2014 09:58:44 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-current@freebsd.org Subject: Re: Some NFS server V4 questions Message-ID: <20141025195819.1cc75873@rsbsd.rsb> In-Reply-To: <544BC6B7.90608@pinyon.org> References: <1414231671692-5959433.post@n5.nabble.com> <544BC6B7.90608@pinyon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Russ, > > PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs > > ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0 > > Possibly need to arrange for mount_nfs to see -o nfsv4 > (I use mount_nfs -o nfsv4,minorversion=1) Yeah, that would work very likely and thanks. >From a purist standpoint, what would be settings on server side to force NFSV4 offering only? This means, how can I configure NFS so that V2/V3 requests get denied AND logged for debug? ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959475.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Sat Oct 25 20:30:06 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A6544C2 for <freebsd-current@freebsd.org>; Sat, 25 Oct 2014 20:30:06 +0000 (UTC) Received: from quine.pinyon.org (quine.pinyon.org [65.101.5.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7BA3C64D for <freebsd-current@freebsd.org>; Sat, 25 Oct 2014 20:30:06 +0000 (UTC) Received: by quine.pinyon.org (Postfix, from userid 122) id ED1451602D3; Sat, 25 Oct 2014 13:30:04 -0700 (MST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on quine.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Received: from feyerabend.n1.pinyon.org (feyerabend.n1.pinyon.org [10.0.10.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by quine.pinyon.org (Postfix) with ESMTPSA id 683001601D8 for <freebsd-current@freebsd.org>; Sat, 25 Oct 2014 13:30:02 -0700 (MST) Message-ID: <544C084A.3070807@pinyon.org> Date: Sat, 25 Oct 2014 13:30:02 -0700 From: "Russell L. Carter" <rcarter@pinyon.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Some NFS server V4 questions References: <1414231671692-5959433.post@n5.nabble.com> <544BC6B7.90608@pinyon.org> <20141025195819.1cc75873@rsbsd.rsb> In-Reply-To: <20141025195819.1cc75873@rsbsd.rsb> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 25 Oct 2014 20:30:06 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/25/14 09:58, Beeblebrox wrote: > Hi Russ, > >>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs >>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0 >> >> Possibly need to arrange for mount_nfs to see -o nfsv4 (I use >> mount_nfs -o nfsv4,minorversion=1) > Yeah, that would work very likely and thanks. > > From a purist standpoint, what would be settings on server side to > force NFSV4 offering only? This means, how can I configure NFS so > that V2/V3 requests get denied AND logged for debug? > I have vfs.nfsd.server_min_nfsvers=4 set on the server, and when I mount_nfs -o nfsv3 on the client, the error the client sees is [tcp] terp:/packages: NFSPROC_NULL: RPC: Program/version mismatch; low version = 4, high version = 4 Have to ^C to exit. Nothing shows up in the server's log, but because of sloth I haven't tried to make anything show up. Maybe there's an option. Best, Russell -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUTAhKAAoJEFnLrGVSDFaEctoP/3VAFxrLfkYDPTsKrCMD0pJf RrNY0ePTVueDltsVXeEpT/pxSzN7RKLhWL0AB0IsoTWBvZZCHTbwv7GvF0yufxNW +oU29DEceIc8dxhXqjjOCKM3Na85C90idukemDG5ZaZoDU9d//POKaV1ET5HwQNq mZ1q4pqNjnf/O0q+7KjOxVvOnA1g7T2x/HxvL7D0RbmO6EGoRNXbMzxidQmcRDSG V4pmS5GoTUuOqTeXqYbrHJsF8tBaxKqcsOcz90LIWoilYCxiVccPY9SI+EYhX0hq ExVzTvt5OvfNSmz252m8I+87Sw0KA9r06fTpbARuK9Afyt/KNcOU/vANjzDegzLG 8u9TcnBfsqNR7K3pqyvt4jyVW6fliI79i1wpVw2ZNn02vGSn1l2iHWzddX9y0Hmj l1VMM2nWgag8V7wHebRmxILZMHK+VU4gWxp4hTXm0GkXHV27vPWY7eMQtbz/e7yu OpqPSUO7AEp6PTMCZoQY8uIEqmfJIKnyv2/ua3RgNtqM1srvjg1nugxXjfD8z9m6 PH0EY691Rv5hUScXwRtcElO8pziKWFbiXE1HrpPDMnpTtq6Wg5r/ubwepWTrmNJC FfdNOzTCVSF6nBMAo7pwV2P2ATHQkDQjMJJ7B8jZPOapCX59q2Cgth/jX0muiX3g wKbO2ZvSZa7lDAmBcecj =DKjs -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141025195819.1cc75873>