Bug 437044

Summary:	auto-connects things it shouldn't, breaks
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	CC:	dcbw, rvokal, wtogami
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:	2008-03-12 17:42:19 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 Bill Nottingham 2008-03-11 21:02:38 UTC

Description of problem:

I have a normal automatic ethernet device. It's connected, with IP, etc.

Randomly afterwards, NM will connect via wireless, completely hosing the system
(there's nothing in resolv.conf, for example.)

Version-Release number of selected component (if applicable):

NetworkManager-0.7.0-0.9.1.svn3417.fc9.x86_64

Comment 1 Bill Nottingham 2008-03-12 03:36:42 UTC

Similarly, on wireless it will go into bozo mode where it drops the default
route and DNS connection as well - presumably it has something to do with
attempting to bring up the (disconnected) wired interface.

Comment 2 Dan Williams 2008-03-12 13:56:37 UTC

There were a few issues with DHCP rebinds blowing away the default route that I
fixed yesterday.  That's likely what you're running into.

Comment 3 Bill Nottingham 2008-03-12 17:42:19 UTC


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