From: Jim Rees <rees@umich.edu>
To: Jeff Hanson <jhansonxi@gmail.com>
Cc: Linux NFS <linux-nfs@vger.kernel.org>
Subject: Re: NFS and firewalls
Date: Mon, 27 Dec 2010 22:26:32 -0500 [thread overview]
Message-ID: <20101228032632.GA10718@merit.edu> (raw)
In-Reply-To: <AANLkTi=67a4C7Wx1zhoB-gAV_uXyzizenLmaEnbruy9i@mail.gmail.com>
Jeff Hanson wrote:
The random port usage of NFS makes it difficult to use with NAT/firewalls.
Assuming you mean v3, I've done this by setting nolock in the mount options
and bypassing the mount protocol by configuring the root file handle on the
client manually.
Others have noted that v4 solves this problem. IPv6 eliminates the need for
NAT, if your client and server support it and your network will pass the
packets.
prev parent reply other threads:[~2010-12-28 3:26 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
2010-12-28 3:26 ` Jim Rees [this message]
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=20101228032632.GA10718@merit.edu \
--to=rees@umich.edu \
--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).