https://bugzilla.novell.com/show_bug.cgi?id=235251#c14 --- Comment #14 from Dieter Jurzitza <dieter.jurzitza@t-online.de> 2007-07-25 09:22:11 MST --- You are wrong here. The current suse init concept does not provide an interface to iwpriv. I have been using both modules since more than a year with WPAPSK only. Suse only supports wpa-supplicant for (IMHO) ununderstandable reasons. Apply the patch below (as readily said) to ifconfig-wireless and you will see both drivers work flawlessly with WEP, WPA-PSK (and no encryption, for sure). Both ralink cards are quite widespread and can be easy to use. So, the information that is presented by hwconfig is wrong in this case. And it would be nice if yast would be open in this regard - the "bug" helps me since quite a while because from this it is possible to configure the card easily after applying the following patch (against 10.2): --- scripts/ifup-wireless.original 2006-10-27 15:32:54.000000000 +0200 +++ scripts/ifup-wireless 2007-01-21 23:21:03.000000000 +0100 @@ -630,9 +630,20 @@ else SUPPARGS="-P/var/run/wpa_supplicant/${INTERFACE}.pid -B" fi - mkdir -p /var/run/wpa_supplicant - message "`printf " %-9s starting wpa_supplicant" $INTERFACE`" - eval wpa_supplicant -i$INTERFACE -c$WPA_SUPP_CONF -D$WPA_DRIVER $SUPPARGS + if [ "$WPA_DRIVER" = "iwpriv" ]; then + i=0 + while [ "$i" != "2" ]; do + run_iw_tool priv set AuthMode=WPAPSK + run_iw_tool priv set EncrypType=TKIP + run_iw_tool priv set WPAPSK="${WIRELESS_WPA_PSK}" + run_iw_tool config essid ${WIRELESS_ESSID} + i=`expr $i + 1` + done + else + mkdir -p /var/run/wpa_supplicant + message "`printf " %-9s starting wpa_supplicant" $INTERFACE`" + eval wpa_supplicant -i$INTERFACE -c$WPA_SUPP_CONF -D$WPA_DRIVER $SUPPARGS + fi } kill_wpa_supplicant() @@ -682,6 +693,12 @@ ndiswrapper|*.sys) WPA_DRIVER=wext ;; + rt2500) + WPA_DRIVER=iwpriv + ;; + rt61) + WPA_DRIVER=iwpriv + ;; *) WPA_DRIVER=unsupported PREFER_WPA_SUPPLICANT=no -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.