Bug 569192

Summary: Good IPv4 eth0 connection marked invalid even when it is only IPv6 DHCP that failed
Product: [Fedora] Fedora Reporter: Al Thomas <astavale>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 12CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-02 02:52:16 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:
Attachments:
Description Flags
/var/log/messages - IP info obscured none

Description Al Thomas 2010-02-28 16:48:43 UTC
Created attachment 396886 [details]
/var/log/messages - IP info obscured

Description of problem:
NetworkManager has default set up of configuring both IPv4 and IPv6 connections on eth0. This works well.

Today the DHCP for IPv6 is not working with my ISP. NetworkManager then disables the connection so no Internet connectivity at all. 

/var/log/messages (attached) shows it is just the IPv6 negotiation that fails and the IPv4 is fine. 

This can be worked around by going to NetworkManager Edit Connections and changing IPv6 Settings method to 'Ignore'. This then allows the connection to be established with the Internet as IPv4 only.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.998-2.git20100106.fc12.i686

How reproducible:
Every time

Steps to Reproduce:
1. Click on NetworkManager icon to connect
2. 
3.
  
Actual results:
NetworkManager icon changes to show it is trying to connect then cross appears to show connection failed.

Expected results:
Connection should be made, but only using IPv4

Additional info:

Comment 1 Dan Williams 2010-03-02 02:52:16 UTC
I believe it's a bug that NM will try IPv6 by default; we should fix that.  For now it should only be on when you turn it on from the connection editor or your system configuration files (/etc/sysconfig/network-scripts/ifcfg-*) set it on.

With that in mind, duping to bug 565926.

*** This bug has been marked as a duplicate of bug 565926 ***