Hello everyone,

I'm attempting to install an Intel Wireless Pro 2200BG mini wireless card into a laptop running Fedora Core 2. I'm using the Windows driver and NDIS wrapper. The NDISWrapper program reports that the wireless device is present, and as far as I can tell modprobe.conf is loading it correctly. Running iwconfig generates the following message for eth1.

eth1 IEEE 802.11b ESSID:"" Nickname:"localhost.localdomain"
Mode:Managed Access Point: FF:FF:FF:FF:FF:FF Bit Rate=54Mb/s
RTS thr=1600 B Fragment thr=2304 B
Encryption key:000E-3509-8073 Security modepen
Power Managementff
Link Quality:0/100 Signal level:24/154 Noise level:0/154
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

When I try to bring the Interface up with the ifup eth1 command, I get the following irritating message.

Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Invalid argument.

Determining IP information for eth1... failed; no link present. Check cable?

I'm not sure where to proceed from here. It seems like the hardware is configured fine, and I do have an access point up and running with DHCP, so I should at least get an IP address. I'm also not sure why the link quality is at 0.

Any help on solving this problem would be greatly appreciated. Thanks,

~Seth~

What sort of encryption, if any, is your wireless AP using? Its possible that you have the WEP configured improperly. Or, if you are using WPA, you need to download the wpa supplicant.

The reason that I'm leaning towards encryption is because the iwconfig output shows a signal strength of 24/154, so your card is "seeing" the wireless AP, apparently.

I'm fairly sure we're not running encryption. If we are I'm not sure how to set up WEP properly. Do the keys match on the AP and the wireless card?

Again though, I'm pretty sure we're not running encryption. I tried first without a keys-eth1 file in my sysconfig, and had similar results. Should I also try setting a static IP?

Thanks for the input.

Well, I'll admit that I'm stumped. There are a number of possiblities/things that I would try, but I don't know how productive they will be.

1) make sure you have the SSID and IP address of your router configured correctly. I am not very familiar with ndiswrapper, but there must be a way to configure it to search for your wireless AP. I mention this because the output you posted from iwconfig lists "localhost.localdomain" as (what I believe is) your router address, and the MAC address as FF:FF:FF:FF:FF:FF. These values are not typical, and could indicate something is misconfigured, or perhaps never configured in the first place.

2) You may or may not be trying to run encryption, but the output of iwconfig shows an encryption key. I'm not exactly sure if it is trying to use it or not, but in my experience Linux warns you whenever you try to connect without encryption. Just double check that all encryption is off, both in your wireless configuration and in your routers configuration

My gut instinct on this problem is a misconfiguration of the wireless card. Not necessarily beacuse you messed up, don't get me wrong . But the fact that the wireless card seems to be getting a signal (signal level is 24/154) seems to point that way.

Also, try running dhclient eth1 to see if you can get an IP address before using ifup eth1.

I was able to get fc2 up with LEAP + cMIC, but found that FC2 does not configure and build aes by default. the only real pointer was an almost innoculous message about aes not found in /var/log/messages.

I would never associate to the AP b/c leap authenticaton would fail. when up and working I get this:

more /proc/driver/aironet/eth1/Status
Status: CFG ACT SYN LNK PRIV KEY WEP

where aironet is my driver for aironet mpi 350 card. there's no real troubleshooting this, you have to just know what is enabled on your AP.

Im running Core 3 with a WPC11 version 3 card. Its a IBM laptop R31 running dual boot XP pro and core 3 xp pro wireless work fine! .... when you put the encryption key in are you putting the 0x in front of the encryption key??? when you hover over the key area it tells you to put that in so its inputted, as a hexadecimal number!! after that it got rid of the SET ENCODE error for me but i still can't view web pages.. when i click activate it says something which i can't see and acts like it connects just like through regular ethernet. i reboot and still won't connect. i've fooled with the wireless part for 3 days now and i can't get it to work. anyone else have suggestions. Also leave transmission rate set on auto that gets rid of a couple other errors i was getting!

hope this helps SOMEONE, i sure could use some