From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: chuck.lever@oracle.com
Cc: nfs@lists.sourceforge.net, Steve Dickson <SteveD@redhat.com>
Subject: Re: Status of mount.nfs
Date: Fri, 03 Aug 2007 09:02:51 -0400 [thread overview]
Message-ID: <1186146171.7255.6.camel@localhost> (raw)
In-Reply-To: <46B24FEA.1040300@oracle.com>
On Thu, 2007-08-02 at 17:43 -0400, Chuck Lever wrote:
> Trond Myklebust wrote:
> > On Thu, 2007-08-02 at 12:20 -0400, Chuck Lever wrote:
> >
> >> I'm not suggesting that we don't support mounting through a firewall.
> >> I'm wondering, though, how people expect it to work. Is it acceptable
> >> to require a few extra mount options on clients to mount successfully
> >> through a firewall, or should a mount with no options whatsoever always
> >> work in this case?
> >
> > The strategy should be to make the _default_ behaviour safe. If you want
> > to add optimisations that need switching on/off then those may take
> > extra mount options.
>
> Exactly: is mounting through a firewall an optimization, or is it
> something that users expect, by default, to work without using extra
> options?
If the user has opened the firewall for outgoing TCP connections, then
that is one of the things that I think should just work.
It doesn't need to work with maximum efficiency (so if you want to try
sending UDP portmap requests before falling back to TCP, then fine) but
opening UDP ports in the firewall or specifying extra mount options
should not be a requirement.
Trond
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-03 13:03 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 19:16 Status of mount.nfs Steinar H. Gunderson
2007-07-08 23:16 ` Chuck Lever
2007-07-09 3:17 ` Neil Brown
2007-07-09 9:55 ` Steinar H. Gunderson
2007-07-09 16:45 ` Chuck Lever
2007-07-10 0:08 ` Neil Brown
2007-07-15 8:31 ` Steinar H. Gunderson
2007-07-16 1:13 ` Neil Brown
2007-07-16 9:20 ` Steinar H. Gunderson
2007-07-16 10:15 ` Neil Brown
2007-07-22 19:17 ` Steinar H. Gunderson
2007-07-22 21:58 ` Trond Myklebust
2007-07-22 22:04 ` Steinar H. Gunderson
2007-07-24 17:51 ` Trond Myklebust
[not found] ` <46A52816.6050500@oracle.com>
2007-07-24 17:24 ` Steinar H. Gunderson
2007-07-24 17:50 ` Trond Myklebust
2007-07-24 17:55 ` Steinar H. Gunderson
2007-07-24 20:46 ` Chuck Lever
2007-07-24 21:10 ` Trond Myklebust
2007-07-24 21:18 ` Chuck Lever
2007-07-25 2:08 ` rpcbind behavior on Fedora 7 Chuck Lever
2007-07-25 19:35 ` Status of mount.nfs Chuck Lever
2007-07-26 12:47 ` Steve Dickson
2007-07-27 3:02 ` Chuck Lever
2007-07-27 15:00 ` Steve Dickson
2007-07-27 15:56 ` Trond Myklebust
2007-07-27 16:16 ` Steve Dickson
2007-07-27 16:27 ` Trond Myklebust
2007-07-27 17:07 ` Steve Dickson
2007-07-27 17:13 ` Trond Myklebust
2007-07-27 21:38 ` Chuck Lever
2007-07-28 12:51 ` Steve Dickson
2007-07-31 18:30 ` Trond Myklebust
2007-07-31 21:28 ` Chuck Lever
2007-08-01 10:58 ` Steve Dickson
2007-08-01 20:02 ` Chuck Lever
2007-08-01 21:12 ` Steve Dickson
2007-08-02 16:20 ` Chuck Lever
2007-08-02 18:42 ` Trond Myklebust
2007-08-02 21:43 ` Chuck Lever
2007-08-03 13:02 ` Trond Myklebust [this message]
2007-08-02 20:46 ` Steve Dickson
2007-07-27 19:37 ` Chuck Lever
2007-07-28 13:20 ` Steve Dickson
2007-07-28 21:00 ` Chuck Lever
2007-07-29 19:24 ` Steve Dickson
2007-07-30 4:14 ` Chuck Lever
2007-07-24 23:41 ` Steinar H. Gunderson
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=1186146171.7255.6.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.com \
--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.