From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NFS setup
Date: Sun, 18 Aug 2019 19:35:36 +1000 [thread overview]
Message-ID: <CAC=wYCE7bYXTGLSkqUWX2UCE2bBU-B+OK=_wAwfbSj5i1rVgPg@mail.gmail.com> (raw)
In-Reply-To: <3412835.6sJ7JlkKkD@peak>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Sun, Aug 18, 2019 at 7:11 PM Peter Humphrey <peter@prh.myzen.co.uk>
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
[-- Attachment #2: Type: text/html, Size: 1743 bytes --]
next prev parent reply other threads:[~2019-08-18 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 8:01 [gentoo-user] NFS setup Peter Humphrey
2019-08-18 8:30 ` Adam Carter
2019-08-18 9:11 ` Peter Humphrey
2019-08-18 9:35 ` Adam Carter [this message]
2019-08-18 10:30 ` Peter Humphrey
2019-08-18 9:00 ` J. Roeleveld
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 0:51 [gentoo-user] nfs setup John Dangler
2005-09-01 2:08 ` Michael Crute
2005-09-01 2:16 ` John Dangler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=wYCE7bYXTGLSkqUWX2UCE2bBU-B+OK=_wAwfbSj5i1rVgPg@mail.gmail.com' \
--to=adamcarter3@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox