All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Simkowiak <dereks@realloc.net>
To: nfs@lists.sourceforge.net
Subject: NFS + ssh (NFS HOWTO Question)
Date: Thu, 25 Sep 2003 17:08:34 -0700	[thread overview]
Message-ID: <3F738382.1040907@realloc.net> (raw)


      Hello,
	I have a quick question about the NFS Howto.  There is something in it 
that I do not understand.  I'm working on an ssh tunnel for NFS.


 From http://nfs.sourceforge.net/nfs-howto/security.html
--------------------------------------------------
For example, to have statd broadcast of port 32765 and listen on port 
32766, and mountd listen on port 32767, you would type:

# statd -p 32765 -o 32766
# mountd -p 32767

[...]

lockd is started by the kernel when it is needed. Therefore you need to 
pass module options (if you have it built as a module) or kernel options 
to force lockd to listen and respond only on certain ports.

If you are using loadable modules and you would like to specify these 
options in your /etc/modules.conf file add a line like this to the file:

options lockd nlm_udpport=32768 nlm_tcpport=32768
--------------------------------------------------

	In the above section it says how to force both lockd and statd onto 
certain ports.  But then a little further down on that same page, where 
it talks about NFS over ssh, it has this seemingly contradicting 
information:

--------------------------------------------------
It is not possible to ask statd or the locking manager to make requests 
to a particular port for a particular mount; therefore, any locking 
requests will cause statd to connect to statd on localhost, i.e., 
itself, and it will fail with an error. Any attempt to correct this 
would require a major rewrite of NFS.
--------------------------------------------------

	I do not understand what this means.  First I'm looking at the 
command-line (and module) options to set particular ports, and then 
further on the same page, it says "It is not possible to ask statd or 
the locking manager to make requests to a particular port for a 
particular mount".

	Could somebody elaborate for me?  What am I missing?  (Or is the 
section on ssh outdated?)

	Any help is greatly appreciated.

Thanks,
Derek Simkowiak



-------------------------------------------------------
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

                 reply	other threads:[~2003-09-26  0:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F738382.1040907@realloc.net \
    --to=dereks@realloc.net \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.