Hi Wolfgang,
I'm not using dhclient6, or dhcpv6 at all on the subnets I connect to. Checking my system I don't see dhclient6 running. Sounds like a similar problem though.I might try the updated policy package mentioned in your bz - but only if the changelog seems like it might help.
On Thu, Jan 23, 2014 at 10:07 AM, Wolfgang S. Rupprecht <wolfgang.rupprecht@xxxxxxxxx> wrote:
I'm seeing an IPv6 breakage in NetworkManager/dhclient6 too. At first
Dan Irwin <rummymobile@xxxxxxxxx> writes:
> Seeing significant issues with IPv6. After some time, IPv6 completely
> seems to stop working. IPv4 is unaffected.
it looked like an Selinux problem (there was an avc), but fixing that
didn't stop the problem with NM not getting a working IPv6 address via
dhclient6. BZ#1055226 https://bugzilla.redhat.com/show_bug.cgi?id=1055226
Mine is via an ethernet connection to my cable modem which connects to
> Re-connecting to wifi seems to restore IPv6 connectivity.
Comcast. I can do a "systemctl restart NetworkManager" in order to get
an ipv6 address.
-wolfgang
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org