From: Greg Banks <gnb@melbourne.sgi.com>
To: Guolin Cheng <guolin@alexa.com>
Cc: Ian Kent <raven@themaw.net>, Michael <mogmios@mlug.missouri.edu>,
nfs@lists.sourceforge.net
Subject: Re: auto-discovery of exports?
Date: Thu, 08 Apr 2004 12:02:37 +1000 [thread overview]
Message-ID: <4074B2BD.7936CF93@melbourne.sgi.com> (raw)
In-Reply-To: 41089CB27BD8D24E8385C8003EDAF7AB084850@karl.alexa.com
Guolin Cheng wrote:
>
> Sure, to your own networks, do you want to search all Internet for nfs
> servers? :)
>
> Run a "nmap -sU -p 2049 <your_net_work, like 192.168.0>" to find all nfs
> servers providing services on UDP, similar "nmap -p 2049 <your_net_work,
> like 192.168.0>" to find nfs servers on TCP.
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.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-04-08 2:03 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 [this message]
2004-04-08 6:54 ` Olaf Kirch
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=4074B2BD.7936CF93@melbourne.sgi.com \
--to=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.