All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Guolin Cheng <guolin@alexa.com>, Ian Kent <raven@themaw.net>,
	Michael <mogmios@mlug.missouri.edu>,
	nfs@lists.sourceforge.net
Subject: Re: auto-discovery of exports?
Date: Thu, 8 Apr 2004 08:54:13 +0200	[thread overview]
Message-ID: <20040408065413.GA19702@suse.de> (raw)
In-Reply-To: <4074B2BD.7936CF93@melbourne.sgi.com>

On Thu, Apr 08, 2004 at 12:02:37PM +1000, Greg Banks wrote:
> You shouldn't rely on port 2049 for pre-v4 NFS.  To enumerate NFS servers
> try doing a broadcast RPC of a NULL call to RPC program 100003.

No, that won't help. Many portmappers are quite restrictive in what
they forward via PMAP_CALL. NFS and MOUNT calls are not among them for
security reasons (because by bouncing your request off portmap, the NFS
server will see a request from 127.0.0.1 - and may grant you more rights
than you would get ordinarily).

Some portmaps may actually allow calls to the NFS NULL procedure, but
many don't.

Broadcasts to 2049 may not work either if the daemon binds to all interface
addresses rather than INADDR_ANY.

I wrote a tool for enumerating NFS servers a long time back, and found
the only way to go about it is to enumerate all hosts first, then do a
pmap_getport(100005), and then call each mountd i turn.

Alternatively you could set up an SLP directory, and change your nfsd startup
scripts to register all nfsd's via SLP.

Olaf
-- 
Olaf Kirch     |  The Hardware Gods hate me.
okir@suse.de   |
---------------+ 


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-04-08  6:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08  1:44 auto-discovery of exports? Guolin Cheng
2004-04-08  2:02 ` Greg Banks
2004-04-08  6:54   ` Olaf Kirch [this message]
2004-04-08  7:07     ` Greg Banks
2004-04-08  8:55       ` Olaf Kirch
2004-04-11  9:44         ` Greg Banks
  -- strict thread matches above, loose matches on Subject: below --
2004-04-07 23:01 Guolin Cheng
2004-04-08  0:37 ` Ian Kent
2004-04-08  5:34   ` Bryan O'Sullivan
2004-04-08 10:29 ` Michael
2004-04-07  8:03 Michael

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=20040408065413.GA19702@suse.de \
    --to=okir@suse.de \
    --cc=gnb@melbourne.sgi.com \
    --cc=guolin@alexa.com \
    --cc=mogmios@mlug.missouri.edu \
    --cc=nfs@lists.sourceforge.net \
    --cc=raven@themaw.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.