Bug 470807

Summary:	NetworkManager tries to start wlan0 even though eth0 is connected
Product:	Red Hat Enterprise Linux 5	Reporter:	Ben Levenson <benl>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED NOTABUG	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.3
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-11-10 21:44:33 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:

Description Ben Levenson 2008-11-10 12:38:54 UTC

Description of problem:
NetworkManager tries to start wlan0 even though eth0 is connected

Version-Release number of selected component (if applicable):
NetworkManager-gnome-0.7.0-0.11.svn4185.el5.x86_64
NetworkManager-0.7.0-0.11.svn4185.el5.x86_64
NetworkManager-0.7.0-0.11.svn4185.el5.i386
NetworkManager-glib-0.7.0-0.11.svn4185.el5.x86_64
NetworkManager-glib-0.7.0-0.11.svn4185.el5.i386

How reproducible:
100%

Steps to Reproduce:
1. upgrade laptop from 5.2 to 5.3
2. Start gnome
  
Actual results:
NetworkManager will make at least 3 attempts to start my wireless connection
even though I already have an IP on eth0

Additional info:
An additional wired connection is listed in the dropdown menu: "eth0" + "System 
eth0"

Comment 1 Dan Williams 2008-11-10 21:44:33 UTC

This is expected with 0.7 because it now supports multiple active devices, and connection sharing, etc...

If there are specific regressions in behavior due to this we should file them separately, but in general, the active device (the one that has the default route) will be the same device that NM 0.6 would have chosen.