ndiswrapper

I was and still have very similar problems with a DWL-520 pci adapter and
decided to use an 8k stack rpm from Linuxant. It didn't help.
----- Original Message ----- 
From: "Corey Wallis" <corey@...>
To: <ndiswrapper-general@...>
Sent: Wednesday, June 09, 2004 6:31 AM
Subject: [Ndiswrapper-general] Linksys WPC54g & Fedora Core 2


> Dear All,
>
> I'm trying to get my Linksys WPC54g card working under Fedora Core 2.
> The ndiswrapper package compiles and installs with no errors. The
> Linksys drivers are successfully installed by ndiswrapper as well. The
> problem occurs during the finalisation of the installation.
>
> I can load the ndiswrapper kernel module with no errors reported.
> However when I check dmesg the following to lines are associated with
> the wlan0 interface.
>
> wlan0: ndiswrapper ethernet device 00:0c:41:2c:c3:20 using driver
> bcmwl5.sys
> wlan0: adding wep key 0 failed (C0010015)
>
> When I try to configure the wlan0 to use a wep encryption key the
> following error message is reported
>
> # /sbin/iwconfig wlan0 key restricted s:mypassword
> Error for wireless request "Set Encode" (8B2A) :
>     SET failed on device wlan0 ; Invalid argument.
>
> However the wlan0 device is recognised and I can use the network
> configuration tool to configure the wlan0 device. The problem though is
> that it is unable to use dhcp to get a valid IP from the access point.
> I'm also unable to set the ESSID and make it stick.
>
> When I run iwconfig with no parameters the following is output.
>
> wlan0  IEEE 802.11g  ESSID:""  Nickname:"myhost"
>        Mode:Managed  Frequency:2.437GHz  Access Point: FF:FF:FF:FF:FF:FF
>        Bit Rate=54Mb/s   Tx-Power:17 dBm
>        RTS thr=2347 B   Fragment thr=2346 B
>        Encryption key:####-####-####-####-####   Security mode:open
>        Power Management:off
>        Link Quality:100/100  Signal level:-10 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
>
> It would appear that the wep key has made it to the configuration but I
> can't set the security mode to restricted. I believe the card is able to
> contact the access point but is unable to communicate with it because
> there is something going wrong with the wep encryption.
>
> What am I missing? This is a stock standard installation of Fedora,
> could this be a 4K stacks issue?
>
> With many thanks.
>
> -Corey
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

First thing you need to test is if you are able to get ndiswrapper
working without WEP.

Pontus

On Wed, 2004-06-09 at 12:31, Corey Wallis wrote:
> Dear All,
> 
> I'm trying to get my Linksys WPC54g card working under Fedora Core 2.
> The ndiswrapper package compiles and installs with no errors. The
> Linksys drivers are successfully installed by ndiswrapper as well. The
> problem occurs during the finalisation of the installation.
> 
> I can load the ndiswrapper kernel module with no errors reported.
> However when I check dmesg the following to lines are associated with
> the wlan0 interface. 
> 
> wlan0: ndiswrapper ethernet device 00:0c:41:2c:c3:20 using driver
> bcmwl5.sys
> wlan0: adding wep key 0 failed (C0010015)
> 
> When I try to configure the wlan0 to use a wep encryption key the
> following error message is reported
> 
> # /sbin/iwconfig wlan0 key restricted s:mypassword
> Error for wireless request "Set Encode" (8B2A) :
>     SET failed on device wlan0 ; Invalid argument.
> 
> However the wlan0 device is recognised and I can use the network
> configuration tool to configure the wlan0 device. The problem though is
> that it is unable to use dhcp to get a valid IP from the access point.
> I'm also unable to set the ESSID and make it stick. 
> 
> When I run iwconfig with no parameters the following is output. 
> 
> wlan0  IEEE 802.11g  ESSID:""  Nickname:"myhost"
>        Mode:Managed  Frequency:2.437GHz  Access Point: FF:FF:FF:FF:FF:FF
>        Bit Rate=54Mb/s   Tx-Power:17 dBm
>        RTS thr=2347 B   Fragment thr=2346 B
>        Encryption key:####-####-####-####-####   Security mode:open
>        Power Management:off
>        Link Quality:100/100  Signal level:-10 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
> 
> It would appear that the wep key has made it to the configuration but I
> can't set the security mode to restricted. I believe the card is able to
> contact the access point but is unable to communicate with it because
> there is something going wrong with the wep encryption. 
> 
> What am I missing? This is a stock standard installation of Fedora,
> could this be a 4K stacks issue?
> 
> With many thanks. 
> 
> -Corey
> 
>  
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
> 
> 
> 
> !DSPAM:40c6e7a6290336810117234!
>

If you are not using latest cvs, you are urged to try that. 

