Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 179043 - wpa_supplicant-0.5.7 fails to connect during startup with ipw2200
Summary: wpa_supplicant-0.5.7 fails to connect during startup with ipw2200
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Roy Marples (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-18 20:51 UTC by François Valenduc
Modified: 2007-06-29 09:55 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Output of emerge --info (emerge-info,2.86 KB, text/plain)
2007-05-18 20:52 UTC, François Valenduc
Details
network configuration file (net,317 bytes, text/plain)
2007-05-18 20:53 UTC, François Valenduc
Details
wpasupplicant configuration file (wpa_supplicant.conf,226 bytes, text/plain)
2007-05-18 20:54 UTC, François Valenduc
Details

Note You need to log in before you can comment on or make changes to this bug.
Description François Valenduc 2007-05-18 20:51:57 UTC
Since a few days, it's almost impossible to use ipw2200 with WPA
encryption in gentoo. I use AES (CCMP) encryption and each time I get
the following message when net.eth1 is started:

starting wpa_supplicant on eth1
starting wpa_cli on eth1
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or
directory 

However, If I run the command wpa_cli -i eth1 reassociate, the
association to the network occurs almost instantly. I just then have to
run dhclient manually to get an IP adress. The problem with such a
method is that the net.eth1 is not considered as started, so dependent
services like samba can't be started.  For your information, I use
wpa_supplicant 0.5.7, ieee80211 version 1.2.16 and ipw2200 version 1.2.1.

Does anybody knows any solution to this very annoying problem ?
Thanks in advance for your help,

Reproducible: Always

Steps to Reproduce:
1. Start the computer
2. Wait until net.eth1 get started
3.

Actual Results:  
The wireless connection doesn't work although the access point is available.
Comment 1 François Valenduc 2007-05-18 20:52:26 UTC
Created attachment 119638 [details]
Output of emerge --info
Comment 2 François Valenduc 2007-05-18 20:53:14 UTC
Created attachment 119639 [details]
network configuration file
Comment 3 François Valenduc 2007-05-18 20:54:30 UTC
Created attachment 119641 [details]
wpasupplicant configuration file
Comment 4 Roy Marples (RETIRED) gentoo-dev 2007-05-19 16:23:19 UTC
Have you tried using in kernel ieee80211 and ipw2200?
Comment 5 François Valenduc 2007-05-19 16:33:34 UTC
I use indeed the ieee80211 and ipw2200 provided in the standard kernel. I don't know why but since today, the problem occurs less frequently (and I didn't change anything in my configuration). I would however like to know what is the missing file or directory the error message is talking about.
Comment 6 Roy Marples (RETIRED) gentoo-dev 2007-05-19 16:40:42 UTC
Oh that's easy. wpa_supplicant creates a socket file which tells wpa_cli how to connect to it. It's this file that is missing.

As to why it's vanishing I have no idea. Try appending -dd to wpa_supplicant_eth1= in /etc/conf.d/net and when it fails attach the relevant parts of your log.
Comment 7 François Valenduc 2007-05-19 17:01:36 UTC
Thanks for your help. I guess the file which you refer to is either /var/run/wpa_supplicant/eth1= or /var/run/wpa_supplicant-eth1.pid. I have added -dd as parameter in the /etc/conf.d/net file but I can't find any trace of wpa_supplicant output in the system logs. Where are these supposed to be saved ?
Comment 8 Roy Marples (RETIRED) gentoo-dev 2007-05-19 17:29:24 UTC
It's /var/run/wpa_supplicant/eth1

It maybe easier to stop net.eth1 and then start wpa_supplicant manually like so

wpa_supplicant -dd -W -B -i eth1 -P "/var/run/wpa_supplicant-eth1.pid"

And then connecting with wpa_cli like so.

/bin/wpa_cli -a /etc/wpa_supplicant/wpa_cli.sh -i eth1 -P var/run/wpa_cli-eth1.pid" -B
Comment 9 François Valenduc 2007-05-19 17:47:55 UTC
You mean that I should disable net.eth1 at startup and connect manually like you have explained ? I am afraid I won't learn anything from that. I have already tried to run wpa_supplicant and wpa_cli manually when it fails during startup and as I have already said, it always succeed. It's during startup that there is a problem.
Comment 10 François Valenduc 2007-05-19 22:02:32 UTC
I have again encountered the problem and I have found something which looks very strange. When wpa_cli complains about the missing file or directory, the file "/var/run/wpa_supplicant/eth1" exists. So it's not missing but it seems wpa_cli can't use it.
Comment 11 Roy Marples (RETIRED) gentoo-dev 2007-05-24 10:52:50 UTC
Does it work if you remove the line "ctrl_interface=/var/run/wpa_supplicant" from your config?
Comment 12 François Valenduc 2007-05-24 17:49:44 UTC
It has worked once but I wouldn't say yet that it will work for sure. I don't know why but without any change, this problem occurs almost no more. Let's hope it will continue to work correctly.

Comment 13 Roy Marples (RETIRED) gentoo-dev 2007-06-29 09:55:00 UTC
I think this is fixed in wpa_supplicant-0.5.8 or 0.6.0