From: Raphael Clifford <raphael@clifford.net>
To: nfs@lists.sourceforge.net
Subject: solaris server and firewalls
Date: Wed, 27 Aug 2003 21:11:53 +0100 [thread overview]
Message-ID: <3F4D1089.2050207@clifford.net> (raw)
Hi,
I am trying to mount a solaris nfs server from my linux client. The
problem is how to do this without effectively disabling the linux firewall.
I understand that the official Sun solution for Sun clients is to mount
using the -o public option. However, I can't find any support for this
in linux. I have copied a section of the man page below for completeness
that describes what this option does. My questions are
a) What can I do?
b) Could the answer be added to the firewall section of the HOWTO. It
must be a common situation. Where I work, for example, there are
hundreds of linux clients per Solaris server.
Cheers,
Raphael
------- excerpt from Solaris man page --------------
URLs and the public option
If the public option is specified, or if the resource
includes and NFS URL, mount will attempt to connect to
the server using the public file handle lookup proto-
col. See Internet RFC 2054 - WebNFS Client Specifica-
tion. If the server supports the public file handle,
the attempt is successful; mount will not need to con-
tact the server's rpcbind(1M), and the mountd(1M) dae-
mons to get the port number of the mount server and
the initial file handle of pathname, respectively. If
the NFS client and server are separated by a firewall
that allows all outbount connections through specific
ports, such as NFS_PORT, then this enables NFS opera-
tions through the firewall. The public option and the
NFS URL can be specified independently or together.
They interact as specified in the following matrix:
[...]
and from the Solaris docs
How to Mount an NFS File System Through a Firewall
1.
Become superuser.
2.
Manually mount the file system, using a command like:
# *mount -F nfs -o public bee:/export/share/local /mnt*
In this example the file system /export/share/local is mounted on
the local client using the public file handle. An NFS URL can be
used instead of the standard path name. If the public file handle
is not supported by the server bee, the mount operation will fail.
------------------------------------------------------------------------
*Note - *
This procedure requires that the file system on the NFS server be
shared using the public option and any firewalls between the
client and the server allow TCP connections on port 2049. Starting
with the 2.6 release, all file systems that are shared allow for
public file handle access.
-------------------------------------------------------
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
next reply other threads:[~2003-08-27 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 20:11 Raphael Clifford [this message]
2003-09-08 11:09 ` solaris server and firewalls Raphael Clifford
2003-09-12 12:29 ` Ion Badulescu
2003-09-14 18:32 ` Raphael Clifford
2003-09-23 13:21 ` Ion Badulescu
2003-09-23 15:43 ` Raphael Clifford
2003-09-23 18:08 ` Ion Badulescu
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=3F4D1089.2050207@clifford.net \
--to=raphael@clifford.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.