From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2B1A5138334 for ; Sun, 18 Aug 2019 09:35:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BEE43E0AA7; Sun, 18 Aug 2019 09:35:49 +0000 (UTC) Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 43C6FE08CA for ; Sun, 18 Aug 2019 09:35:49 +0000 (UTC) Received: by mail-ot1-x329.google.com with SMTP id e12so13368854otp.10 for ; Sun, 18 Aug 2019 02:35:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=mvptrBkbWRuhH7ZKdoX9QxcBBVjv3J0AfUzuxAtu3YQ=; b=V/HX/0vdPoYBC5qQViwiaMSEpI4x4ojWjay241hZu4MpU3PYg2OsM/zqKrR8dAzxMA ftG4jvMk94iUlq1tl28coOEb64KH+tO3+B0ZPElJIZhUOI3ntOhVdBtB+XKX7IC/Zzw/ 2evjXsg72ooYRbo4/P04R/WWrkCBBDAP6ANqKbuGOXnXxdEal45KWwRoSrialhtN2bgV 3RwNWeyinU1wxROxGthC+5fGZC+SI4fXjUzhWxOCKSkfHcOK9rCwuagaN4So5VSjRlrL bugkaUl9ofPuhrN+rwyBUuvU5/RJ9pOKsB1rJD2YNA4dqRGJ05LQX64eAtsrNJSQIc24 bKFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=mvptrBkbWRuhH7ZKdoX9QxcBBVjv3J0AfUzuxAtu3YQ=; b=sQz8wLBHCexNJMAiLQvKopXZpDNisoZjsU6L0nl1cYcqy8DDvnHvKYBMEe7NG+ISs6 nsorK1W8JyzeazHrMNjOaCjrXahWoYpc2vKsYuP6DxUAkaH78rCB4BtpEcsPR+NZAuFu T2nSaM2iz23dOa6q3axah6NL/Jz/dd+1ebsJ5GIEyRyJ09KQe6Ubi/aiHXJIt0guCtGn gVhuOv69T4+gw66cX+rDcu7I8rmRniGo8Z08tzQ83UFJU7BDst8hqKWAclvTPYN+Kwtg Qnet/yooOrO2OAqXOEEco0PqV5Co5ullh6h4V4j1MSIgORfYya/6tSq69+i1yGgS2LAM hTZg== X-Gm-Message-State: APjAAAU91TwT6nlJu9gbJpEpRF2QAMz8LMiW8Hf+SRpJwXmSR+vD+aWg ChJn9/VLdLwQQIN3+9yhYLfitOZ1Z9VVCmN5QJ01vuK5 X-Google-Smtp-Source: APXvYqxQD1gqMthZiOhUEOIN7W8BsOdj7G7PK04vhvUNg2wnQND3FoATfNvdUiFabOJkbyeCFSOtMk13gRqRuxDKQow= X-Received: by 2002:a9d:f65:: with SMTP id 92mr13191433ott.24.1566120947932; Sun, 18 Aug 2019 02:35:47 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <3217537.KO732anV92@peak> <3412835.6sJ7JlkKkD@peak> In-Reply-To: <3412835.6sJ7JlkKkD@peak> From: Adam Carter Date: Sun, 18 Aug 2019 19:35:36 +1000 Message-ID: Subject: Re: [gentoo-user] NFS setup To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="000000000000c6e275059060f2b8" X-Archives-Salt: 6fb933e4-c93f-4375-a9ce-deb652dba2f4 X-Archives-Hash: 5282da94196fbf8fe999da9ff5c8468c --000000000000c6e275059060f2b8 Content-Type: text/plain; charset="UTF-8" On Sun, Aug 18, 2019 at 7:11 PM Peter Humphrey wrote: > On Sunday, 18 August 2019 09:30:36 BST Adam Carter wrote: > > > Is the output of 'mount | grep nfs' the same on the two client machines? > > $ mount | grep nfs > nfsd on /proc/fs/nfsd type nfsd (rw,nosuid,nodev,noexec,relatime) > > nfs4 requires less ports than nfs3, just 2049 and something for mountd (IIRC). Try using nfs4 and setting up the firewall for 2049 and 32767 from your OPTS_RPC_MOUNTD="-p 32767" setting. From tcpdump, where .2 is the client and .250 is the server; 192.168.1.2.949 > 192.168.1.250.2049: Flags [S] but the other session is 192.168.1.250.730 > 192.168.1.2.40895: Flags [S] ie a low port on the nfs server makes a connection back to the client, so its quite unconventional FYI, here's what one of mine looks like $ mount | grep nfs 192.168.1.250:/export/public on /mnt/public type nfs4 (ro,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.251,local_lock=none,addr=192.168.1.250,_netdev) $ grep nfs /etc/fstab 192.168.1.250:/export/public /mnt/public nfs4 ro,_netdev,vers=4.0,soft,noatime 0 0 --000000000000c6e275059060f2b8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Aug 18, 2019 at 7:11 PM Peter Humphrey <peter@prh.myzen.co.uk> wrote:
On Sunday, 18 August 2019 09:3= 0:36 BST Adam Carter wrote:

>=C2=A0 Is the output of 'mount | grep nfs' the same on the two = client machines?

$ mount | grep nfs
nfsd on /proc/fs/nfsd type nfsd (rw,nosuid,nodev,noexec,relatime)


nfs4 requires less ports than nfs3, ju= st 2049 and something for mountd (IIRC). Try using nfs4 and setting up the = firewall for 2049 and 32767 from your OPTS_RPC_MOUNTD=3D"-p 32767"= ; setting. From tcpdump, where .2 is the client and .250 is the server;
=
192.168.1.2.949 > 192.168.1.250.2049: Flags [S]
but= the other session is
192.168.1.250.730 > 192.168.1.2.40895: F= lags [S]
ie a low port on the nfs server makes a connection back = to the client, so its quite unconventional

FYI, he= re's what one of mine looks like
$ mount | grep nfs
192.168.1.250:/export/public on /mnt/public type nfs4
(ro,n= oatime,vers=3D4.0,rsize=3D1048576,wsize=3D1048576,namlen=3D255,soft,proto= =3Dtcp,timeo=3D600,retrans=3D2,sec=3Dsys,clientaddr=3D192.168.1.251,local_l= ock=3Dnone,addr=3D192.168.1.250,_netdev)

$ gre= p nfs /etc/fstab
192.168.1.250:/export/public =C2=A0 =C2=A0/= mnt/public =C2=A0 =C2=A0 =C2=A0 =C2=A0nfs4 =C2=A0 =C2=A0ro,_netdev,vers=3D4= .0,soft,noatime =C2=A0 =C2=A0 0 0

--000000000000c6e275059060f2b8--