Bug#441361: no support for NFS (v3) mount over IPv6?
SHG == Steinar H Gunderson sgunder...@bigfoot.com writes: [...] IS But mount.nfs doesn't find 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#441361: no support for NFS (v3) mount over IPv6?
On Sun, Sep 09, 2007 at 12:11:41AM -0700, Steve Langasek wrote: After rolling out IPv6 on my home network, I've taken a peek at whether I could switch my NFS shares to IPv6 as well, which would let me simplify my DNS resolution a bit. But mount.nfs doesn't find records for hosts, and it also can't parse numeric IPv6 addresses on account of all the colons. For the bug reference, preliminary IPv6-supporting packages (client side only) are available at: http://storage.sesse.net/nfs-ipv6/ I tested with 2.6.26 (works with NFSv3, but not NFSv4) and 2.6.28-rc3 (works with both), against a Solaris 10 server. I have no idea when upstream plans to incorporate this support, but I guess it's a possible target for squeeze. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441361: no support for NFS (v3) mount over IPv6?
Package: nfs-common Version: 1:1.1.1~git-20070709-3 Severity: important Tags: ipv6 After rolling out IPv6 on my home network, I've taken a peek at whether I could switch my NFS shares to IPv6 as well, which would let me simplify my DNS resolution a bit. But mount.nfs doesn't find records for hosts, and it also can't parse numeric IPv6 addresses on account of all the colons. A similar problem affects exportfs on the server side: exportfs: invalid netmask `48' for 2001:4830:1244:: Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441361: no support for NFS (v3) mount over IPv6?
severity 441361 wishlist thanks On Sun, Sep 09, 2007 at 12:11:41AM -0700, Steve Langasek wrote: After rolling out IPv6 on my home network, I've taken a peek at whether I could switch my NFS shares to IPv6 as well, which would let me simplify my DNS resolution a bit. But mount.nfs doesn't find records for hosts, and it also can't parse numeric IPv6 addresses on account of all the colons. Well, the kernel doesn't support NFS over IPv6. There's work being done in that direction (for instance, very recently the RPC client got IPv6 support, and both the NFS client and server is slowly being moved to a transport-independent system, the transport switch), but you simply cannot expect this to work on Linux at this stage. :-/ Believe me, when upstream adds support, Debian will be among the first distributions to support it, but for now, I cannot really see how this should be a bug of severity important. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
