|
Bugzilla – Full Text Bug Listing |
| Summary: | no WPA connection possible | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Dominique Leuenberger <dimstar> |
| Component: | Network | Assignee: | Tambet Ingo <tambet> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P3 - Medium | CC: | yast2-maintainers |
| Version: | Alpha 0plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Please attach your /var/log/messages, /var/log/NetworkManager, and the yast logs. http://en.opensuse.org/Bugs/YaST Sorry.. no log files so far.. but I found how to pursuade NM to connect to the AP. I have to force it to use TKIP instead of Automatic, then it connects. So the automatic selector is not working (even though on the Command Line I did never specify TKIP, so wpa_supplicant is able to do it right! The essid is hidden, this means it can't be sniffed properly I believe, so you can't use automatic. JP, the reply is not perfectly satisfying, as on CLI (using wpa_supplicant, iwconfig and hdclient) I never specified to use TKIP. I mean for myself this does not cause a problem, I guess I have enough knowledge to connect (apparantly, as I succeeded), but Joe Average might be a bit on his limit. So just having essit hidden (which is not worst practice) should still allow to login on automatic (as said: wpa_supplicant seems to do the trick when started manually. Seems NM is missing some parameters to send via the socket?) Tambet, JP, what's the status on this bug? NM uses wpa_supplicant as well, so I'm not sure why exactly it can not determine the wpa type. Based on how easy it is to work around this problem (that widget is there for a reason), there's nothing critical about it. You can see what commands NM sends to wpa_supplicant from /var/log/NetworkManager log file, but it does send all from your manual config file. Fixed in 11.0 and later. |
NIC: ipw2200 driver WPA encrypted WLAN, PSK ESSID: hidden I can not connect to the network when using Network Manager. I can connect perfectly to it when using the following commands: wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant.conf -B iwconfig eth0 essid <ssid> dhclient eth0 /etc/wpa_supplicant contains only the lines: network={ ssid=<ssid> psk=<PSK in encrypted form> } I consider this feature a higly required one. It's a show stopper if it can not be used in such an environment. Also a configuration via Yast (traditional, without NM) does not work for a connection.