From: Ferenc Wagner <wferi@niif.hu>
To: lvs-users@linuxvirtualserver.org
Cc: netdev@vger.kernel.org, robert.gallagher@heanet.ie,
Julius Volz <juliusv@google.com>
Subject: Re: Is CONFIG_IP_VS_IPV6 still/really dangerous?
Date: Sat, 05 Jun 2010 00:21:58 +0200 [thread overview]
Message-ID: <87aarah20p.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: <AANLkTikQPaHYuOOAiJtIft9NnOZ2S1LXTVMi_BLD8gau@mail.gmail.com> (Julius Volz's message of "Fri, 4 Jun 2010 16:14:37 +0200")
Julius Volz <juliusv@google.com> writes:
> On Fri, Jun 4, 2010 at 3:56 PM, Ferenc Wagner <wferi@niif.hu> wrote:
>
>> In commit fab0de02fb0da83b90cec7fce4294747d86d5c6f CONFIG_IP_VS_IPV6 is
>> described as:
>>
>> Add IPv6 support to IPVS. This is incomplete and might be dangerous.
>>
>> I agree its implementation is incomplete. But I wonder if it's really
>> dangerous in the sense that generic distribution kernels shouldn't
>> enable it, because it can break unrelated (eg. IPv4 IPVS) functionality.
>>
>> What does that warning mean today? Isn't it out of date?
>
> I wrote the IPv6 support back in the day, but never used it
> large-scale. Rob Gallagher from HEAnet was doing some bigger
> experiments with it, but I'm not sure how far it went. CCing him.
>
> There are probably some other people out there that have tested it
> extensively. Maybe try the lvs-users and lvs-devel mailing lists?
Sounds like a good idea! So:
Dear lvs-users,
did you experience any breakage as a result of switching on
CONFIG_IP_VS_IPV6? I mean apart from it having incomplete
functionality. The gist of the question is whether this option
is suitable for generic distro kernels or not, cf. above.
--
Thanks for your time,
Feri.
prev parent reply other threads:[~2010-06-04 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 13:56 Is CONFIG_IP_VS_IPV6 still/really dangerous? Ferenc Wagner
2010-06-04 14:14 ` Julius Volz
2010-06-04 22:21 ` Ferenc Wagner [this message]
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=87aarah20p.fsf@tac.ki.iif.hu \
--to=wferi@niif.hu \
--cc=juliusv@google.com \
--cc=lvs-users@linuxvirtualserver.org \
--cc=netdev@vger.kernel.org \
--cc=robert.gallagher@heanet.ie \
/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