[lfs-support] Using wpa_supplicant [Was: ifup--a really uninformed question]

Dan McGhee beesnees at grm.net
Sat Nov 2 11:11:17 PDT 2013


I'm still on the trail of getting my wireless up in chroot. I have all 
the ifconfig files I need, and, except for the static stuff in Ch. 7 of 
the book, they are "cut and paste" from BLFS. This time in chroot, after 
I had turned off my card in the host system I used 
</etc/rc.d/init.d/network start> for my command. The third set of screen 
output was:
> Starting wpa_supplicant on the wlan0 
> interface.../lib/lsb/init-functions: line 664: /run/var/bootlog: No 
> such file or directory
> Could not set interface wlan0 flags (UP): Operation not possible due 
> to RF-kill
> * [ OK ]
(Received complaints about /run/var/bootlog all through the process. 
They were right, it doesn't exist yet.)

The last line of screen output was:
> /lib/lsb/init-functions: line 586: /run/var/bootlog: No such file or 
> directory
> RTNETLINK answers: Operation not possible due to RF-kill
I don't know how, when or where the "RF-kill generates, but based on the 
fact that it's a kernel message, I'm wondering if it didn't originate 
somewhere in the wpa_supplicant process because dmesg gave me the 
following when I checked it after I couldn't ping anything.
> [ 3547.476338] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 3554.073619] wlan0: authenticate with c4:3d:c7:70:07:e7
> [ 3554.088957] wlan0: send auth to c4:3d:c7:70:07:e7 (try 1/3)
> [ 3554.090954] wlan0: authenticated
> [ 3554.092919] wlan0: associate with c4:3d:c7:70:07:e7 (try 1/3)
> [ 3554.096066] wlan0: RX AssocResp from c4:3d:c7:70:07:e7 (capab=0x411 
> status=0 aid=2)
> [ 3554.096156] wlan0: associated
> [ 3554.096256] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [ 4217.269801] wlan0: deauthenticating from c4:3d:c7:70:07:e7 by local 
> choice (reason=3)

Compare that output with this output when I "awoke" my laptop from sleep 
a little later.

> [ 4246.722109] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 4248.988116] wlan0: authenticate with c4:3d:c7:70:07:e7
> [ 4249.003441] wlan0: send auth to c4:3d:c7:70:07:e7 (try 1/3)
> [ 4249.004987] wlan0: authenticated
> [ 4249.007303] wlan0: associate with c4:3d:c7:70:07:e7 (try 1/3)
> [ 4249.010487] wlan0: RX AssocResp from c4:3d:c7:70:07:e7 (capab=0x411 
> status=0 aid=2)
> [ 4249.010571] wlan0: associated
(I accidently cut off the last line which stated that wlan0 link was ready.)

They are both identical except for that last line in the first set. If I 
am correct, the "authenticate/deauthenticate" stuff comes from 
wpa_supplicant. I'm not sure what is happening.

I checked after the failed attempt and all the right drivers were 
loaded. I think wpa_supplicant has everything it needs based on the 
config file and the arguments in its service script.

The only other thing I can think of right now is d-bus. Because I 
ultimately want to run wpa_supplicant with "Network Manager," I 
installed d-bus and built and configured wpa_supplicant with d-bus 
support. My question is, then, do I need to start the d-bus daemon as a 
result? Is wpa_supplicant not "talking" to whom it needs to speak. I've 
not used d-bus or wpa_supplicant on such an intimate level. I Ubuntu it 
just happens.

The last current question I have is, in the service script for 
wpa_supplicant, it is called with the -q option for little debugging 
operation. If I add -d, for more debug info, in the ifconfig.wifi0 file 
under "WPA_ARGS=, will that over ride the behavior of the service script?

In the meantime, I'm trying to learn how to use wpa_cli so that I might 
get a better handle on what's happening. Obviously, I'm focusing on 
wpa_supplicant right now. Does anyone see another or different 
alternative to where the problem might be?

Thanks,
Dan







More information about the lfs-support mailing list