NFS port

proxtib

Member
Dec 16, 2020
25
1
6
35
Hello,

I dont understant somthing with NFS.

My proxmox is not on the same network as my NAS. There is a router / firewall in between.

Code:
Proxmox - FW - NAS (=OpenMediaVault 5.6, NFSv4)


If I understood correctly with NFSv4 only ports 111 and 2049 are necessary.
So I have open this 2 ports on my FW and select "NFS version: 4" when try to add NFS storage.

But it but it does not work....
I look on my FW and I see frames blocked in the direction of my nas with port 44171, 45525 ...


I don't understand, why is proxmox sending frames with these ports to my NAS? NFSv4 only needs ports 111 and 2049, right?






PS: Theoretically not necessary with NFSv4, but I have set NFS port on my NAS:

Code:
# nano /etc/default/nfs-common

...
STATDOPTS="--port 32765 --outgoing-port 32766"
...
# nano /etc/default/nfs-kernel-server

...
RPCMOUNTDOPTS="-p 32767"
...
# nano /etc/default/quota

...
RPCRQUOTADOPTS="-p 32769"
...
# sysctl --system
# /etc/init.d/nfs-kernel-server restart
 
Even if I select NFSv4, is NFSv3 used? o_O

Anyway, which ports should I open on my FW?


Thanks for the help
 
I know it is quite old topic, but I had similar problem - accessing NFS shares from Proxmox on OpenMediavault.
What I need to do was set mountd port to be more "static":
file
Code:
/etc/default/nfs-kernel-server

Code:
...
RPCMOUNTDOPTS="--port 32767"
...

Pass on my Firewall ports: 111, 2049, 32767

On OpenMediavault it needs to be done "OMV way":
Code:
omv-env set -- OMV_NFSD_MOUNTDOPTS '--port 32767 --manage-gids'
monit restart omv-engined
omv-salt stage run prepare
omv-salt stage run deploy