Notice: IPv6 breaking issues tentatively considered blocker for F17

[Conan Kudo (ニール・ゴンパ)]

On Fri, Mar 9, 2012 at 11:14 PM, Adam Williamson <awilliam at redhat.com>wrote:

> On Fri, 2012-03-09 at 20:54 -0800, Adam Williamson wrote:
> > Hey, folks. We made a fairly significant call at the blocker review
> > meeting today, and agreed to notify devel list and FESCo (I'll file a
> > FESCo ticket also) so everyone's aware and can raise objections if they
> > wish.
> >
> > The bug under discussion was
> > https://bugzilla.redhat.com/show_bug.cgi?id=591630 . The effect of the
> > bug is that, if you install Fedora OOTB (the bug applies to at least 15
> > and 16 as well as 17) on a system on an IPv6-only network, it will not
> > be able to connect to the network.
>
> To be more precise...DHCPv6 is blocked. So I guess if you used a static
> network config it would work.
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>

Considering how rare it is to use a static network config, a blocker on
DHCPv6 is definitely a good idea. I'm aware of at least a few networks that
are switching over to v6 internally and using 6to4 techniques to allow IPv4
services to work (which breaks quite a few streaming applications, like
Empathy's Google Talk voice/video chat). That being said, it would be
considered a v6-only network and it would be quite bad if Fedora couldn't
connect to it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120310/83cda1eb/attachment.html>