wpa_supplicant service fails to autostart on Fedora 8
Dan Williams
dcbw
Sat Jan 19 09:59:45 PST 2008
On Sat, 2008-01-19 at 02:04 -0800, Reik Red wrote:
> Hmm, I found something that looks fishy. In my system,
>
> S10network
>
> is started before
>
> S28wpa_supplicant
>
> Since S10network starts both eth0 and wlan0 (in turn),
> it makes sense that the subtask dhclient wlan0 fails,
> because wlan0 cannot really be up before wpa_supplicant is.
Right; the latest update only ensures that wpa_supplicant is started
after messagebus.
The problem with making network depend on wpa_supplicant is that this
breaks the network-mounted-usr case, because wpa_supplicant is installed
in /usr. Nothing has been done to work through this yet, there are two
options:
1) Make network-mounted-usr people fend for themselves and don't keep
trying to preserve that use-case from 1992
2) Add the bits to the network service to "suggest" that it start the
supplicant if it's available
You can't make the network service have a hard dependency on the
supplicant because that would result in an error if the user didn't have
the wpa_supplicant package installed, nor can you really make the
sysvinit package depend on wpa_supplicant either, forcing everyone to
install the supplicant even if they don't need it.
> Am I blowing smoke here? I'll be the first to admit that
> I'm no expert on init, but this looks strange.
>
> Hope someone can give a hint, I'm a bit lost here. Should wpa_supplicant
> be started even before S10?
Not for everyone, and not as a hard dependency of the network service.
I forget the actual keyword, but try looking around for the advisory
requires option for new LSB initscripts.
Dan
> Side question: What is the generic method for making init verbose and saving
> the output to a log file? Linux systems do not seem to do this by default.
>
> Reik
>
> Reik Red wrote:
> > I have a similar problem as Robert had, but in my case updating
> > to the latest does not help.
> >
> > The main symptom is that ifup wlan0 (or equivalent) hangs during boot,
> > because it is not able to get an IP address. After timing out and finishing
> > the boot, I can run dhclient wlan0 and get the IP address. In fact,
> > wlan0 itself is up already, just without an IP address.
> >
> > I can't see anything in /var/log/wpa_supplicant.log, even with
> > OTHER_ARGS=-d. However, I can see some of the -d output on the
> > boot screen soon after the timeout.
> >
> > By the way, what happened with the old -f -u options, is that relevant
> > to my problem?
> >
> > For completeness: I am bringup up eth0 as well during this process, but
> > if I remove the cable it does not help on the wlan0 problem, and result
> > is the same.
> >
> > Reik
> >
> > Dan Williams wrote:
> >> On Wed, 2008-01-02 at 10:43 +0100, Robert Allerstorfer wrote:
> >>> On Mon, 31 Dec 2007, 11:10 GMT-05 Dan Williams wrote:
> >>>
> >>>> On Mon, 2007-12-31 at 13:47 +0100, Robert Allerstorfer wrote:
> >>>>> I am trying to activate the wlan0 device automatically at booting
> >>>>> Fedora 8. It should associate to my WPA2-personal protected Access
> >>>>> Point. Since NetworkManager 0.7 svn3109 does NOT work for this, I
> >>>>> don't start that service. Instead, I have set the wpa_supplicant
> >>>>> service to autostart. This will run
> >>>>> 'wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -iwlan0
> >>>>> -Dwext -B -u -f -d'
> >>>>> which fails while booting:
> >>>>> [root at localhost ~]# cat /var/log/wpa_supplicant.log
> >>>>> Could not acquire the system bus.
> >>>> You're probably interested in Fedora bug #244029. That's the best
> >>>> place
> >>>> to track your issue since it's a Fedora specific issue.
> >>>> Dan
> >>> OK, with the official current wpa_supplicant package for Fedora 8
> >>> (0.5.7-16.fc8), wpa_supplicant cannot be autostarted as a service.
> >>> Updating wpa_supplicant to version 0.5.7-20.fc8 currently available
> >>> from Fedora's updates-testing repo solves this problem:
> >>
> >> Now that it's gone through some testing, it's likely time to push it to
> >> plain updates.
> >>
> >> dan
> >>
> >>> [root at localhost ~]# yum --enablerepo=updates-testing update
> >>> wpa_supplicant
> >>> [root at localhost ~]# rpm -q --changelog wpa_supplicant | more
> >>> * Mon Dec 24 2007 Dan Williams <dcbw at redhat.com> - 0.5.7-20
> >>> - Fix LSB initscript header to ensure 'messagebus' is started first
> >>> (rh #244029)
> >>>
> >>> * Thu Dec 06 2007 Dan Williams <dcbw at redhat.com> - 0.5.7-19
> >>> - Fix two leaks when signalling state and scan results (rh #408141)
> >>>
> >>> * Mon Dec 03 2007 Dan Williams <dcbw at redhat.com> - 0.5.7-18
> >>> - Add logrotate config file (rh #404181)
> >>> - Add new LSB initscript header to initscript with correct deps (rh
> >>> #244029)
> >>> - Move other runtime arguments to /etc/sysconfig/wpa_supplicant
> >>>
> >>> * Thu Nov 15 2007 Dan Williams <dcbw at redhat.com> - 0.5.7-17
> >>> - Start after messagebus service (rh #385191)
> >>> - Fix initscript 'condrestart' command (rh #217281)
> >>>
> >>> After doing
> >>> [root at localhost ~]# chkconfig wpa_supplicant off
> >>> [root at localhost ~]# chkconfig wpa_supplicant on
> >>>
> >>> the startup priority will change from 12 to 28, after the messagebus
> >>> service:
> >>> [root at localhost ~]# ls -l /etc/rc.d/rc*.d/S*wpa_supplicant
> >>> lrwxrwxrwx 1 root root 24 2007-12-31 14:16
> >>> /etc/rc.d/rc2.d/S28wpa_supplicant -> ../init.d/wpa_supplicant
> >>> lrwxrwxrwx 1 root root 24 2007-12-31 14:16
> >>> /etc/rc.d/rc3.d/S28wpa_supplicant -> ../init.d/wpa_supplicant
> >>> lrwxrwxrwx 1 root root 24 2007-12-31 14:16
> >>> /etc/rc.d/rc4.d/S28wpa_supplicant -> ../init.d/wpa_supplicant
> >>> lrwxrwxrwx 1 root root 24 2007-12-31 14:16
> >>> /etc/rc.d/rc5.d/S28wpa_supplicant -> ../init.d/wpa_supplicant
> >>>
> >>> With autostarting the wpa_supplicant service and NOT using
> >>> NetworkManager, establishing a wireless connection to a WPA2 protected
> >>> access point with a Broadcom card works for the first time for me on
> >>> Fedora :-)
> >>>
> >>> rob.
> >>>
> >>>
> >>> _______________________________________________
> >>> HostAP mailing list
> >>> HostAP at lists.shmoo.com
> >>> http://lists.shmoo.com/mailman/listinfo/hostap
> >>
> >> _______________________________________________
> >> HostAP mailing list
> >> HostAP at lists.shmoo.com
> >> http://lists.shmoo.com/mailman/listinfo/hostap
> >
>
> _______________________________________________
> HostAP mailing list
> HostAP at lists.shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
More information about the Hostap
mailing list