Get RPC: Program/version mismatch if I set OPTS_RPC_MOUNTD and OPTS_RPC_STATD in /etc/conf.d/nfs
Apparently, though unproven, at 07:03 on Tuesday 09 November 2010, Andrey F.
did opine thusly:
> Hi everyone,
> I am getting a strange error when I try to mount my nfs partitions.
> In /etc/conf.d/nfs I have:
> OPTS_RPC_MOUNTD="-p 32767"
> OPTS_RPC_STATD="-p 32765 -o 32766"
> I set these two options so that I can use nfs with iptables. If don't set
> these two variables, I wind up not being able to mount the nfs partitions
> because the ports for statd and mountd are selected at random.
> With the variables set, I get the following error:
> # mount -o vers=3 10.1.1.1:/nfs /mnt/temp -v
> mount: no type was given - I'll assume nfs because of the colon
> mount.nfs: timeout set for Mon Nov 8 20:47:30 2010
> mount.nfs: trying text-based options 'vers=3,addr=10.1.1.1'
> mount.nfs: prog 100003, trying vers=3, prot=6
> mount.nfs: trying 10.1.1.1 prog 100003 vers 3 prot TCP port 2049
> mount.nfs: prog 100005, trying vers=3, prot=17
> mount.nfs: trying 10.1.1.1 prog 100005 vers 3 prot UDP port 32767
> mount.nfs: portmap query retrying: RPC: Program/version mismatch
> mount.nfs: prog 100005, trying vers=3, prot=6
> mount.nfs: trying 10.1.1.1 prog 100005 vers 3 prot TCP port 32767
> mount.nfs: portmap query failed: RPC: Program/version mismatch
> mount.nfs: Operation not permitted
> Does anyone know why this is happening? How can I make nfs and iptables
> play nice?
Have you used tcpwrappers instead of iptables?
I'd give that a try (unless you need some functionality of iptables and aren't
just merely restricting access). Then you can remove the added complexity you
had to introduce.
alan dot mckinnon at gmail dot com