From: Ian Kent <raven@themaw.net>
To: christof.koehler@bccms.uni-bremen.de
Cc: autofs@vger.kernel.org
Subject: Re: autofs reverts to IPv4 for multi-homed IPv6 server ?
Date: Wed, 27 Apr 2016 10:27:23 +0800 [thread overview]
Message-ID: <1461724043.4208.38.camel@themaw.net> (raw)
In-Reply-To: <1461722078.4208.31.camel@themaw.net>
On Wed, 2016-04-27 at 09:54 +0800, Ian Kent wrote:
> On Tue, 2016-04-26 at 17:27 +0200, Christof Koehler wrote:
> >
> > While I am at it I will see that basic IPv6 tests (with and without
> > libtirpc) are done in any case.
>
> That will be useful.
Don't forget that the glibc RPC implementation shouldn't work with IPv6
and autofs relies on RPC calls for it's proximity and availability
checks so IPv6 without libtirpc probably won't work and that's what we
have seen so far.
You can set some specific autofs configuration options to prevent the
proximity and availability checks for most cases in which case the host
name would be passed on to mount.nfs(8) and work ok for IPv6 mounting to
the extent that mount.nfs(8) does.
But that's not really testing autofs IPv6 handling though.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2016-04-27 2:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 14:19 autofs reverts to IPv4 for multi-homed IPv6 server ? Christof Koehler
2016-04-08 4:46 ` Ian Kent
2016-04-08 10:10 ` Ian Kent
2016-04-08 10:14 ` Ian Kent
2016-04-08 12:25 ` Christof Koehler
2016-04-08 14:29 ` Christof Koehler
2016-04-08 15:32 ` Christof Koehler
2016-04-10 2:09 ` Ian Kent
2016-04-08 16:12 ` Christof Koehler
2016-04-08 16:15 ` Christof Koehler
2016-04-10 2:17 ` Ian Kent
2016-04-10 2:14 ` Ian Kent
2016-04-09 1:42 ` Ian Kent
2016-04-09 9:56 ` Christof Koehler
2016-04-10 2:29 ` Ian Kent
2016-04-25 4:40 ` Ian Kent
2016-04-25 15:06 ` Christof Koehler
2016-04-26 1:06 ` Ian Kent
2016-04-26 9:53 ` Ian Kent
2016-04-26 15:27 ` Christof Koehler
2016-04-27 1:54 ` Ian Kent
2016-04-27 2:27 ` Ian Kent [this message]
2016-04-27 16:52 ` Christof Koehler
2016-04-28 2:56 ` Ian Kent
2016-04-28 3:21 ` Ian Kent
2016-04-28 9:12 ` Christof Koehler
2016-04-28 9:10 ` Christof Koehler
2016-04-28 10:50 ` Ian Kent
2016-04-28 11:26 ` Christof Koehler
2016-04-28 12:40 ` Christof Koehler
2016-04-29 1:54 ` Ian Kent
2016-04-29 14:10 ` Christof Koehler
2016-04-29 14:42 ` Christof Koehler
2016-04-30 3:21 ` Ian Kent
2016-04-30 11:36 ` Christof Koehler
2016-04-30 15:15 ` Christof Koehler
2016-04-30 15:16 ` Christof Koehler
2016-05-02 6:01 ` Ian Kent
2016-05-02 16:08 ` Christof Koehler
2016-05-03 7:58 ` Ian Kent
2016-05-03 15:13 ` Christof Koehler
2016-05-04 7:20 ` Ian Kent
2016-05-04 12:38 ` Christof Koehler
2016-04-09 1:35 ` Ian Kent
2016-04-11 2:42 ` Ian Kent
2016-04-11 16:32 ` Christof Koehler
2016-04-11 16:35 ` Christof Koehler
2016-04-12 1:07 ` Ian Kent
2016-04-08 11:47 ` Christof Koehler
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=1461724043.4208.38.camel@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=christof.koehler@bccms.uni-bremen.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.