Bug 429710 - Full IPv6 Support for Network Manager
Full IPv6 Support for Network Manager
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Dan Williams
: FutureFeature
Depends On: 196482
  Show dependency treegraph
Reported: 2008-01-22 11:25 EST by Daniel Riek
Modified: 2010-07-02 14:46 EDT (History)
10 users (show)

See Also:
Fixed In Version: NetworkManager-0.8.0-0.1.git20100122.el6
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-02 14:46:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 1 Dan Williams 2008-07-02 21:57:53 EDT
IPv6 support is getting added upstream over the next month or so; David Cantrell
is leading this effort.
Comment 2 Dan Williams 2010-02-05 19:21:45 EST
Much of this is awaiting tags into RHEL6 in 0.8-0.1.git20100122
Comment 4 Tore Anderson 2010-02-19 17:04:51 EST
Fixed?  Cool!  Does this also mean that the following bugs are now resolved?


That would truly be awesome...

Comment 5 Tore Anderson 2010-03-24 14:59:27 EDT

I think the subscribers to this bug might find this comment interesting:


It describes my testing the IPv6 capabilites of F13 Alpha (with NetworkManager 0.8.0-0.4.git20100211, so newer than what was mentioned in comment #2).  The very disappointing conclusion is that NM doesn't currently support IPv6 in any usable way whatsoever.

Comment 7 Dan Williams 2010-06-08 16:52:29 EDT
Recent NM builds (since early May) have full IPv6 support.
Comment 8 Vladimir Benes 2010-06-09 09:07:23 EDT
https://bugzilla.redhat.com/show_bug.cgi?id=569485 finally resolved so we can VERIFY this bug.
Comment 9 releng-rhel@redhat.com 2010-07-02 14:46:12 EDT
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.