Re: Bug#441361: no support for NFS (v3) mount over IPv6?
>>>>> "SHG" == Steinar H Gunderson <sgunderson@bigfoot.com> writes:
[...]
IS> But mount.nfs doesn't find AAAA records for hosts, and it also
IS> can't parse numeric IPv6 addresses on account of all the colons.
SHG> For the bug reference, preliminary IPv6-supporting packages
SHG> (client side only)
I've got it. Sigh. I had some big plans for it. (Perhaps I
should change the Debian GNU/Linux server to something like
OpenSolaris? Just kidding, of course.)
And also:
http://article.gmane.org/gmane.linux.nfs/29288
http://article.gmane.org/gmane.linux.nfs/29294
--cut: http://article.gmane.org/gmane.linux.nfs/29294 --
Server side in the kernel is nearly done. There are a handful of small
patches outstanding. Until I have mountd working, there's no way to
test the server side pieces thoroughly. So for now, "completion" of
the server side is some time in the future.
> + userspace support
> - nfsd support has already been added but disabled temporarily till
> we get statd and mountd IPv6 aware.
> - making statd IPv6 aware is currently under development/review.
Basic support is code complete and has seen some testing. We're
waiting for upstream NFS maintainers to review the latest patch series.
> - mount.nfs changes - done?
The netid changes mentioned above will require some mount.nfs support,
which is in the works. 2.6.33, maybe?
> - rpc.mountd, exportfs changes - TBD.
These are the next step. This is going to be a fairly heavy-weight
change -- mountd and exportfs internals are unsuited for
internationalized domain names, IPv6, and mixed IPv4/IPv6 environments,
and will need to be replaced.
[...]
rpcbind and libtirpc are also prerequisites, but there are few
distributions I know of that have replaced portmapper with rpcbind.
> How far we are from getting full IPv6 support?
The short answer is mountd/exportfs will take about six months. The
client side is close enough that I think we can promise basic IPv6
support for upcoming enterprise releases. We're also thinking the
kernel work on the server is close enough that few or no kABI changes
will be needed once mountd is working, but that's just a guess.
--cut: http://article.gmane.org/gmane.linux.nfs/29294 --
--
FSF associate member #7257
Reply to: