From: Chuck Lever <chuck.lever@oracle.com>
To: ftn768@gmail.com
Cc: Jack Byer <ojbyer@usa.net>, linux-nfs@vger.kernel.org
Subject: Re: IPv6 and NFS4
Date: Mon, 03 May 2010 11:13:13 -0400 [thread overview]
Message-ID: <4BDEE809.8060501@oracle.com> (raw)
In-Reply-To: <544oecoS23680S01.1272897953@web01.cms.usa.net>
On 05/03/2010 10:45 AM, Jack Byer wrote:
> If I have an NFS4 server successfully sharing a directory with a client and
> both machines have valid IPv4 and IPv6 addresses should it be possible to
> mount the directory using either IPv4 or IPv6?
Yes, that should work if nfs-utils-1.2.2 is built with --enable-tirpc
and --enable-ipv6.
> Both machines are running 2.6.34-rc6 kernels, nfs-utils-1.2.2,
> libtirpc-0.2.0 and rpcbind-0.2.0. Mounting over IPv4 works perfectly, but
> IPv6 just times out while trying to mount the share. Using tcpdump I see
> that the two machines exchange 40 packets before the client finally gives
> up. There are no messages generated in the system log or dmesg of either
> machine.
Are the IPv6 addresses correctly registered with DNS? Have you tried
"mount.nfs4 ... -v" ? Or:
$ sudo rpcdebug -m nfs -s mount
will produce more syslogging.
--
chuck[dot]lever[at]oracle[dot]com
prev parent reply other threads:[~2010-05-03 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 14:45 IPv6 and NFS4 Jack Byer
2010-05-03 15:13 ` Chuck Lever [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=4BDEE809.8060501@oracle.com \
--to=chuck.lever@oracle.com \
--cc=ftn768@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ojbyer@usa.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 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).