Advertisement

11.19.2008 at 02:02PM PST, ID: 23919739
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.4

Specifically setting NFS ports, rogue statd port

Asked by mynamebecory2 in NFS File Server, Linux Network Security, Ubuntu

I have NFS set up on a server using static ports due to having iptables running on the same machine.  I set up mountd, lockd, and statd to use specific ports, but on reboot statd uses one of the ports I specified and additionally picks a dynamic port in the 6xx range.  I have confirmed this with netstat, see below

tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      3417/portmap    
tcp        0      0 0.0.0.0:32765           0.0.0.0:*               LISTEN      3436/rpc.statd  
tcp        0      0 0.0.0.0:32767           0.0.0.0:*               LISTEN      3904/rpc.mountd
udp        0      0 0.0.0.0:644             0.0.0.0:*                           3436/rpc.statd  <-- The elusive port
udp        0      0 0.0.0.0:111             0.0.0.0:*                           3417/portmap    
udp        0      0 0.0.0.0:32765           0.0.0.0:*                           3436/rpc.statd  
udp        0      0 0.0.0.0:32767           0.0.0.0:*                           3904/rpc.mountd

I am running on Ubuntu 8.04 and have done the following:
/etc/default/nfs-common
  STATDOPTS="--port 32765 --outgoing-port 32766"

/etc/default/nfs-kernel-server
  RPCMOUNTDOPTS="-p 32767"

/etc/modprobe.d/options
options lockd nlm_udpport=32768 nlm_tcpport=32768

Any help is appreciated.Start Free Trial
[+][-]11.19.2008 at 02:21PM PST, ID: 22999343

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: NFS File Server, Linux Network Security, Ubuntu
Sign Up Now!
Solution Provided By: mynamebecory2
Participating Experts: 0
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 - Hierarchy / EE_QW_2_20070628