Red Hat Bugzilla – Bug 463651
[LTC 6.0 FEAT] 201320:IPv6 support in NFS (user space)
Last modified: 2010-07-02 15:37:24 EDT
Emily J. Ratliff <firstname.lastname@example.org> - 2008-09-16 18:11 EDT
1. Feature Overview:
Feature Id: 
a. Name of Feature: IPv6 support in NFS (user space)
b. Feature Description
To add the support of IPv6 in NFS. This feature is for user space part. The NFS
commands/tools/utils packages are available since 1.0.10.
2. Feature Details:
Arch Specificity: Purely Common Code
Category: Remote Filesystems
Request Type: Other
d. Upstream Acceptance: Accepted
Sponsor Priority 1
f. Severity: High
IBM Confidential: no
Code Contribution: 3rd party code
g. Component Version Target: nfs-utils 1.0.10 -> userspace tools
3. Business Case
IPv6 support in NFS is needed for several customers and is required for some government contracts
(all DoD contracts).
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Sarah Wright, email@example.com, 503-578-5145
Frank Filz, firstname.lastname@example.org
Varun Chandramohan, email@example.com
Jeffrey Heroux, firstname.lastname@example.org
We currently ship nfs-utils-1.1.3 in Fedora.
The feature requested has already been accepted into the upstream code base
planned for the next major release of Red Hat Enterprise Linux.
When the next milestone release of Red Hat Enterprise Linux 6 is available,
please verify that the feature requested is present and functioning as
Varun is no longer working on this.
Here is an update from Chuck Lever on the status of NFS support fpor IPv6:
On Jan 28, 2009, at Jan 28, 2009, 2:34 PM, Frank S Filz wrote:
> I'm trying to determine the current status of IPv6 support for NFS.
> I understand support is nearly complete but a few pieces may not be
> quite complete.
You should be able to mount NFSv4 servers from the Linux NFS client in
2.6.28, using the mount.nfs command from the latest nfs-utils.
Callback over IPv6 is supported, and maybe referral too.
With 2.6.30, IPv6 will be supported in all the kernel NFS client and
server components (rpcbind and mountd client, NLM, NSM, NFS client,
and NFSD), though I wager it will need some shake-down time as user
space support for IPv6 is still lagging.
Distributions need to carry the new libtirpc and replace their
portmapper with rpcbind. Fedora, so far, is the only one that is
doing this, although I think RHEL 6 and the next release of OpenSUSE
will have it too.
The next upstream release of nfs-utils will have showmount and
complete [u]mount.nfs support for IPv6 (necessary for mounting NFSv2/
v3 servers over IPv6, but not sufficient).
I have sm-notify support done, and am working on rpc.statd now for
testing at Connectathon 2009. This will complete client side support
for NFSv2/v3 over IPv6, and is also necessary but not sufficient for
server side NFSv2/v3 over IPv6.
The next piece is rpc.mountd and exportfs to complete server side IPv6
support, as NFS server access control is IP address-based. Bull had
something here, but I haven't seen that work, and they've been defunded.
We haven't looked at Kerberos (GSSAPI) yet, but I don't think there
will be significant issues there. Jeff (cc added) might be looking at
IBM is signed up to test and provide feedback
Fixed in 'nfs-utils-1.2.0-10.el6', included in compose 'RHEL6.0-20091029.0'.
Moving to ON_QA.
------- Comment From email@example.com 2009-11-02 14:53 EDT-------
Chuck Lever just posted an update on status:
Since this has been accepted by Red Hat , moving to Accepted
------- Comment From firstname.lastname@example.org 2010-03-04 16:04 EDT-------
Status has been upated here:
There is also a pointer to the Connectathon 2010 presentation on IPv6 which may be a bit more up to date than the wiki page.
------- Comment From email@example.com 2010-05-28 12:35 EDT-------
This feature has been verified. Only NFS v4 was tested since we didn't have a IPv6 capable NFS v3 server.
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.