Thread: [Ndiswrapper-general] WEP problems with Dell 1350 (Broadcom 4306)
Status: Beta
Brought to you by:
pgiri
From: Christian <chr...@ch...> - 2005-04-19 00:44:47
|
First, just wanted to say 'Thank You' in advance to any and all that can help. I'm having a problem getting WEP enabled on my Fedora 3 (2.6.11 kernel) installation. ndiswrapper 1.1 installed fine and if I don't have WEP enabled I connect to my Linksys WRT54GS with no problems. With WEP disabled, the following are my 'iwconfig' and 'iwlist' outputs: # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:"christian" Nickname:"laptop.christianl.org" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:A1:01:73 Bit Rate=54 Mb/s Tx-Power:25 dBm RTS thr=2347 B Fragment thr=2346 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-41 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 # iwlist wlan0 scanning wlan0 Scan completed : Cell 01 - Address: 00:0F:66:A1:01:73 ESSID:"christian" Protocol:IEEE 802.11g Mode:Managed Frequency:2.437 GHz (Channel 6) Quality:0/100 Signal level:-37 dBm Noise level:-256 dBm Encryption key:off Bit Rate:1 Mb/s Bit Rate:2 Mb/s Bit Rate:5.5 Mb/s Bit Rate:6 Mb/s Bit Rate:9 Mb/s Bit Rate:11 Mb/s Bit Rate:12 Mb/s Bit Rate:18 Mb/s Bit Rate:24 Mb/s Bit Rate:36 Mb/s Bit Rate:48 Mb/s Bit Rate:54 Mb/s Extra:bcn_int=100 Extra:atim=0 But, anytime I try to enable a WEP key (by using either '# iwconfig wlan0 key <key>' or '# iwconfig wlan0 key restricted <key>' or by using the network config UI) I can't get the ESSID to 'stick' in iwconfig. It keeps showing 'off/any' and I can't get a connection to the AP. I've looked through the ndiswrapper site at sourceforge and no one else using my driver/NIC/config seems to have WEP problems. Some users even reported getting WPA to work by using wpa_supplicant (my kernel crashes when I try it). Any ideas? |
From: Gerald H. <ghe...@ro...> - 2005-04-19 02:50:54
|
On Tue, 19 Apr 2005 00:33:07 +0000 (UTC), you wrote: >But, anytime I try to enable a WEP key (by using either '# iwconfig = wlan0 key ><key>' or '# iwconfig wlan0 key restricted <key>' or by using the = network config >UI) I can't get the ESSID to 'stick' in iwconfig. It keeps showing = 'off/any' Try using NetworkManager to config and activate your wireless connection. |
From: Christian <chr...@ch...> - 2005-04-19 03:19:16
|
Gerald Henriksen <ghenriks <at> rogers.com> writes: > > Try using NetworkManager to config and activate your wireless > connection. > Yep. Tried that too. Once I ran 'ndiswrapper -m', I was able to see wlan0 as an interface in the manager, but I can't set a key there either. I made sure to enter the full 26 characters as 0xYYYYYYYY..., but after doing that, iwconfig still reports off/any for my ESSSID. Christian |
From: Jonathan B. <be...@gm...> - 2005-04-20 02:21:33
|
On 4/18/05, Christian <chr...@ch...> wrote: > First, just wanted to say 'Thank You' in advance to any and all that can = help. >=20 > I'm having a problem getting WEP enabled on my Fedora 3 (2.6.11 kernel) > installation. ndiswrapper 1.1 installed fine and if I don't have WEP ena= bled I > connect to my Linksys WRT54GS with no problems. With WEP disabled, the > following are my 'iwconfig' and 'iwlist' outputs: >=20 > # iwconfig wlan0 > wlan0 IEEE 802.11g ESSID:"christian" Nickname:"laptop.christianl.or= g" > Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:A1:01= :73 > Bit Rate=3D54 Mb/s Tx-Power:25 dBm > RTS thr=3D2347 B Fragment thr=3D2346 B > Encryption key:off [snip] > But, anytime I try to enable a WEP key (by using either '# iwconfig wlan0= key > <key>' or '# iwconfig wlan0 key restricted <key>' or by using the network= config > UI) I can't get the ESSID to 'stick' in iwconfig. It keeps showing 'off/= any' > and I can't get a connection to the AP. I've looked through the ndiswrap= per > site at sourceforge and no one else using my driver/NIC/config seems to h= ave WEP > problems. Some users even reported getting WPA to work by using wpa_supp= licant > (my kernel crashes when I try it). >=20 > Any ideas? Hi Christian, How is the router setup? I could assume that you enable WEP between your two steps, but you don't explicitly state that. Can you connect with the AP from another computer (or from windows if you happen to dual boot) with WEP enabled? The ESSID will only show up once you card has associated with the AP, so your problem is with associating, not just setting the ESSID. You might want to try: # iwconfig wlan0 key open <key> instead of restricted and see if that allows you to connect. That seems to be the one configuration that you haven't tried. Note that the default is restricted (at least on my computer). Jonathan |
From: Christian <chr...@ch...> - 2005-04-20 03:57:39
|
Jonathan Berry <berryja <at> gmail.com> writes: > > Hi Christian, > > How is the router setup? I could assume that you enable WEP between > your two steps, but you don't explicitly state that. Can you connect > with the AP from another computer (or from windows if you happen to > dual boot) with WEP enabled? > The ESSID will only show up once you card has associated with the AP, > so your problem is with associating, not just setting the ESSID. You > might want to try: > # iwconfig wlan0 key open <key> > instead of restricted and see if that allows you to connect. That > seems to be the one configuration that you haven't tried. Note that > the default is restricted (at least on my computer). > I was actually just about to post that I was finally able to get ESSID to 'stick' by using 'iwconfig wlan0 key open <key>' and then 'iwconfig wlan0 essid <essid>' when I saw your post. And, yes...the router is setup for WEP. Here's what I get from iwconfig: # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:"christian" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:A1:01:73 Bit Rate:54 Mb/s Tx-Power:25 dBm RTS thr:2347 B Fragment thr:2346 B Encryption key:XXXX-XXXX-XX Security mode:open Power Management:off Link Quality:100/100 Signal level:-43 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 Now I have a new problem: I can't pull a DHCP lease from the AP's DHCP server and trying to manually configure the IP returns a 'destination unreachble' error for any outbound traffic ("ping 192.168.1.1"). In order to connect, I've turned off WEP and am just using the MAC address filter for it, but obviously I don't want to leave it this way. Following your suggestion, I tried this in XP SP2 and lo and behold, it couldn't pull an IP either using WEP 64-bit. (I previously had it working just fine with WPA PSK-TKIP). The plot thickens. I changed the router back to using WPA and now XP can pull an IP. So, looks like a config issue with the router, but after pouring over settings I can't find it. I'm going to attempt to install wpa_supplicant now and see how well that works. It didn't last time I tried it, but I was probably using a restricted key then. Thanks for the ideas Jonathan. Christian |
From: Christian <chr...@ch...> - 2005-04-20 06:31:40
|
Unfortunately, wpa_supplicant didn't work. Despite all my different config attempts, the daemon couldn't tell that the router supported WPA (but, it does work in XP SP2). Below is a snippet from the scan by wpa_supplicant: Starting AP scan (broadcast SSID) Scan timeout - try to get results Received 242 bytes of scan results (1 BSSes) Scan results: 1 Selecting BSS from priority group 1 0: 00:0f:66:a1:01:73 ssid='christian' wpa_ie_len=0 rsn_ie_len=0 skip - no WPA/RSN IE No suitable AP found. I tried reinstalling the router's firmware (Linksys WRT54GSv1.0) and even went so far as to grab the Satori 4.0 firmware from Sveasoft, but I still can't get a DHCP lease using dhclient when I've got WEP enabled. True, this seems to point to a router problem or maybe a wpa_supplicant/router issue, but there seem to be some intelligent people on this group. Any know what else I can try now (other than turning the AP into a paperweight)? I can post all my wpa_supplicant stuff if needed. Christian |