| 1 |
On Sun, Aug 18, 2019 at 7:11 PM Peter Humphrey <peter@××××××××××××.uk> |
| 2 |
wrote: |
| 3 |
|
| 4 |
> On Sunday, 18 August 2019 09:30:36 BST Adam Carter wrote: |
| 5 |
> |
| 6 |
> > Is the output of 'mount | grep nfs' the same on the two client machines? |
| 7 |
> |
| 8 |
> $ mount | grep nfs |
| 9 |
> nfsd on /proc/fs/nfsd type nfsd (rw,nosuid,nodev,noexec,relatime) |
| 10 |
> |
| 11 |
> |
| 12 |
nfs4 requires less ports than nfs3, just 2049 and something for mountd |
| 13 |
(IIRC). Try using nfs4 and setting up the firewall for 2049 and 32767 from |
| 14 |
your OPTS_RPC_MOUNTD="-p 32767" setting. From tcpdump, where .2 is the |
| 15 |
client and .250 is the server; |
| 16 |
192.168.1.2.949 > 192.168.1.250.2049: Flags [S] |
| 17 |
but the other session is |
| 18 |
192.168.1.250.730 > 192.168.1.2.40895: Flags [S] |
| 19 |
ie a low port on the nfs server makes a connection back to the client, so |
| 20 |
its quite unconventional |
| 21 |
|
| 22 |
FYI, here's what one of mine looks like |
| 23 |
$ mount | grep nfs |
| 24 |
192.168.1.250:/export/public on /mnt/public type nfs4 |
| 25 |
(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) |
| 26 |
|
| 27 |
$ grep nfs /etc/fstab |
| 28 |
192.168.1.250:/export/public /mnt/public nfs4 |
| 29 |
ro,_netdev,vers=4.0,soft,noatime 0 0 |
Archives