From: "Bruce Allan" Subject: Re: rpc.statd and port usage... Date: Fri, 22 Mar 2002 11:33:59 -0800 Sender: nfs-admin@lists.sourceforge.net Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: nfs@lists.sourceforge.net, nfs-admin@lists.sourceforge.net To: "Steve Wolfe" Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: Use the -o and -p options to rpc.statd for outgoing requests and listening, respectively. See the manpage for statd. --- Bruce Allan Software Engineer, Linux Technology Center IBM Corporation, Beaverton OR 503-578-4187 IBM Tie-line 775-4187 "Steve Wolfe" To: Sent by: cc: nfs-admin@lists.sour Subject: [NFS] rpc.statd and port usage... ceforge.net 03/22/2002 11:13 AM On all of my machines, rpc.statd picks a (seemingly) random port < 1023, but one machine is acting differently: It will bind to one random port < 1023, then it will bind to both TCP and UDP on a high port, usually in the 32xxx range. Is that normal (or potentially normal) behavior, or should I be giving heed to the red lights and sirens that are going off in my head? If it is potentially normal, how would I go about making it use only low, priveliged ports, which are a lot easier to block at the firewall? steve _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs