Subject: Re: Problems with NFS: Port mapper failure
To: David S. <davids@idiom.com>
From: Daniel Eggert <danieleggert@mac.com>
List: netbsd-help
Date: 10/17/2002 00:00:29
On onsdag, okt 16, 2002, at 22:46 Europe/Copenhagen, David S. wrote:

> On Wed, Oct 16, 2002 at 10:25:09PM +0200, Daniel Eggert wrote:
>>
>> I figured out, that it's a problem with ipfilter. How should i 
>> configre
>> ipfilter to let clients connect to the NFS server?
>
> 'rpcinfo -p <file server>' will show you the ports used by 
> 'portmapper',
> 'nfs', 'mountd', 'status', and 'nlockmgr'.  You're clients need access 
> to
> all of them.  The ports for 'portmapper' (111) and 'nfs' (2049) are
> constant.  The others in general aren't.  Change your '/etc/exports' or
> stop and re-start the daemons, and those ports will change.  But it's
> been my experience on NetBSD that once '/etc/exports' is fixed, the
> ports used by 'mountd', 'status', and 'nlockmgr' will also stay fixed.
> But that not the case on other systems, like Linux.
>
> David S.

With changing port number IPsec seems like the only way out without 
compromising security.

Daniel