From: Jeff Layton <jlayton@redhat.com>
To: Jim Rees <rees@umich.edu>
Cc: Valentijn Sessink <valentyn@blub.net>, linux-nfs@vger.kernel.org
Subject: Re: ipv6 + krb5, server status?
Date: Wed, 13 Oct 2010 09:52:16 -0400 [thread overview]
Message-ID: <20101013095216.5b9b31a7@corrin.poochiereds.net> (raw)
In-Reply-To: <20101013125656.GA5197@merit.edu>
On Wed, 13 Oct 2010 08:56:56 -0400
Jim Rees <rees@umich.edu> wrote:
> Valentijn Sessink wrote:
>
> Hello list,
>
> I found a lot of information on the subject NFS server, ipv6 + krb5, but
> not anything conclusive. So I tried it out; I got IPv6 +
> NFS4 to work, but only with sec=sys.
>
> When using sec=krb5, there seemed to be errors in gssd communication.
> (Ubuntu 10.04 with rpcbind instead of portmap; with nfs-utils-1.2.3 from
> nfs.sf.net, and with a 2.6.35-020635rc1-generic kernel package).
>
> Is this correct, i.e. svcgssd still needs to be adapted to IPv6? Or
> should NFS-server/IPv6/Kerberos on Linux just work, i.e. should I
> re-check my configuration?
>
> I don't know the specific answer to your question, but ipv6 support is still
> a work in progress, and I'm actually a bit surprised it works out of the box
> even with sec=sys.
>
> You may want to try the very latest ipv6 version of nfs-utils, which may
> have some patches that have not yet been merged upstream. You can get it
> from git://git.linux-nfs.org/projects/cel/nfs-utils.git . The usual
> warnings apply, this is experimental code, you could lose data, it may not
> work with your 2.6.35 kernel, and if you find bugs you can't necessarily get
> anyone to help you.
As of nfs-utils-1.2.3, IPv6 server-side support should be
"complete" (modulo bugs, of course).
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2010-10-13 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 10:57 ipv6 + krb5, server status? Valentijn Sessink
2010-10-13 12:56 ` Jeff Layton
2010-10-13 13:18 ` Valentijn Sessink
2010-10-13 12:56 ` Jim Rees
2010-10-13 13:52 ` Jeff Layton [this message]
2010-10-13 13:56 ` Valentijn Sessink
2010-10-13 14:49 ` Jeff Layton
2010-10-13 14:58 ` Jeff Layton
2010-10-20 11:01 ` Valentijn Sessink
2010-10-20 12:05 ` Jim Rees
2010-10-20 12:11 ` Valentijn Sessink
2010-10-20 12:50 ` Jim Rees
-- strict thread matches above, loose matches on Subject: below --
2010-10-09 14:19 Valentijn Sessink
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=20101013095216.5b9b31a7@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
--cc=valentyn@blub.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).