From: Jeff Hanson <jhansonxi@gmail.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux NFS <linux-nfs@vger.kernel.org>
Subject: Re: NFS and firewalls
Date: Mon, 27 Dec 2010 21:58:49 -0500 [thread overview]
Message-ID: <AANLkTimqwRzCWBSb8yFjbq2pHrXvGKuDqM1SGvwMiA+-@mail.gmail.com> (raw)
In-Reply-To: <1293495170.9774.7.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Mon, Dec 27, 2010 at 7:12 PM, Trond Myklebust
<trond.myklebust@fys.uio.no> wrote:
> NFSv4.1 fully solves this problem. All connections to the server are
> initiated by the client, including for callback paths. The only port
> that needs to be accessible on the server side is port 2049.
>
> NFSv4 also solves the problem, with the one caveat that callbacks won't
> work behind a NAT (which basically means you won't get delegations).
>
Thanks. I made a note in the Ubuntu bug report.
next prev parent reply other threads:[~2010-12-28 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 23:32 NFS and firewalls Jeff Hanson
2010-12-28 0:12 ` Trond Myklebust
[not found] ` <1293495170.9774.7.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-12-28 2:58 ` Jeff Hanson [this message]
2010-12-28 3:26 ` Jim Rees
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=AANLkTimqwRzCWBSb8yFjbq2pHrXvGKuDqM1SGvwMiA+-@mail.gmail.com \
--to=jhansonxi@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).