From: Robert Rati <Robert.Rati@motorola.com>
Subject: rpc.mountd ports
Date: Wed, 12 Feb 2003 17:29:23 -0600
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <3E4AD8D3.3080603@motorola.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
To: nfs@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

When I start rpc.mountd, I notice that it always registers 4 ports with 
portmapper.  2 TCP and 2 UDP, which corespond to two separate instances 
of mountd.  When I run exportfs, I see that no file systems are being 
exported.  If I export a file system, the only difference is exportfs 
shows a file system being exported.  This will obviously cause a problem 
if I try to specify a port for rpc.mountd to run on as both instances of 
mountd try to use the same port and the tcp bind for the second instance 
fails.  Why does rpc.mountd start two instances of mountd?

This issue comes from trying to allow an NFS export through a firewall. 
  Since mountd uses a different port each time it starts, it's nearly 
impossible to pass it through a firewall.  Does anyone have an alternate 
solution to this problem besides telling rpc.mountd to run on a 
specified port (as that isn't working as detailed above).  I'm stuck 
using kernel 2.2.17, so I've been unable to check out the nfs-utils 
ability to handle specifying a port for mountd.  TIA.

Rob


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs