From: Haakon Riiser <haakon.riiser@fys.uio.no>
Subject: Re: Random UDP port assignment for rpc.statd
Date: Sun, 20 Feb 2005 15:10:37 +0100
Message-ID: <20050220141037.GA7686@s>
References: <20050220111312.GA3974@s> <1108908221.27120.26.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: nfs@lists.sourceforge.net
To: Trond Myklebust <trond.myklebust@fys.uio.no>
In-Reply-To: <1108908221.27120.26.camel@lade.trondhjem.org>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

[Trond Myklebust]

> su den 20.02.2005 Klokka 12:13 (+0100) skreiv Haakon Riiser:

>> Why isn't it possible to specify all of statd's listening
>> ports using the -p flag?  It works for the TCP port and one
>> of the UDP ports, but there is always one more listening UDP
>> port that is randomly assigned.  [...]

> rpc.statd needs some ports for communication with the portmapper
> and the lockd manager on the loopback net, and this is probably
> what you are seeing. There should be nothing that needs to be
> allowed firewall access, though.

Actually, I wanted to /block/ this port in the firewall, not open
for external access.  My firewall allows everything by default, and
has rules to block ports that shouldn't be visible to the world.
Should I be concerned about this port being unblocked?

-- 
 Haakon


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs