Bug 879032

Summary:	F17 is trying to connect to non-existed networks during boot
Product:	[Fedora] Fedora	Reporter:	Milan Kerslager <milan.kerslager>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	iarlyy, jonathan, lnykryn, notting, plautrba, rvokal, vpavlin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-28 13:51:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Milan Kerslager 2012-11-21 21:21:15 UTC

I have some WiFi networks predefined. Most of them are global, because I'm sharing the notebook with some people.

When the system boots, I see a lot of delays (2 sec or so for every defined network) when "network" script is trying to connect to WiFi networks that are not present in the place I'm booting. I have to blacklist WiFi module to prevent these delays.

I don't understand why this happens during boot, when there is NetworkManager in GUI and I don't want to connect before GUI is on. I don't understand why it is trying to connect to the networks that aren't there, even the ethernet port which is not connected at all... This is crazy :-) and annoying, frustrating when I see twenty networks include some auto-detected and auto-configured but never used.

Comment 1 Lukáš Nykrýn 2013-03-28 13:51:13 UTC

Solution to this is to have network.service disabled and from f19 initscripts will skip wireless networks if they are handled with NM and NM is on.