NFS mount over IPv6 success
Subsystems (2)
Hi,
I'm sure others have gotten this to work at some point, but it's finally gotten to the point where I could get it to work myself, so I thought I could share my success story:
- Vanilla 2.6.28-rc3 client (2.6.26 also worked, although not with NFSv4)
- Solaris 10 server
- libtirpc from git (git://git.infradead.org/~steved/libtirpc.git)
- IPv6-patched nfs-utils from git
(git://git.linux-nfs.org/projects/cel/nfs-utils.git)
After recompiling (actually making Debian packages of) the client software, it was just a matter of mounting. 2.6.26 had some issues with IPv6 address literals -- only DNS worked -- but 2.6.28-rc3 did both just fine.
I haven't done extensive testing, but this looks pretty good :-) Now I'm just waiting for the server support to get ready in the same way, and then for everything to trickle into mainline.
/* Steinar */
Signature · 1 line
Homepage: http://www.sesse.net/
A message that is not in the archive (sent off-list or not yet received): 20081109164132.GA19615-6Z/[email protected]
Steinar-
Thanks for testing!
Keep an eye out for IPv6-related patches for nfs-utils. The key is to ensure IPv4 continues to work, especially on Debian which tracks upstream nfs-utils closely.
Quoted 17 lines · Steinar H. Gunderson
Hi,
I'm sure others have gotten this to work at some point, but it's finally gotten to the point where I could get it to work myself, so I thought I could share my success story:
- Vanilla 2.6.28-rc3 client (2.6.26 also worked, although not with NFSv4)
- Solaris 10 server
- libtirpc from git (git://git.infradead.org/~steved/libtirpc.git)
- IPv6-patched nfs-utils from git
(git://git.linux-nfs.org/projects/cel/nfs-utils.git)After recompiling (actually making Debian packages of) the client software, it was just a matter of mounting. 2.6.26 had some issues with IPv6 address literals -- only DNS worked -- but 2.6.28-rc3 did both just fine.
Quoted 11 lines
I haven't done extensive testing, but this looks pretty good :-) Now I'm just waiting for the server support to get ready in the same way, and then for everything to trickle into mainline.
/* Steinar */
Signature · 5 lines
Homepage: http://www.sesse.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
Quoted 3 lines · Chuck Lever
Keep an eye out for IPv6-related patches for nfs-utils. The key is to ensure IPv4 continues to work, especially on Debian which tracks upstream nfs-utils closely.
We don't plan to incorporate IPv6-specific patches before upstream does (and lenny, our upcoming release, is not going to get libtirpc or rpcbind). When upstream nfs-utils is ready, you can expect us to configure with --enable-ipv6 pretty quickly, though :-)
I still haven't had any success with nfsd on the server side in Linux; it's a bit unclear to me what nfs-utils to use in particular.
/* Steinar */
Signature · 1 line
Homepage: http://www.sesse.net/
A message that is not in the archive (sent off-list or not yet received): 20081112133553.GA32294-6Z/[email protected]
Steinar H. Gunderson a =C3=A9crit :
Quoted 4 lines · Chuck Lever
=20
Quoted 1 line
Keep an eye out for IPv6-related patches for nfs-utils. The key is t=
o =20
Quoted 6 lines
Quoted 4 lines
ensure IPv4 continues to work, especially on Debian which tracks =20 upstream nfs-utils closely.
=20We don't plan to incorporate IPv6-specific patches before upstream doe=
s (and
Quoted 1 line
lenny, our upcoming release, is not going to get libtirpc or rpcbind).=
When
Quoted 4 lines
upstream nfs-utils is ready, you can expect us to configure with --enable-ipv6 pretty quickly, though :-)
I still haven't had any success with nfsd on the server side in Linux;=
it's a
Quoted 5 lines
bit unclear to me what nfs-utils to use in particular.
/* Steinar */
=20
Hi,
There is a prototype nfs-utils package based on nfs-utils-1.1.2 you ca= n=20
play with at http://nfsv4.bullopensource.org/
Regards
--=20
-----------------------------------------------------------------
Company : Bull, Architect of an Open World TM (www.bull.com)
Name : Aime Le Rouzic=20
Mail : Bull - BP 208 - 38432 Echirolles Cedex - France
E-Mail : [email protected]
Phone : 33 (4) 76.29.75.51
=46ax : 33 (4) 76.29.75.18
-----------------------------------------------------------------=20
Quoted 23 lines · On Nov 12, 2008, at 11:05 AM, Le Rouzic wrote:
Steinar H. Gunderson a =E9crit :
Quoted 21 lines · Chuck Lever
Quoted 8 lines
Keep an eye out for IPv6-related patches for nfs-utils. The key =20 is to
ensure IPv4 continues to work, especially on Debian which tracks upstream nfs-utils closely.We don't plan to incorporate IPv6-specific patches before upstream =20 does (and
lenny, our upcoming release, is not going to get libtirpc or =20 rpcbind). When
upstream nfs-utils is ready, you can expect us to configure with --enable-ipv6 pretty quickly, though :-)I still haven't had any success with nfsd on the server side in =20 Linux; it's a
bit unclear to me what nfs-utils to use in particular.
Quoted 7 lines
Quoted 3 lines
/* Steinar */
Hi,
There is a prototype nfs-utils package based on nfs-utils-1.1.2 you =20 can
play with at http://nfsv4.bullopensource.org/
Oops. Sorry, I forgot about that.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
Quoted 2 lines · On Wed, Nov 12, 2008 at 05:05:13PM +0100, Le Rouzic wrote:
There is a prototype nfs-utils package based on nfs-utils-1.1.2 you can play with at http://nfsv4.bullopensource.org/
I already tried that with the latest git tree from Chuck, but no go (statd/nfsd didn't register on IPv6 in rpcbind, IIRC).
/* Steinar */
Signature · 1 line
Homepage: http://www.sesse.net/
A message that is not in the archive (sent off-list or not yet received): 20081112163727.GA31625-6Z/[email protected]
Quoted 6 lines · Steinar H. Gunderson
Quoted 2 lines · On Wed, Nov 12, 2008 at 05:05:13PM +0100, Le Rouzic wrote:
There is a prototype nfs-utils package based on nfs-utils-1.1.2 you can play with at http://nfsv4.bullopensource.org/
I already tried that with the latest git tree from Chuck, but no go (statd/nfsd didn't register on IPv6 in rpcbind, IIRC).
My nfs-utils doesn't have any of Bull's server-side changes. It also doesn't have an IPv6-enabled rpc.statd yet.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
Quoted 6 lines · Chuck Lever
Quoted 4 lines
Quoted 2 lines
There is a prototype nfs-utils package based on nfs-utils-1.1.2 you can play with at http://nfsv4.bullopensource.org/
I already tried that with the latest git tree from Chuck, but no go (statd/nfsd didn't register on IPv6 in rpcbind, IIRC).
My nfs-utils doesn't have any of Bull's server-side changes. It also doesn't have an IPv6-enabled rpc.statd yet.
I used Bull's nfs-utils -- the git tree I was referring to was your kernel tree, not nfs-utils. :-)
Perhaps things would be better if I used Bull's kernel as well, but 2.6.27 has other issues for me, so it's hard to test on my machine.
/* Steinar */
Signature · 1 line
Homepage: http://www.sesse.net/
Quoted 9 lines · Steinar H. Gunderson
Quoted 3 lines · Chuck Lever
Keep an eye out for IPv6-related patches for nfs-utils. The key is to ensure IPv4 continues to work, especially on Debian which tracks upstream nfs-utils closely.
We don't plan to incorporate IPv6-specific patches before upstream does (and lenny, our upcoming release, is not going to get libtirpc or rpcbind). When upstream nfs-utils is ready, you can expect us to configure with --enable-ipv6 pretty quickly, though :-)
We need testing to ensure that the latest nfs-utils still works on legacy systems, built with --disable-ipv6 and no libtirpc. So please do test my patches and report issues there.
Quoted 2 lines
I still haven't had any success with nfsd on the server side in Linux; it's a bit unclear to me what nfs-utils to use in particular.
Server side NFS doesn't have any user space IPv6 support yet. The kernel in my tree supports NFSv4 service over IPv6, but I don't think /etc/exports supports IPv6 addresses yet.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com