From: Erik Enge <eenge@prium.net>
To: nfs@lists.sourceforge.net
Subject: Multiple mounts to a rpc.mountd with port specified.
Date: 25 Nov 2002 12:20:13 -0500 [thread overview]
Message-ID: <871y59efci.fsf@prium.net> (raw)
Hi.
I'm currently setting up NFS through a firewall and my current strategy
(which seems to work fine) is to specify a port for the rpc.mountd so I
can predict what to open on the firewall.
Will this impede performance or functioning at all with multiple mounts
(over the same port)?
I have opened ports 111, 2049 and 32700 (port for mountd) on the
firewall and from the logs I can see that I'm not dropping any packets.
I am also running lockd, so does this mean that lockd uses 111, 2049 or
32700 or is it not running? Is there a specific port for lockd or do I
specify the port on rpc.statd and then lockd will use that?
Thanks for any answers,
Erik Enge
Software Engineer
Professional Reviews Inc.
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2002-11-25 17:26 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=871y59efci.fsf@prium.net \
--to=eenge@prium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox