Bug 798697
| Summary: | The default IPv6 mode is "Ignore" for implicit/ifcfg-less connection profiles (e.g. wired ethernet) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tore Anderson <tore> | ||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 17 | CC: | awilliam, cra, dcbw, robatino, satellitgo | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | AcceptedBlocker | ||||||||
| Fixed In Version: | NetworkManager-0.9.3.997-0.7.fc17 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-03-21 18:47:51 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 195271, 752649 | ||||||||
| Attachments: |
|
||||||||
|
Description
Tore Anderson
2012-02-29 15:44:36 UTC
My suspicion was correct, the patch in http://mail.gnome.org/archives/networkmanager-list/2011-August/msg00063.html (Which still applies cleanly) does indeed solve the problem. I'll update the title accordingly. Tore Actually, only the last chunk of the above patch is relevant for this bug. Tore Nominating for F17 blocker. According to a post by Adam Williamson: «IPv6 breaking issues tentatively considered blocker for F17», see http://thread.gmane.org/gmane.linux.redhat.fedora.devel/160775. The issue at hand is that NetworkManager considers the default IPv6 mode for configuration-less profiles to be "ignore". This means that the kernel might configure IPv6 routing and addresses (learned from SLAAC only), however, DHCPv6 will never be started and no IPv6 DNS servers will be added to /etc/resolv.conf. Furthermore, NetworkManager will not consider the IPv6 connection to have been successful. Even if IPv6 routing and addressing has been configured by the kernel, the lack of configured DNS servers means that the network connection is essentially unusable for almost every use case. Notably, the default wired ethernet connection profile in Fedora 17 is such an implicit connection profile (no ifcfg file) which triggers this problem. It is worth noting that apart for the obvious lack of support for IPv6 network, the bug also leads to an inconsistent user experience for the following two reasons: - The nm-connection-editor utility shows that the IPv6 mode is "Automatic" for the implicit connection profile in question. - When connecting to wireless networks by clicking on their SSID in the nm-applet's drop-down list (and optionally entering a PSK), the resulting IPv6 mode is by default "Automatic". Tore Created attachment 569078 [details]
Change default IPv6 mode for implicit profile to Automatic
This patch changes the default IPv6 mode for configuration-less/implicit connection profiles from Ignore to Automatic.
This brings it in line with the defaults in nm-connection-editor as well as the default for wireless networks.
Toreg
Discussed at 2012-03-16 blocker review meeting. Accepted as a blocker bug per criterion "The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops" in the context of an IPv6-only connection. Dan says that he is going to accept this patch, but rework it not to apply to mobile broadband connections. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers NetworkManager-0.9.3.997-0.7.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/NetworkManager-0.9.3.997-0.7.fc17 Package NetworkManager-0.9.3.997-0.7.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.3.997-0.7.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4188/NetworkManager-0.9.3.997-0.7.fc17 then log in and leave karma (feedback). NetworkManager-0.9.3.997-0.7.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |