It seems you have to run rpcbind with -i flag:
-i ``insecure'' mode. Allows calls to SET and UNSET from an
host. Normally rpcbind accepts these requests only from the
loopback interface for security reasons. This change is necessary for
programs that were compiled with earlier versions of the rpc
library and do not make those requests using the loopback
interface.
# mount_nfs -o port=3049,intr localhost:/null /crypt
root@fuchur:~# mount
/dev/da0s2a on / (ufs, NFS exported, local, soft-updates)
devfs on /dev (devfs, local)
/dev/vinum/vol/vinum0 on /usr (ufs, NFS exported, local, soft-updates)
/dev/da0s2e on /var (ufs, local, soft-updates)
procfs on /proc (procfs, local)
linprocfs on /usr/compat/linux/proc (linprocfs, local)
localhost:/null on /crypt (nfs)
Martin
Martin Blapp, [EMAIL PROTECTED]
------------------------------------------------
Improware AG, UNIX solution and service provider
Zurlindenstrasse 29, 4133 Pratteln, Switzerland
Phone: +41 79 370 26 05, Fax: +41 61 826 93 01
------------------------------------------------
On Thu, 22 Mar 2001, Martin Blapp wrote:
>
> If you have not recompiled cfs, does starting the rpcbind with -L
> fix this ? Old binarys resist to work without this option.
>
> from rpcbind man-page:
>
> Allow old-style local connections over the loopback interface.
> Without this flag, local connections are only allowed over a
> local socket, /var/run/rpcbind.sock
>
> Martin
>
> Martin Blapp, [EMAIL PROTECTED]
> ------------------------------------------------
> Improware AG, UNIX solution and service provider
> Zurlindenstrasse 29, 4133 Pratteln, Switzerland
> Phone: +41 79 370 26 05, Fax: +41 61 826 93 01
> ------------------------------------------------
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
