Bug#407936: [pkg-wpa-devel] Bug#407936: wpasupplicant: does not configure interface correctly when it is available at boot time

[Kel Modderman]

On Monday 22 January 2007 23:52, Ivan Zaera Avellon wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
> Severity: normal
> Tags: patch
>
>
> When wpasupplicant is launched from /etc/wpa_supplicant/functions.sh it
> tries to use flag -W, which is supposed to make it wait until the wpa_cli
> attaches to the socket. The thing is, that the -W is not documented in
> wpasupplicant, and thus, it does not work (at least in my system). This
> causes wpa_cli to miss the CONNECTED event when the wireless network is
> available from the very first moment. As the event is missed, wpa_action is
> not called and the interface is not configured.

I reproduced this problem.

You did not supply a 'ctrl_interface' value in your configuration, therefore no
UNIX socket for communication with wpa_cli was created, and
wpa_supplicant did not take notice of the '-W' (wait for wpa_cli attachment
to ctrl_interface) option accordingly.

Please confirm my findings.

I updated the documentation for wpa-roam as below:

Index: debian/README.modes
===================================================================
--- debian/README.modes (revision 778)
+++ debian/README.modes (working copy)
@@ -262,6 +262,11 @@
 cp /usr/share/doc/wpasupplicant/examples/wpa_supplicant.conf.template \
        /etc/wpa_supplicant/wpa_supplicant.conf

+NOTE: it is critical that the used wpa_supplicant.conf defines the location of
+      the 'ctrl_interface' so that a communication socket is created for the
+      wpa_cli (wpa-roam daemon) to attach. The mentioned example conf file,
+      wpa_supplicant.conf.template, has this set to a sane default.
+
 It is required to edit this configuration file, and add the network blocks for
 all known networks. If you do not understand what this means, start reading the
 wpa_supplicant.conf(5) manpage now.


Thanks, Kel.