Can't Connect To WEP Wireless Network
 

Hi Folks,

I'm running a semi-fresh Slackware 10.2 installation, with whatever 2.4.x kernel comes by default. I have installed ndiswrapper and configured my drivers by adding both bcmwl5.sys and bcmwl5a.inf (I have a Dell TrueMobile 1400 card and for some reason, I think both have to be added for it to work).
The wireless card appears to be configured correctly, because it shows up to the system and all. But I cannot connect to my network. I seem to be able to configure the card correctly (though for some reason, there are two networks visible - XXXXXXXXX on ch. 9, and xxxxxxxxx on ch. 11; it's caps vs. no caps, and I'm just blanking out the essid). The only one that I can get it to see is xxxxxxxxx on channel 11. Here is the output of my iwconfig after configuring the card:

wlan0 IEEE 802.11g ESSID:"XXXXXXXXX"
Mode:Auto Frequency:2.462 GHz Access Point: BA:EC:6E:9F:58:1C
Bit Rate:54 Mb/s Tx-Power:46 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:XXXX-XXXX-XX Security mode:restricted
Power Management:off
Link Quality:100/100 Signal level:-57 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

After I configure it, I can have it up in ifconfig as follows:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:784 (784.0 b) TX bytes:784 (784.0 b)

wlan0 Link encap:Ethernet HWaddr 00:90:4B:1A:35:C5
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Memory:faff6000-faff8000

Now, if I try to run dhcpcd wlan0, it takes a while and does nothing; it seems that the network device disappears from ifconfig after I do that. Here is the result of ifconfig after the dhcpcd command:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:784 (784.0 b) TX bytes:784 (784.0 b)

Anyone have any ideas? While I won't be around this network for too much longer, at least for a while, I would like to know why this isn't working. If anyone has any suggestions, please let me know - thanks!

- Daniel

I have the same issue, are you using WEP? I can get an ip address if I disable the WEP, but as soon as I enable it again I nothing. My card is a Proxim using the orinoco.cs driver.

I'm using WEP; my family has a laptop running Windows connected wirelessly to the router, so I don't want to disable WEP to see what happens.

connecting to wireless router
 

I seem to have the same trouble: connecting to a router that has a WPA-PSK network with a TKIP encryption , i'm running FC4 and knoppix 4 also i cant seem to get etherreal or airsnort to run i have a broadcom card
any ideas,
thanks:confused:

Have you tried with 'open' authentication as a pose to restricted out of curiosity..?
Link quality 100/100 looks a little dodgy..
Is the router is definately set to be giving DHCP addresses?
Is it your network you are connecting to? Maybe they have MAC filtering . in which case you can authenticate with the correct key and unless you have a MAC that it recognises its not going to let you play.

If you do #dhcpcd <device> and it times out then yes, you will find the device is 'down' again in ifconfig.
It will timeout if 1) you are out of range from the router. 2) the key is incorrect (even with the above iwconfig result this can happen) 3) if they have MAC filtering setup or they are not infact using DHCP

is the restricted value automatically there or are you typing #iwconfig wlan0 key restricted s:asciipassphrase

it looks like me like you have the wrong key.. OR they have MAC filtering enabled OR they do not use DHCP maybe try password in 'hex' . sometimes some NICsjust wont play with other routers in Ascii mode.

If you connect to your router using ascii make sure you use:
#iwconfig <device> key s: password
If you are using the HEX key then use
#iwconfig <device> key password