WEP with ndiswrapper not working in FC2

vrooje · 05-01-2006, 01:31 AM

I'm currently running FC2 2.6.10-1.771. I have ndiswrapper loaded to make my broadcom wireless card talk nice with Linux.

The bottom line: I can bring up wlan0 without problems, as long as the connection is unencrypted.

Once I switch to WEP encryption (128-bit), obtaining an IP address always fails. It works fine in Windows, so I know the key is correct. When I am in FC2 and I do an iwlist wlan0 scan, I can find my network as well as the other networks around me.

I was getting some error messages about failed commands, but I believe I have now tracked them all down and fixed them, except:

Code:

Driver for device wlan0 recommends version 18 of Wireless Extension, but has been compiled with version 17, therefore some driver features may not be available...

I have wireless_tools.27 installed, and I believe I have the latest kernel for my distribution (or I have been looking on outdated websites tonight). I am also pretty sure that I have the correct, and most updated, driver for my Broadcom wireless card.

Am I correct in thinking that the only way I can get version 18 of Wireless Extension is to upgrade my distribution? That FC2 just doesn't support 128-bit WEP?

I would love to use WPA, but some of the other devices in my home that use this wireless connection can't use WPA (namely TiVo). I might be able to switch to 64-bit encryption, but I would prefer not to.

Have others found solutions for this? I searched the forums, and it seems like other posts ike this didn't get answers. I am hoping that was just an oversight.

Help?

vrooje · 05-01-2006, 01:57 PM

Update: I am now using 64-bit WEP, and still can't connect in FC2 (am typing from Windows).

vrooje · 05-07-2006, 08:00 PM

Um... good to know that I have a question that stumped the whole board.

dcdbutler · 05-08-2006, 11:31 PM

Try this:

# iwconfig wlan0 key XXXXXXXXXX

# iwconfig wlan0 key open

# iwconfig wlan0 essid [ssid]

then check iwconfig to see if it's taken ok. If it's ok, try to bring it up with dhcp. Sometimes nodes are set to use open encryption (unencrypted packets allowed) which is what the 'key open' should do - This is the case with a broadcom card I use.

Since it works unencrypted, this is the only reason I can think that it wouldn't work with encryption with what you've been trying so far (unless you're using an inappropriate driver). The other key mode is 'restricted' which means that unencrypted packets are discarded.

Good luck

vrooje · 05-10-2006, 12:38 AM

Okay, that worked... what the heck?!

My previous commands:

Code:

iwconfig wlan0 essid XXXXX
iwconfig wlan0 key open XXXXX
ifconfig wlan0 up
ifup wlan0

which is what I use (except for the key) for another, unsecured network that I connect to regularly.

This code:

Code:

iwconfig wlan0 essid XXXXX
iwconfig wlan0 key open XXXXX
dhclient

which I am positive I tried a week or so ago, with no effect... very odd.

Thank you!