Some networking scenarios make the use of a static wireless network
configuration more desirable than one based on interactive Network
Manager configuration. For example, systems which always connect to
the same wireless AP in the same way have no need of a GUI for
interactively connecting, and in fact the presence of such a GUI would
Additionally, there are scenarios which require that the network
interface be available on boot prior to login, e.g., an unattended
machine that is controlled by a UPS. A networking configuration based
on Network manager is only available after user login.
Thus a wireless network configuration that is not based on Network
Manager is desirable in these scenarios.
One such configuration utilizes the "network" and "wpa_supplicant"
services along with a suitable wpa_supplicant.conf file and
/etc/sysconfig/network-scripts/ifcfg-wlan0 script. Services would then
be configured as follows
/sbin/chkconfig wpa_supplicant on
/sbin/chkconfig network on
/sbin/chkconfig NetworkManager off
Such a configuration will require the wpa_supplicant service
to be started prior to the network service at bootup.
HOWEVER, USING THE DEFAULT INIT SCRIPTS, THE WPA_SUPPLICANT
SERVICE DOESN'T START UNTIL AFTER THE NETWORK SERVICE.
Further, attempting to modify the service priority of the
/etc/rc.d/init.d/wpa_supplicant by changing the header
# chkconfig: - 23 88
# chkconfig: 345 9 88
doesn't work because of the $local_fs and messagebus dependencies
further down in the header (see the attached wpa_supplicant
script) - the wpa_supplicant service continues to start AFTER
the network service.
Even further yet, removing the $local_fs and messagebus dependencies
results in an unbootable system.
Thus the purpose of this ticket is to request that the init service
priorities for the network, wpa_supplicant, local_fs, messagebus, and
potentially other related services to be "rewired" so that a default
installation will start the wpa_supplicant service prior to the
Version-Release number of selected component (if applicable):
Name : wpa_supplicant
Arch : x86_64
Epoch : 1
Version : 0.6.8
Release : 4.fc11
Size : 618 k
Repo : installed
From repo : updates
Summary : WPA/WPA2/IEEE 802.1X Supplicant
URL : http://w1.fi/wpa_supplicant/
License : BSD
Description: wpa_supplicant is a WPA Supplicant for Linux, BSD and Windows with support
: for WPA and WPA2 (IEEE 802.11i / RSN). Supplicant is the IEEE 802.1X/WPA
: component that is used in the client stations. It implements key negotiation
: with a WPA Authenticator and it controls the roaming and IEEE 802.11
: authentication/association of the wlan driver.
Linux localhost.localdomain 184.108.40.206-217.2.16.fc11.x86_64 #1 SMP Mon Aug 24 17:17:40 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Created attachment 359176 [details]
wpa_supplicant init script
Created attachment 359177 [details]
working wpa_supplicant.conf file
Created attachment 359178 [details]
working /etc/sysconfig/network-scripts/ifcfg-wlan0 script
I got around this issue by turnning the network service off and then created my own service that does nothing but start and stop the network service. I established the service with a priority and run-level that ensure it starts after the wpa_supplicant service. See attached init serice script "airlink".
Created attachment 359284 [details]
new airlink service
See also https://bugzilla.redhat.com/show_bug.cgi?id=154348
Still happen on F12
BTW: a small patch will solve this issue:
--- ifup-wireless 2008-02-17 13:18:59.000000000 +0100
+++ ifup-wireless 2007-06-10 15:16:07.000000000 +0200
@@ -108,3 +100,7 @@
# use any essid
iwconfig $DEVICE essid any >/dev/null 2>&1
+if [ "$WPA" = "yes" -a ! -f /var/lock/subsys/wpa_supplicant ] ; then
+ service wpa_supplicant start
it need only to add a line
there's more comments about how initscripts should be integrated with wpa_supplicant in this thread. That basically means using the ifcfg-wlan0 to construct a wpa_supplicant config file so that we can preserve the normal, well-known mechanisms that Fedora/Red Hat admins know for network configuration in /etc/sysconfig/network-scripts, and the normal ifup/ifdown commands.
*** This bug has been marked as a duplicate of bug 154348 ***