| Summary: | net.wlan0 init.d script tries to start wpa_cli but fails (wpa_ctrl_open) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | TBeck <toby.beck> |
| Component: | Current packages | Assignee: | Roy Marples (RETIRED) <uberlord> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | seventhguardian |
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | my wpa_supplicant configuration file | ||
|
Description
TBeck
2006-10-29 07:30:50 UTC
Please attach /etc/wpa_supplicant.conf (if exists) AND /etc/wpa_supplicant/wpa_supplicant.conf Just blank out the passwords/keys, please leave everything else intact. Created attachment 100764 [details]
my wpa_supplicant configuration file
Do you see this issue with wpa_supplicant-0.5.4? Yes, I have the same issue with 0.5.4. Here some more information: after booting, when i start wpa_cli manually without having changed anything yet, wpa_cli starts and reports this: <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys <2>Trying to associate with 00:30:f1:db:83:60 (SSID='WLAN' freq=0 MHz) <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys <2>Trying to associate with 00:15:e9:14:30:aa (SSID='Brunnenstr10' freq=0 MHz) after booting, if i set wlan0 up manually with ip l set wlan 0 up and then start wpa_cli, wpa_supplicant associates w/o problems Do you see this issue with wpa_supplicant-0.5.7? I'm having the same issue here with baselayout-2.0.0_alpha3, and found the source of the problem. Apparently wpa_cli doesn't respect the -P switch (pid file selection), and start-stop-daemon can't work with it: $ /etc/init.d/net.eth1 start (...) * Starting wpa_cli on eth1 ... + start-stop-daemon --start --exec /bin/wpa_cli --pidfile /var/run/wpa_cli-eth1.pid -- -a /etc/wpa_supplicant/wpa_cli.sh -p 'DIR=/var/run/wpa_supplicant GROUP=wheel' -i eth1 -P /var/run/wpa_cli-eth1.pid -B Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory * start-stop-daemon: failed to started `/bin/wpa_cli' (...) Manually starting wpa_cli confirms this issue: $ wpa_cli -P $PWD/test.pid Result -> No PID file gets created. I don't know why this is happening, I've had it working with this baselayout just some days ago... So I'm not sure what changed, or if it is a wpa_cli/baselayout bug.. Just to check, was this the way wpa_cli was used in the init scripts before baselayout-2.0.0_alpha3? Oh sorry... No, this is not the true issue. It's true that wpa_cli doesn't respect the -P switch, but the true issue is another one: The -p argument is 'DIR=/var/run/wpa_supplicant GROUP=wheel', which I believe isn't yet supported by wpa_cli-0.5.7. The error "Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory" should be fixed in wpa_supplicant-0.5.8 or at least 0.6.0 Re-open if you dis-agree. |
