[Bug 146252] Re: rpc.statd listend on a random UDP port regardless of startup arguments

[Rolf Leggewie]

Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as "Won't Fix".

** Changed in: nfs-utils (Ubuntu Hardy)
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/146252

Title:
  rpc.statd listend on a random UDP port regardless of startup arguments

Status in linux-nfs.org:
  Fix Released
Status in “nfs-utils” package in Ubuntu:
  Fix Released
Status in “nfs-utils” source package in Hardy:
  Won't Fix
Status in “nfs-utils” package in Debian:
  Fix Released

Bug description:
  Among other options, I have the following in /etc/defaults/nfs-common:

  # Options for rpc.statd.
  #   Should rpc.statd listen on a specific port? This is especially useful
  #   when you have a port-based firewall. To use a fixed port, set this
  #   this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
  #   For more information, see rpc.statd(8) or http://wiki.debian.org/?SecuringNFS
  STATDOPTS="--port 1000 --outgoing-port 999"

  When I /etc/init.d/nfs-common restart, arguments get passed to
  rpc.statd properly:

  statd     9964  0.0  0.0   1876   708 ?        Ss   12:30   0:00
  /sbin/rpc.statd --port 1000 --outgoing-port 999

  However, statd still listens on a UDP port that's random (in this case
  port 812):

  t# netstat -anp | grep rpc.statd
  tcp        0      0 0.0.0.0:1000            0.0.0.0:*               LISTEN     9964/rpc.statd      
  udp        0      0 0.0.0.0:812             0.0.0.0:*                          9964/rpc.statd      
  udp        0      0 0.0.0.0:1000            0.0.0.0:*                          9964/rpc.statd      
  unix  2      [ ]         DGRAM                    36015    9964/rpc.statd      

  Because of this today I had a conflict with CUPS, since statd decided
  randomly to listen on UDP port 631.

  Regardless of that, the defaults are also unacceptable for end user
  systems, because the NFS daemons randomize their listen poerts and are
  likely to interfere with CUPS and other services. The Ubuntu default
  should be statically assigned ports and the daemons should obide by
  those assignments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-nfs/+bug/146252/+subscriptions