From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeff Hanson <jhansonxi@gmail.com>
Cc: Linux NFS <linux-nfs@vger.kernel.org>
Subject: Re: NFS and firewalls
Date: Mon, 27 Dec 2010 19:12:50 -0500 [thread overview]
Message-ID: <1293495170.9774.7.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <AANLkTi=67a4C7Wx1zhoB-gAV_uXyzizenLmaEnbruy9i@mail.gmail.com>
On Mon, 2010-12-27 at 18:32 -0500, Jeff Hanson wrote:
> The random port usage of NFS makes it difficult to use with NAT/firewalls.
>
> The common workaround is to configure statd, mountd, lockd, and quotad
> to static ports. Since there isn't any standard (IANA registered) port
> assignments this breaks on many networks that use dynamic or different
> static ports.
>
> This makes it difficult to use the "standard" network file sharing
> protocol with mobile devices which often use firewalls.
>
> Saned, Samba (netbios), and FTP all have conntrack modules to handle
> dynamic port usage. Has there been any attempt to write one for NFS?
>
> I filed a bug with Ubuntu about it (#688446), mostly for psychological
> benefit as it's probably something they're not going to get involved
> with.
Neither am I.
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).
NFSv3 is the only protocol that actually has the problem you describe
above. We're working to deprecate it...
Cheers
Trond
next prev parent reply other threads:[~2010-12-28 0:12 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 [this message]
[not found] ` <1293495170.9774.7.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-12-28 2:58 ` Jeff Hanson
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=1293495170.9774.7.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=jhansonxi@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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).