Bug 113635 - ndiswrapper uses wrong keys
Summary: ndiswrapper uses wrong keys
Status: VERIFIED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 3
Hardware: x86 SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: Joachim Gleissner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-28 13:27 UTC by Howard Coles Jr.
Modified: 2007-06-05 10:04 UTC (History)
1 user (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Howard Coles Jr. 2005-08-28 13:27:40 UTC
When I use YaST to setup ndiswrapper for wlan0 it asks for all the same
information it did in 9.3.   However, when I try to "ifup" the wlan0 interface I
receive errors because it uses this command line:

iwconfig wlan0 key open mykeymaskedhere [1] key 128 [2] key 128 [3] key 128 [4]

Here is the full output of trying to run ifup wlan0 command:

     wlan0   device: Broadcom Corporation BCM4309 802.11a/b/g (rev 03)
command 'iwconfig wlan0 key open mykeymaskedhere [1] key 128 [2] key 128 [3] key
128 [4]' returned
  Error for wireless request "Set Encode" (8B2A) :
setting encryption key FAILED, aborting interface setup.

When I had the wpa_supplicant package installed it put 128 after each "wep_key"
field in the /var/run/wpa conf file.   I thought I could uninstall WPA (which
isn't good, because I need it at work), but now its using that same syntax on
its own.  I don't know where its pulling this from, however I can manually run
"dhcpcd wlan0" and get a dhcp address.

It looks like the extra "key 128" fields are the problem because I can manually
get the card up by issuing the proper iwconfig commands:
iwconfig wlan0 ESSID MYSSID
iwconfig wlan0 KEY MYKEY
dhcpcd wlan0

I didn't know if this was a ndiswrapper, wpa_supplicant, or YAST problem so I
put it under Network.

I'm running a Dell Latitude D600.
Comment 1 Joachim Gleissner 2005-08-29 10:04:44 UTC
Please check whether the ifup-wireless attachted in bug 113597 fixes this. 
Comment 2 Howard Coles Jr. 2005-09-01 02:22:55 UTC
(In reply to comment #1)
> Please check whether the ifup-wireless attachted in bug 113597 fixes this. 

No.  with wpa_supplicant installed the fields are still wrong.  I need
wpa_supplicant for work, but not home so I have to have it installed, but I
don't need it working from home.  So how do I get YaST to NOT use wpa at home,
and use it at work?
Comment 3 Howard Coles Jr. 2005-09-01 02:26:12 UTC
(In reply to comment #1)
> Please check whether the ifup-wireless attachted in bug 113597 fixes this. 

Oops, my bad.  If I manually set "PREFER_WPA_SUPPLICANT" to NO then it works,
however my question now is, where would a normal user set that option? Is there
a way that could be included in the sysconfig scripts?
Comment 4 Joachim Gleissner 2005-09-01 09:41:44 UTC
I'll change the default to 'NO' for ndiswrapper. 
Comment 5 Joachim Gleissner 2005-09-02 12:54:44 UTC
Should work with RC1.