The error code indicates that the key is not a valid key. Make sure
you give the key correctly. If you are using ASCII string, I hope you
are aware of s: prefix (see the man page for iwconfig).

-- 
Giri

Hi Corey,
I'm running the same card as you are with .8rc2 and it is working fine
with WEP enabled.  Although, I am only using a 64 bit key which encodes
to a 10 digit hash.  I am not running a 128 bit key.  The GUI under
System Settings->Network which is what I used to configure the wlan0
device worked fine for me. Did you remeber to prefix the digits with the
"0x".  I assume you did.  Are you using a 128 bit key? I think that
results in a 24 or 26 digit hash. Maybe that's the problem.  Go to
/etc/sysconfig/devices directory and you should see the two files
modified by the gui, ifcfg-wlan0 and key-wlan0.  See if there is a
problem in there.  See if all the parameters in there are correct if not
use vi and edit them there and see if the card will work ie
bootproto=dhcp, essid=whatever, channel=x, etc you get the idea.  Hope
that works for you.

You wouldn't happen to be running on a hyperthreaded machine would you. 
If so, if you can get your machine running could you let me know if it
hangs when you run under the smp kernel.  I'm the guy who put that
question in yesterday and I haven't heard anything yet.  Everything
works fine except that the machine hangs on me when running as smp. 
Good Luck

Chris

On Wed, 2004-06-09 at 06:31, Corey Wallis wrote:
> Dear All,
> 
> I'm trying to get my Linksys WPC54g card working under Fedora Core 2.
> The ndiswrapper package compiles and installs with no errors. The
> Linksys drivers are successfully installed by ndiswrapper as well. The
> problem occurs during the finalisation of the installation.
> 
> I can load the ndiswrapper kernel module with no errors reported.
> However when I check dmesg the following to lines are associated with
> the wlan0 interface. 
> 
> wlan0: ndiswrapper ethernet device 00:0c:41:2c:c3:20 using driver
> bcmwl5.sys
> wlan0: adding wep key 0 failed (C0010015)
> 
> When I try to configure the wlan0 to use a wep encryption key the
> following error message is reported
> 
> # /sbin/iwconfig wlan0 key restricted s:mypassword
> Error for wireless request "Set Encode" (8B2A) :
>     SET failed on device wlan0 ; Invalid argument.
> 
> However the wlan0 device is recognised and I can use the network
> configuration tool to configure the wlan0 device. The problem though is
> that it is unable to use dhcp to get a valid IP from the access point.
> I'm also unable to set the ESSID and make it stick. 
> 
> When I run iwconfig with no parameters the following is output. 
> 
> wlan0  IEEE 802.11g  ESSID:""  Nickname:"myhost"
>        Mode:Managed  Frequency:2.437GHz  Access Point: FF:FF:FF:FF:FF:FF
>        Bit Rate=54Mb/s   Tx-Power:17 dBm
>        RTS thr=2347 B   Fragment thr=2346 B
>        Encryption key:####-####-####-####-####   Security mode:open
>        Power Management:off
>        Link Quality:100/100  Signal level:-10 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
> 
> It would appear that the wep key has made it to the configuration but I
> can't set the security mode to restricted. I believe the card is able to
> contact the access point but is unable to communicate with it because
> there is something going wrong with the wep encryption. 
> 
> What am I missing? This is a stock standard installation of Fedora,
> could this be a 4K stacks issue?
> 
> With many thanks. 
> 
> -Corey
> 
>  
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

Dear Chris,

I was using version 0.8rc2. The key that is used by my windows machine,
which I'm using at the moment until I get this resolved, is 10 characters
long and is specified as a 40 bit wep key. I get the same error as reported
by iwconfig when I try to set the key using the gui or iwconfig from the
command line. 

Since I posted last I noticed version 0.8 is now available which I will try.
I'm not sure how to download via cvs, I'm new to Linux as you may have
guessed. So at the moment I'm restricted to the releases via tar.gz and the
sourceforge website. 

When checking the ifcfg-wlan0 and key-wlan0 what should I be looking for? Is
there any documentation on what a typical file should look like? I'm also
unable to test access without a wep key because the access point is
corporately controlled and I don't have the ability to turn wep off. 

Unfortunately my laptop isn't capable of hyperthreading so I can't help you
with that problem. 

With many thanks for your help. 

-Corey

-----Original Message-----
From: ndiswrapper-general-admin@...
[mailto:ndiswrapper-general-admin@...] On Behalf Of Chris
Kerios
Sent: Thursday, 10 June 2004 8:12 AM
To: Corey Wallis
Cc: ndiswrapper-general@...
Subject: Re: [Ndiswrapper-general] Linksys WPC54g & Fedora Core 2

