Summary: | wpa_supplicant - connection refused | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Filbert <filbert> |
Component: | New packages | Assignee: | Roy Marples (RETIRED) <uberlord> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | base-system |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Filbert
2007-04-24 17:11:22 UTC
sorry, i was wrong about the mistakes for the wpa_cli. i thought that the start-stop-daemon syntax was mixed up. what i've written about wpa_supplicant is still true. however, i'm still analyzing the error "failed to connect to wpa_supplicant - wpa_ctrl_open: connection refused" which is caused by wpa_cli. i'll report soon. -W is a valid option for wpa_supplicant, I checked the sources. -W means "wait for wpa_cli to connect to us before we try and associate" It's not documented though. The script itself is correct. From the sounds of it. wpa_supplicant didn't launch correctly. well, i think i got it. i don't know what the problem exactly was/is but here's what i've done: i edited the file /etc/conf.d/net. there i've added the argument -w (lower case) for wpa_supplicant when i installed gentoo a few years ago. i deleted it and now it works. let's see for how long... i made also some interesting observations. when i began to to search for the problem the first thing i did was adding the -dd option to /etc/conf.d/net for wpa_supplicant. regardless no debug information appeared. i didn't wonder because i thought this was just a side effect of the daemonizing. since i got rid of the -w option i get a lot of debug output and wpa_supplicant daemonizes as well. thanks for support Closing as repoter solved issue. |