Re: Re: WEP encryption and ndiswrapper

[Angelo <angelo@freeshell.org>]

Jan Schledermann wrote:
> Angelo Bertolli wrote:
>
>   
> > Hey everyone, I was wondering if anyone was having a similar problem:  I
> > can connect to my wireless network using ndiswrapper, but only if I have
> > WEP encryption turned off.  Otherwise, it never connects.  I tried with
> > Ubuntu a while back, and it worked fine.  Anyone know why Debian would
> > have any problems.  I'm using ndiswrapper 1.28 (installed with
> > module-assistant).
> >
> > Angelo
> >     
> On my laptop (running sid) ndiswrapper works fine with WEP.
> What do your log files have to say?
> Do you see the network device with ifconfig and iwconfig? What does iwconfig
> show?
>   
wlan0     IEEE 802.11b  ESSID:off/any  Nickname:"ang"
         Mode:Auto  Frequency:2.437 GHz  Access Point: Not-Associated
         Bit Rate=11 Mb/s   Tx-Power:20 dBm   Sensitivity=0/3
         RTS thr=2432 B   Fragment thr=2432 B
         Power Management:off
         Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
         Tx excessive retries:0  Invalid misc:0   Missed beacon:0

> If you see the device, but it isn't connected, you could try to issue the
> setup information manually with iwconfig: something like: 
>   
Yes, everything seems to be setup on the hardware side.
> iwconfig wlan0 essid "My WAP" mode "managed" nickname "wzzp"
> key "XXXXXXXXXXXXXXXXXXXXXXXXXX" restricted rate auto
>
> replace:
> "wlan0" with the device used on your computer
> "My WAP" with the actual ESSID of your WAP
> "XXXXXXXXXXXXXXXXXXXXXXXXXX" with your actual key
>   
Does seem to want to set the ssid

wlan0     IEEE 802.11b  ESSID:off/any  Nickname:"ang"
         Mode:Auto  Frequency:2.437 GHz  Access Point: Not-Associated
         Bit Rate=11 Mb/s   Tx-Power:20 dBm   Sensitivity=0/3
         RTS thr=2432 B   Fragment thr=2432 B
         Power Management:off
         Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
         Tx excessive retries:0  Invalid misc:0   Missed beacon:0

So when I try to get the interface up, it keeps trying but of course can't:

Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:11:95:87:95:2a
Sending on   LPF/wlan0/00:11:95:87:95:2a
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


If I set it to static, then it brings up the interface immediately with 
no connectivity.

And if I turn off WEP, then I'm able to connect either way.

I kind of figured someone else might be going through this because it's 
happening on both my desktop and my laptop.  But then again, both 
machines have wirless chipsets with the Real Tek 8180 chipsets.  The 
real strange thing is that they worked in Ubuntu.

Angelo