Hi Corey,
I'm running the same card as you are with .8rc2 and it is working fine
with WEP enabled.  Although, I am only using a 64 bit key which encodes
to a 10 digit hash.  I am not running a 128 bit key.  The GUI under
System Settings->Network which is what I used to configure the wlan0
device worked fine for me. Did you remeber to prefix the digits with the
"0x".  I assume you did.  Are you using a 128 bit key? I think that
results in a 24 or 26 digit hash. Maybe that's the problem.  Go to
/etc/sysconfig/devices directory and you should see the two files
modified by the gui, ifcfg-wlan0 and key-wlan0.  See if there is a
problem in there.  See if all the parameters in there are correct if not
use vi and edit them there and see if the card will work ie
bootproto=dhcp, essid=whatever, channel=x, etc you get the idea.  Hope
that works for you.

You wouldn't happen to be running on a hyperthreaded machine would you. 
If so, if you can get your machine running could you let me know if it
hangs when you run under the smp kernel.  I'm the guy who put that
question in yesterday and I haven't heard anything yet.  Everything
works fine except that the machine hangs on me when running as smp. 
Good Luck

Chris

On Wed, 2004-06-09 at 06:31, Corey Wallis wrote:
> Dear All,
> 
> I'm trying to get my Linksys WPC54g card working under Fedora Core 2.
> The ndiswrapper package compiles and installs with no errors. The
> Linksys drivers are successfully installed by ndiswrapper as well. The
> problem occurs during the finalisation of the installation.
> 
> I can load the ndiswrapper kernel module with no errors reported.
> However when I check dmesg the following to lines are associated with
> the wlan0 interface. 
> 
> wlan0: ndiswrapper ethernet device 00:0c:41:2c:c3:20 using driver
> bcmwl5.sys
> wlan0: adding wep key 0 failed (C0010015)
> 
> When I try to configure the wlan0 to use a wep encryption key the
> following error message is reported
> 
> # /sbin/iwconfig wlan0 key restricted s:mypassword
> Error for wireless request "Set Encode" (8B2A) :
>     SET failed on device wlan0 ; Invalid argument.
> 
> However the wlan0 device is recognised and I can use the network
> configuration tool to configure the wlan0 device. The problem though is
> that it is unable to use dhcp to get a valid IP from the access point.
> I'm also unable to set the ESSID and make it stick. 
> 
> When I run iwconfig with no parameters the following is output. 
> 
> wlan0  IEEE 802.11g  ESSID:""  Nickname:"myhost"
>        Mode:Managed  Frequency:2.437GHz  Access Point: FF:FF:FF:FF:FF:FF
>        Bit Rate=54Mb/s   Tx-Power:17 dBm
>        RTS thr=2347 B   Fragment thr=2346 B
>        Encryption key:####-####-####-####-####   Security mode:open
>        Power Management:off
>        Link Quality:100/100  Signal level:-10 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
> 
> It would appear that the wep key has made it to the configuration but I
> can't set the security mode to restricted. I believe the card is able to
> contact the access point but is unable to communicate with it because
> there is something going wrong with the wep encryption. 
> 
> What am I missing? This is a stock standard installation of Fedora,
> could this be a 4K stacks issue?
> 
> With many thanks. 
> 
> -Corey
> 
>  
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general



-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general@...
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

Hi Corey,
What I've done is inserted my ifcfg-wlan0, keys-wlan0 file and
modprobe.conf files.  You can take a look at them.  I've changed my WEP
key in the keys-wlan0 file and ESSID= parameter for obvious reasons but
you will get the idea.  Keep in mind that these are the three files that
configure the entire wireless system.  If you are OK in these files then
your problem is with the installation/build of ndiswrapper.  Happy
hacking.
Chris

/etc/sysconfig/networking/devices/ifcfg-wlan0 file
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
ONBOOT=no
USERCTL=yes
PEERDNS=yes
GATEWAY=
TYPE=Wireless
DHCP_HOSTNAME=oscar
IPADDR=
DEVICE=wlan0
HWADDR=
BOOTPROTO=dhcp
DOMAIN=
NETMASK=
ESSID=myworld
CHANNEL=8
MODE=Auto
RATE=Auto
IPV6INIT=no

/etc/sysconfig/networking/devices/
KEY=78C684A33E

/etc/modprobe.conf
alias wlan0 ndiswrapper




On Thu, 2004-06-10 at 05:21, Corey Wallis (InetWizardry) wrote:
> Dear Chris,
> 
> I was using version 0.8rc2. The key that is used by my windows machine,
> which I'm using at the moment until I get this resolved, is 10 characters
> long and is specified as a 40 bit wep key. I get the same error as reported
> by iwconfig when I try to set the key using the gui or iwconfig from the
> command line. 
> 
> Since I posted last I noticed version 0.8 is now available which I will try.
> I'm not sure how to download via cvs, I'm new to Linux as you may have
> guessed. So at the moment I'm restricted to the releases via tar.gz and the
> sourceforge website. 
> 
> When checking the ifcfg-wlan0 and key-wlan0 what should I be looking for? Is
> there any documentation on what a typical file should look like? I'm also
> unable to test access without a wep key because the access point is
> corporately controlled and I don't have the ability to turn wep off. 
> 
> Unfortunately my laptop isn't capable of hyperthreading so I can't help you
> with that problem. 
> 
> With many thanks for your help. 
> 
> -Corey
> 
> -----Original Message-----
> From: ndiswrapper-general-admin@...
> [mailto:ndiswrapper-general-admin@...] On Behalf Of Chris
> Kerios
> Sent: Thursday, 10 June 2004 8:12 AM
> To: Corey Wallis
> Cc: ndiswrapper-general@...
> Subject: Re: [Ndiswrapper-general] Linksys WPC54g & Fedora Core 2
> 
> Hi Corey,
> I'm running the same card as you are with .8rc2 and it is working fine
> with WEP enabled.  Although, I am only using a 64 bit key which encodes
> to a 10 digit hash.  I am not running a 128 bit key.  The GUI under
> System Settings->Network which is what I used to configure the wlan0
> device worked fine for me. Did you remeber to prefix the digits with the
> "0x".  I assume you did.  Are you using a 128 bit key? I think that
> results in a 24 or 26 digit hash. Maybe that's the problem.  Go to
> /etc/sysconfig/devices directory and you should see the two files
> modified by the gui, ifcfg-wlan0 and key-wlan0.  See if there is a
> problem in there.  See if all the parameters in there are correct if not
> use vi and edit them there and see if the card will work ie
> bootproto=dhcp, essid=whatever, channel=x, etc you get the idea.  Hope
> that works for you.
> 
> You wouldn't happen to be running on a hyperthreaded machine would you. 
> If so, if you can get your machine running could you let me know if it
> hangs when you run under the smp kernel.  I'm the guy who put that
> question in yesterday and I haven't heard anything yet.  Everything
> works fine except that the machine hangs on me when running as smp. 
> Good Luck
> 
> Chris
> 
> On Wed, 2004-06-09 at 06:31, Corey Wallis wrote:
> > Dear All,
> > 
> > I'm trying to get my Linksys WPC54g card working under Fedora Core 2.
> > The ndiswrapper package compiles and installs with no errors. The
> > Linksys drivers are successfully installed by ndiswrapper as well. The
> > problem occurs during the finalisation of the installation.
> > 
> > I can load the ndiswrapper kernel module with no errors reported.
> > However when I check dmesg the following to lines are associated with
> > the wlan0 interface. 
> > 
> > wlan0: ndiswrapper ethernet device 00:0c:41:2c:c3:20 using driver
> > bcmwl5.sys
> > wlan0: adding wep key 0 failed (C0010015)
> > 
> > When I try to configure the wlan0 to use a wep encryption key the
> > following error message is reported
> > 
> > # /sbin/iwconfig wlan0 key restricted s:mypassword
> > Error for wireless request "Set Encode" (8B2A) :
> >     SET failed on device wlan0 ; Invalid argument.
> > 
> > However the wlan0 device is recognised and I can use the network
> > configuration tool to configure the wlan0 device. The problem though is
> > that it is unable to use dhcp to get a valid IP from the access point.
> > I'm also unable to set the ESSID and make it stick. 
> > 
> > When I run iwconfig with no parameters the following is output. 
> > 
> > wlan0  IEEE 802.11g  ESSID:""  Nickname:"myhost"
> >        Mode:Managed  Frequency:2.437GHz  Access Point: FF:FF:FF:FF:FF:FF
> >        Bit Rate=54Mb/s   Tx-Power:17 dBm
> >        RTS thr=2347 B   Fragment thr=2346 B
> >        Encryption key:####-####-####-####-####   Security mode:open
> >        Power Management:off
> >        Link Quality:100/100  Signal level:-10 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
> > 
> > It would appear that the wep key has made it to the configuration but I
> > can't set the security mode to restricted. I believe the card is able to
> > contact the access point but is unable to communicate with it because
> > there is something going wrong with the wep encryption. 
> > 
> > What am I missing? This is a stock standard installation of Fedora,
> > could this be a 4K stacks issue?
> > 
> > With many thanks. 
> > 
> > -Corey
> > 
> >  
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: GNOME Foundation
> > Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> > GNOME Users and Developers European Conference, 28-30th June in Norway
> > http://2004/guadec.org
> > _______________________________________________
> > Ndiswrapper-general mailing list
> > Ndiswrapper-general@...
> > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general