still struggling with ndiswrapper

[James Pifer]

I've tried getting my builtin wireless card in my laptop working before
and was close, but could never get it working. I would REALLY like to
use my laptop without being tied to my desk. Previously I could load the
drivers, using ndiswrapper, and get all the way up to loading it, but I
could never get an ipaddress. So I figured I would try again but this
time remove wep and see if can connect.

lspci shows me this:

02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)

When I try to modprobe ndiswrapper the machine locks up hard. After a
reboot I see this in /var/log/messages:

Oct 27 15:09:45 kernel: ndiswrapper version 1.4rc4 loaded
(preempt=no,smp=yes)
Oct 27 15:09:45 kernel: ndiswrapper: driver bcmwl5 (Broadcom,10/20/2004,
3.70.22.0) loaded
Oct 27 15:09:45 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18
(level, low) -> IRQ 193
Oct 27 15:09:45 kernel: ndiswrapper: using irq 193

I also tried reinstalling ndiswrapper but still get the same thing. If
it's an IRQ problem, any suggestions on how to handle it?

Any other suggestions?

Thanks,
James

[Rick Stevens]

On Thu, 2005-10-27 at 16:00 -0400, James Pifer wrote:
>  I've tried getting my builtin wireless card in my laptop working
> before
>  and was close, but could never get it working. I would REALLY like to
>  use my laptop without being tied to my desk. Previously I could load the
>  drivers, using ndiswrapper, and get all the way up to loading it, but I
>  could never get an ipaddress. So I figured I would try again but this
>  time remove wep and see if can connect.
>  
>  lspci shows me this:
>  
>  02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
>  Wireless LAN Controller (rev 03)
>  
>  When I try to modprobe ndiswrapper the machine locks up hard. After a
>  reboot I see this in /var/log/messages:
>  
>  Oct 27 15:09:45 kernel: ndiswrapper version 1.4rc4 loaded
>  (preempt=no,smp=yes)
>  Oct 27 15:09:45 kernel: ndiswrapper: driver bcmwl5 (Broadcom,10/20/2004,
>  3.70.22.0) loaded
>  Oct 27 15:09:45 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18
>  (level, low) -> IRQ 193
>  Oct 27 15:09:45 kernel: ndiswrapper: using irq 193 
Uh, oh.  Smells like an apic problem to me.

>  I also tried reinstalling ndiswrapper but still get the same thing.
> If
>  it's an IRQ problem, any suggestions on how to handle it? 
Gee, I don't get that.  I'm using a Fujitsu Lifebook C2200 on the stock
FC4 kernel:

[root@golem ~]# uname -r
2.6.13-1.1532_FC4

[root@golem ~]# lspci
<snip>
00:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 02)
</snip>

[root@golem ~]# tail /var/log/messages
<snip>
Oct 27 14:04:01 golem kernel: ndiswrapper version 1.4rc4 loaded
(preempt=no,smp=no)
Oct 27 14:04:01 golem kernel: ndiswrapper: driver bcmwl5
(Broadcom,02/12/2003, 3.10.39.7) loaded
Oct 27 14:04:01 golem kernel: ACPI: PCI Interrupt 0000:00:12.0[A] ->
Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
Oct 27 14:04:01 golem kernel: ndiswrapper: using irq 11
Oct 27 14:04:02 golem kernel: wlan0: vendor: ''
Oct 27 14:04:02 golem kernel: wlan0: ndiswrapper ethernet device
00:90:96:57:e9:ff using driver bcmwl5, 14E4:4320:10CF:1204.5.conf
Oct 27 14:04:02 golem kernel: ndiswrapper (set_auth_mode:685): setting
auth mode failed (C0010015)
Oct 27 14:04:02 golem kernel: wlan0: encryption modes supported: none
</snip>

>  Any other suggestions? 
Although we appear to have the same wireless chipset, I am using an
older Broadcom driver.  It works with the default 4K stack kernel.  I'd
try a couple of things:

1. Try booting with the "noapic" option specified on the boot line

2. Try recompiling your kernel with 8K stacks enabled

If you'd like to try my older Broadcom driver, I suppose I could send
it to you.  Contact me off-list if you wish to have it.

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens(a)vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-                Huked on foniks reely wurked for me!                -
----------------------------------------------------------------------

[Josh Coffman]

--- Rick Stevens <rstevens(a)vitalstream.com&gt; wrote:

>  On Thu, 2005-10-27 at 16:00 -0400, James Pifer
>  wrote:
>  > I've tried getting my builtin wireless card in my
>  laptop working before
>  > and was close, but could never get it working. I
>  would REALLY like to
>  > use my laptop without being tied to my desk.
>  Previously I could load the
>  > drivers, using ndiswrapper, and get all the way up
>  to loading it, but I
>  > could never get an ipaddress. So I figured I would
>  try again but this
>  > time remove wep and see if can connect.
>  > 
>  > lspci shows me this:
>  > 
>  > 02:02.0 Network controller: Broadcom Corporation
>  BCM4306 802.11b/g
>  > Wireless LAN Controller (rev 03)
>  > 
>  > When I try to modprobe ndiswrapper the machine
>  locks up hard. After a
>  > reboot I see this in /var/log/messages:
>  > 
>  > Oct 27 15:09:45 kernel: ndiswrapper version 1.4rc4
>  loaded
>  > (preempt=no,smp=yes)
>  > Oct 27 15:09:45 kernel: ndiswrapper: driver bcmwl5
>  (Broadcom,10/20/2004,
>  > 3.70.22.0) loaded
>  > Oct 27 15:09:45 kernel: ACPI: PCI Interrupt
>  0000:02:02.0[A] -> GSI 18
>  > (level, low) -> IRQ 193
>  > Oct 27 15:09:45 kernel: ndiswrapper: using irq 193
>  
>  Uh, oh.  Smells like an apic problem to me.
>  
>  > I also tried reinstalling ndiswrapper but still
>  get the same thing. If
>  > it's an IRQ problem, any suggestions on how to
>  handle it?
>  
>  Gee, I don't get that.  I'm using a Fujitsu Lifebook
>  C2200 on the stock
>  FC4 kernel:
>  
>  [root@golem ~]# uname -r
>  2.6.13-1.1532_FC4
>  
>  [root@golem ~]# lspci
>  <snip>
>  00:12.0 Network controller: Broadcom Corporation
>  BCM4306 802.11b/g
>  Wireless LAN Controller (rev 02)
>  </snip>
>  
>  [root@golem ~]# tail /var/log/messages
>  <snip>
>  Oct 27 14:04:01 golem kernel: ndiswrapper version
>  1.4rc4 loaded
>  (preempt=no,smp=no)
>  Oct 27 14:04:01 golem kernel: ndiswrapper: driver
>  bcmwl5
>  (Broadcom,02/12/2003, 3.10.39.7) loaded
>  Oct 27 14:04:01 golem kernel: ACPI: PCI Interrupt
>  0000:00:12.0[A] ->
>  Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
>  Oct 27 14:04:01 golem kernel: ndiswrapper: using irq
>  11
>  Oct 27 14:04:02 golem kernel: wlan0: vendor: ''
>  Oct 27 14:04:02 golem kernel: wlan0: ndiswrapper
>  ethernet device
>  00:90:96:57:e9:ff using driver bcmwl5,
>  14E4:4320:10CF:1204.5.conf
>  Oct 27 14:04:02 golem kernel: ndiswrapper
>  (set_auth_mode:685): setting
>  auth mode failed (C0010015)
>  Oct 27 14:04:02 golem kernel: wlan0: encryption
>  modes supported: none
>  </snip>
>  
>  > Any other suggestions?
>  
>  Although we appear to have the same wireless
>  chipset, I am using an
>  older Broadcom driver.  It works with the default 4K
>  stack kernel.  I'd
>  try a couple of things:
>  
>  1. Try booting with the "noapic" option specified on
>  the boot line
>  
>  2. Try recompiling your kernel with 8K stacks
>  enabled 
I'd not recomend recompiling the kernel with 8k stacks
based on advise I received. ..something about future
kernels may require 4k stacks.

Also, I have basically the same chipset on an HP
zv5000 and run it with not problems. just recently
upgraded ndiswrapper from v1.2 to v1.4. 

>  
>  If you'd like to try my older Broadcom driver, I
>  suppose I could send
>  it to you.  Contact me off-list if you wish to have
>  it.
>  
>  
----------------------------------------------------------------------
>  - Rick Stevens, Senior Systems Engineer    
>  rstevens(a)vitalstream.com -
>  - VitalStream, Inc.                      
>  http://www.vitalstream.com -
>  -                                                   
>                  -
>  -                Huked on foniks reely wurked for
>  me!                -
>   
looks like you have a release candidate version of
ndiswrapper. may not be related but you could get
stable release of 1.4

also, how are you installing ndiswraper? I've had
great success compiling from source available at
http://ndiswrapper.sf.net

you can also look for a suitable windows driver here:
https://www.linuxant.com/driverloader/drivers.php




	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

[L. Paul Andralouis]

Hi James:

     When you use ndiswrapper to list the drivers,
does it say that the card is present?  I forget the
exact syntax of what it says, but it lists the drivers
and if it can load the card, it says "hardware
present" or something like that.


--Paul

--- James Pifer <jep(a)obrien-pifer.com&gt; wrote:

>  I've tried getting my builtin wireless card in my
>  laptop working before
>  and was close, but could never get it working. I
>  would REALLY like to
>  use my laptop without being tied to my desk.
>  Previously I could load the
>  drivers, using ndiswrapper, and get all the way up
>  to loading it, but I
>  could never get an ipaddress. So I figured I would
>  try again but this
>  time remove wep and see if can connect.
>  
>  lspci shows me this:
>  
>  02:02.0 Network controller: Broadcom Corporation
>  BCM4306 802.11b/g
>  Wireless LAN Controller (rev 03)
>  
>  When I try to modprobe ndiswrapper the machine locks
>  up hard. After a
>  reboot I see this in /var/log/messages:
>  
>  Oct 27 15:09:45 kernel: ndiswrapper version 1.4rc4
>  loaded
>  (preempt=no,smp=yes)
>  Oct 27 15:09:45 kernel: ndiswrapper: driver bcmwl5
>  (Broadcom,10/20/2004,
>  3.70.22.0) loaded
>  Oct 27 15:09:45 kernel: ACPI: PCI Interrupt
>  0000:02:02.0[A] -> GSI 18
>  (level, low) -> IRQ 193
>  Oct 27 15:09:45 kernel: ndiswrapper: using irq 193
>  
>  I also tried reinstalling ndiswrapper but still get
>  the same thing. If
>  it's an IRQ problem, any suggestions on how to
>  handle it?
>  
>  Any other suggestions?
>  
>  Thanks,
>  James
>  
>  
>  -- 
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe:
>  https://www.redhat.com/mailman/listinfo/fedora-list
>   


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

[James Pifer]

On Fri, 2005-10-28 at 01:47 -0700, L. Paul Andralouis wrote:
>  Hi James:
>  
>       When you use ndiswrapper to list the drivers,
>  does it say that the card is present?  I forget the
>  exact syntax of what it says, but it lists the drivers
>  and if it can load the card, it says "hardware
>  present" or something like that.
>  
>  
>  --Paul
>   
Yes, when I did ndiswrapper -l I would get a response that the driver
was installed and the hardware was present. 

Thanks,
James

[Jeff Vian]

On Fri, 2005-10-28 at 09:44 -0400, James Pifer wrote:
>  On Fri, 2005-10-28 at 01:47 -0700, L. Paul Andralouis wrote:
>  > Hi James:
>  > 
>  >      When you use ndiswrapper to list the drivers,
>  > does it say that the card is present?  I forget the
>  > exact syntax of what it says, but it lists the drivers
>  > and if it can load the card, it says "hardware
>  > present" or something like that.
>  > 
>  > 
>  > --Paul
>  > 
>  
>  Yes, when I did ndiswrapper -l I would get a response that the driver
>  was installed and the hardware was present. 
>  
>  Thanks,
>  James
>   
One other thing I needed to do (and I just realized I did not tell you
earlier) was put the following 2 lines in modprobe.conf.  I think the
options line is the final step that made it work for me. Before that it
did not actually create the interface so it could not be activated.

	alias wlan0 ndiswrapper
	options ndiswrapper ifname wlan0

Note that the interface name and the alias can be almost anything you
want, but the config file in /etc/sysconfig/network-scripts must be
named appropriately.  I use ifcfg-wlan0 since that is the interface name
I chose.

[L. Paul Andralouis]

Hi James:

     I had a Linksys card that required that you set
the ssid to the actual network name, so If you were at
home and your network name is "home", you'd have to
set it as such.  Then when you went to a t-mobile
hotspot you'd have to set it to "tmobile".

     Most of them aren't that way, but just in case.

     I have also had a card that did not work right
with the fedora's 4k stack size.  The symptom there
was that it'd initially work, but then die when you
tried to put significant throughput thru it.

     The only other thing I've found is that some
ndiswrapper versions would not work with this
notebook.  You might try another version.

     Another hint is to completely delete the
ndiswrapper card from the network config, and create
it again, possibly rebooting after the delete.

     Once it works, do be aware that you have to
recompile every time you update the kernel.  Just go
in there and do a "make install".

     Hope this helps.

                    Best Regards,
                    L. Paul Andralouis

--- James Pifer <jep(a)obrien-pifer.com&gt; wrote:

>  On Fri, 2005-10-28 at 01:47 -0700, L. Paul
>  Andralouis wrote:
>  > Hi James:
>  > 
>  >      When you use ndiswrapper to list the drivers,
>  > does it say that the card is present?  I forget
>  the
>  > exact syntax of what it says, but it lists the
>  drivers
>  > and if it can load the card, it says "hardware
>  > present" or something like that.
>  > 
>  > 
>  > --Paul
>  > 
>  
>  Yes, when I did ndiswrapper -l I would get a
>  response that the driver
>  was installed and the hardware was present. 
>  
>  Thanks,
>  James
>  
>  -- 
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe:
>  https://www.redhat.com/mailman/listinfo/fedora-list
>   


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

[Jeff Vian]

On Thu, 2005-10-27 at 16:00 -0400, James Pifer wrote:
>  I've tried getting my builtin wireless card in my laptop working
> before
>  and was close, but could never get it working. I would REALLY like to
>  use my laptop without being tied to my desk. Previously I could load the
>  drivers, using ndiswrapper, and get all the way up to loading it, but I
>  could never get an ipaddress. So I figured I would try again but this
>  time remove wep and see if can connect.
>  
>  lspci shows me this:
>  
>  02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
>  Wireless LAN Controller (rev 03)
>  
>  When I try to modprobe ndiswrapper the machine locks up hard. After a
>  reboot I see this in /var/log/messages:
>  
>  Oct 27 15:09:45 kernel: ndiswrapper version 1.4rc4 loaded
>  (preempt=no,smp=yes)
>  Oct 27 15:09:45 kernel: ndiswrapper: driver bcmwl5 (Broadcom,10/20/2004,
>  3.70.22.0) loaded
>  Oct 27 15:09:45 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18
>  (level, low) -> IRQ 193
>  Oct 27 15:09:45 kernel: ndiswrapper: using irq 193
>  
>  I also tried reinstalling ndiswrapper but still get the same thing. If
>  it's an IRQ problem, any suggestions on how to handle it?
>  
>  Any other suggestions?
>   
It may be related to the 4k stack problem.  I had that on my laptop and
used the kernel with 16k stack from
http://www.linuxant.com/driverloader/wlan/full/downloads-fc4-i686.php
to solve it.

>  Thanks,
>  James
>  
>

[James Pifer]

>  It may be related to the 4k stack problem.  I had that on my laptop
> and
>  used the kernel with 16k stack from
>  http://www.linuxant.com/driverloader/wlan/full/downloads-fc4-i686.php
>  to solve it.
>  
>  > Thanks,
>  > James
>  > 
>  > 
>   
Okay, now I'm running a kernel with 16k stacks. I also loaded
ndiswrapper 1.5. 

I can load everything like this:

ndiswrapper -i /install/ndiswrapper/broadcom/bcmwl5.inf
/sbin/modprobe ndiswrapper
/sbin/iwconfig wlan0 mode Managed
/sbin/iwconfig wlan0 key my_key_goes_here
/sbin/iwconfig wlan0 essid my_ssid_goes_here
/sbin/ifconfig wlan0 192.168.1.25 netmask 255.255.255.0 up

In /var/log/messages I get this:
Nov  2 15:03:54 laptop kernel: ndiswrapper version 1.5 loaded
(preempt=no,smp=yes)
Nov  2 15:03:54 laptop kernel: ndiswrapper: driver bcmwl5
(Broadcom,10/20/2004, 3.70.22.0) loaded
Nov  2 15:03:54 laptop kernel: ACPI: PCI Interrupt 0000:02:02.0[A] ->
GSI 18 (level, low) -> IRQ 193
Nov  2 15:03:54 laptop kernel: eth%d: ndiswrapper ethernet device
00:90:4b:5f:be:d2
Nov  2 15:03:54 laptop kernel: ndiswrapper: using irq 193
Nov  2 15:03:55 laptop kernel: wlan0: vendor: ''
Nov  2 15:03:55 laptop kernel: wlan0: ndiswrapper ethernet device
00:90:4b:5f:be:d2 using driver bcmwl5, 14E4:4320.5.conf
Nov  2 15:03:55 laptop kernel: wlan0: encryption modes supported: WEP;
TKIP with WPA; AES/CCMP with WPA

Here's the big problem at the moment. I don't see this device connecting
to my wireless router. If I look at the connections on my wireless
router this mac address does not connect. I've also tried it with
encryption turned off on the router, and not using a WEP key, but it
still doesn't connect. 

Anyone have any suggestions now?

Thanks,
James

[James Pifer]

>  Okay, now I'm running a kernel with 16k stacks. I also loaded
>  ndiswrapper 1.5. 
>  
>  I can load everything like this:
>  
>  ndiswrapper -i /install/ndiswrapper/broadcom/bcmwl5.inf
>  /sbin/modprobe ndiswrapper
>  /sbin/iwconfig wlan0 mode Managed
>  /sbin/iwconfig wlan0 key my_key_goes_here
>  /sbin/iwconfig wlan0 essid my_ssid_goes_here
>  /sbin/ifconfig wlan0 192.168.1.25 netmask 255.255.255.0 up
>   
One more thing. If I run iwconfig after running the above commands I get
this:

wlan0     IEEE 802.11g  ESSID:off/any
          Mode:Managed  Frequency:2.462 GHz  Access Point:
00:00:00:00:00:00
          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: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

It doesn't show the ESSID, says Encryption is off, and Access Point
address of 00:00:00:00:00:00.

I assume these settings are part of my problem. Why didn't the settings
"take"? Anyone know what I am doing wrong?

Thanks,
James

[Josh Coffman]

--- James Pifer <jep(a)obrien-pifer.com&gt; wrote:

>  > Okay, now I'm running a kernel with 16k stacks. I
>  also loaded
>  > ndiswrapper 1.5. 
>  > 
>  > I can load everything like this:
>  > 
>  > ndiswrapper -i
>  /install/ndiswrapper/broadcom/bcmwl5.inf
>  > /sbin/modprobe ndiswrapper
>  > /sbin/iwconfig wlan0 mode Managed
>  > /sbin/iwconfig wlan0 key my_key_goes_here
>  > /sbin/iwconfig wlan0 essid my_ssid_goes_here
>  > /sbin/ifconfig wlan0 192.168.1.25 netmask
>  255.255.255.0 up
>  > 
>  
>  One more thing. If I run iwconfig after running the
>  above commands I get
>  this:
>  
>  wlan0     IEEE 802.11g  ESSID:off/any
>            Mode:Managed  Frequency:2.462 GHz  Access
>  Point:
>  00:00:00:00:00:00
>            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: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
>  
>  It doesn't show the ESSID, says Encryption is off,
>  and Access Point
>  address of 00:00:00:00:00:00.
>  
>  I assume these settings are part of my problem. Why
>  didn't the settings
>  "take"? Anyone know what I am doing wrong?
>  
>  Thanks,
>  James
>   
since noone else has responded...

did you check "ndiswrapper -l" again? show that the
driver is loaded and all?

then did you try "dhclient wlan0"? then check iwconfig
to see if you got connected? or try "iwlist wlan0
scan" to find out whether it sees any networks?

is your access point broadcasting the essid? have MAC
filtering on?

..just covering the basics.

i've have some goofy results sometimes with iwconfig
and had to do this on a few occasions:

command "dhclient -r wlan0"
using network applet, Deactivate wlan0
using network applet, Activate wlan0




	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

[James Pifer]

>  did you check "ndiswrapper -l" again? show that the
>  driver is loaded and all?
>   
Yes, ndiswrapper -l shows:
[root@laptop ~]# ndiswrapper -l
Installed ndis drivers:
bcmwl5          driver present, hardware present


>  then did you try "dhclient wlan0"? then check iwconfig
>  to see if you got connected? or try "iwlist wlan0
>  scan" to find out whether it sees any networks?
>   
Yes, the scan shows that it sees 4 wireless networks, including mine.

>  is your access point broadcasting the essid? have MAC
>  filtering on? 
Yes, it is broadcasting the essid. 
I do have MAC filtering on, but my wireless cards MAC address is in the
list to allow. I guess I could shut it off to rule it out. Same thing
with MAC filtering off. Never see a connection on the router.  

>  
>  ..just covering the basics.
>  
>  i've have some goofy results sometimes with iwconfig
>  and had to do this on a few occasions:
>  
>  command "dhclient -r wlan0"
>  using network applet, Deactivate wlan0
>  using network applet, Activate wlan0
>   
I'll give this a look. I really don't want to use DHCP though. It's
turned off on my wireless router and is provided by another box on the
network. Should still work, but I get DHCP discover failures on my
wireless router, so that could be another obstacle. I do have another
machine running Windows XP connected with wireless, so I know it is
functioning. That machine also has a static address assigned. 

Thanks,
James

[Jeff Vian]

On Wed, 2005-11-02 at 17:04 -0500, James Pifer wrote:
>  > Okay, now I'm running a kernel with 16k stacks. I also
> loaded
>  > ndiswrapper 1.5. 
>  > 
>  > I can load everything like this:
>  > 
>  > ndiswrapper -i /install/ndiswrapper/broadcom/bcmwl5.inf
>  > /sbin/modprobe ndiswrapper
>  > /sbin/iwconfig wlan0 mode Managed
>  > /sbin/iwconfig wlan0 key my_key_goes_here
>  > /sbin/iwconfig wlan0 essid my_ssid_goes_here
>  > /sbin/ifconfig wlan0 192.168.1.25 netmask 255.255.255.0 up
>  > 
>  
>  One more thing. If I run iwconfig after running the above commands I get
>  this:
>  
>  wlan0     IEEE 802.11g  ESSID:off/any
>            Mode:Managed  Frequency:2.462 GHz  Access Point:
>  00:00:00:00:00:00
>            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: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
>  
>  It doesn't show the ESSID, says Encryption is off, and Access Point
>  address of 00:00:00:00:00:00.
>  
>  I assume these settings are part of my problem. Why didn't the settings
>  "take"? Anyone know what I am doing wrong?
>   
I think the channel may have an affect like this.  What channel is the
AP using?  Then set the card to the same channel.

>  Thanks,
>  James
>

[Jeff Vian]

On Wed, 2005-11-02 at 15:10 -0500, James Pifer wrote:
>  > It may be related to the 4k stack problem.  I had that on my
> laptop and
>  > used the kernel with 16k stack from
>  > http://www.linuxant.com/driverloader/wlan/full/downloads-fc4-i686.php
>  > to solve it.
>  > 
>  > > Thanks,
>  > > James
>  > > 
>  > > 
>  > 
>  
>  Okay, now I'm running a kernel with 16k stacks. I also loaded
>  ndiswrapper 1.5. 
>  
>  I can load everything like this:
>  
>  ndiswrapper -i /install/ndiswrapper/broadcom/bcmwl5.inf
>  /sbin/modprobe ndiswrapper
>  /sbin/iwconfig wlan0 mode Managed
>  /sbin/iwconfig wlan0 key my_key_goes_here
>  /sbin/iwconfig wlan0 essid my_ssid_goes_here
>  /sbin/ifconfig wlan0 192.168.1.25 netmask 255.255.255.0 up
>  
>  In /var/log/messages I get this:
>  Nov  2 15:03:54 laptop kernel: ndiswrapper version 1.5 loaded
>  (preempt=no,smp=yes)
>  Nov  2 15:03:54 laptop kernel: ndiswrapper: driver bcmwl5
>  (Broadcom,10/20/2004, 3.70.22.0) loaded
>  Nov  2 15:03:54 laptop kernel: ACPI: PCI Interrupt 0000:02:02.0[A] ->
>  GSI 18 (level, low) -> IRQ 193
>  Nov  2 15:03:54 laptop kernel: eth%d: ndiswrapper ethernet device
>  00:90:4b:5f:be:d2
>  Nov  2 15:03:54 laptop kernel: ndiswrapper: using irq 193
>  Nov  2 15:03:55 laptop kernel: wlan0: vendor: ''
>  Nov  2 15:03:55 laptop kernel: wlan0: ndiswrapper ethernet device
>  00:90:4b:5f:be:d2 using driver bcmwl5, 14E4:4320.5.conf
>  Nov  2 15:03:55 laptop kernel: wlan0: encryption modes supported: WEP;
>  TKIP with WPA; AES/CCMP with WPA
>  
>  Here's the big problem at the moment. I don't see this device connecting
>  to my wireless router. If I look at the connections on my wireless
>  router this mac address does not connect. I've also tried it with
>  encryption turned off on the router, and not using a WEP key, but it
>  still doesn't connect. 
>  
>  Anyone have any suggestions now?
>   
As I recall, you previously had the system locking up when you did the
modprobe step.  This seems to be some progress.

Use ndiswrapper -l to see the interface drivers and device are present.

Have you tried using iwlist to see if the adapter finds any local access
points? It should see the access point even if it does not connect, and
should tell you about it.

Other things that might interfere are mode, channel (I think 1-12, but 6
is usually the default for the AP), and maybe others.
I usually try to get the connection without encryption, then enable
encryption later.

My ifcfg-wlan0 is:

IPV6INIT=no
ONBOOT=no
USERCTL=no
PEERDNS=yes
GATEWAY=
TYPE=Wireless
DEVICE=wlan0
HWADDR=
BOOTPROTO=dhcp
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
ESSID='my_essid'
CHANNEL=6
MODE=Managed
RATE=Auto

That worked first time with dhcp, although I have done the same with
static IP addresses as well.  The only things I change for a static IP
is IPADDR, GATEWAY, NETMASK, and BOOTPROTO

If I am using WEP the entry is made in keys-wlan0

>  Thanks,
>  James
>  
>

[James Pifer]

>  As I recall, you previously had the system locking up when you did
> the
>  modprobe step.  This seems to be some progress.
>   
Yes, step in the right direction...

>  Use ndiswrapper -l to see the interface drivers and device are
> present.
>   
Yes, driver is loaded and hardware present. 

>  Have you tried using iwlist to see if the adapter finds any local
> access
>  points? It should see the access point even if it does not connect, and
>  should tell you about it. 
Sure does. 

>  
>  Other things that might interfere are mode, channel (I think 1-12, but 6
>  is usually the default for the AP), and maybe others.
>  I usually try to get the connection without encryption, then enable
>  encryption later.
>   
Yes, had not specified the channel but tried it with channel 6 which is
what my router is using. Still no luck. I was trying it with encryption
off for a while. I can try it again. 

>  My ifcfg-wlan0 is:
>   
I'll give this a shot too. 

>  IPV6INIT=no
>  ONBOOT=no
>  USERCTL=no
>  PEERDNS=yes
>  GATEWAY=
>  TYPE=Wireless
>  DEVICE=wlan0
>  HWADDR=
>  BOOTPROTO=dhcp
>  NETMASK=
>  DHCP_HOSTNAME=
>  IPADDR=
>  DOMAIN=
>  ESSID='my_essid'
>  CHANNEL=6
>  MODE=Managed
>  RATE=Auto
>  
>  That worked first time with dhcp, although I have done the same with
>  static IP addresses as well.  The only things I change for a static IP
>  is IPADDR, GATEWAY, NETMASK, and BOOTPROTO
>  
>  If I am using WEP the entry is made in keys-wlan0 
Thanks,
James

[James Pifer]

>  
>  Other things that might interfere are mode, channel (I think 1-12, but 6
>  is usually the default for the AP), and maybe others.
>  I usually try to get the connection without encryption, then enable
>  encryption later. 
Woo-hoo. It made a connection when I turned WEP off. Now the question is
what am I doing wrong with that? I know I have the key right on the
command line. I have my router setup to use 128bit WEP. When I look at
iwconfig, it does look kind of funny, because it shows the key split
into groups of 4, like abcd-wxyz-1234 etc, and it ends with just two
characters after the last dash. 

Thanks so far!

James

httpd: permission denied

[Albert A. Modderkolk]

I get the below error when the first program is executed. randbann.pl is
755 and it reads only from a file with ww read access.  Which files are
used by httpd that could cause this error or what else could cause this?

Tia, Albert

[Tue Nov 01 10:02:42 2005] [notice] Apache/2.0.54 (Fedora) configured --
resuming normal operations
[Thu Nov 03 00:59:56 2005] [error] [client 127.0.0.1] (13)Permission
denied: exec of '/catalogs/grn/cgi/randbann.pl' failed
[Thu Nov 03 00:59:56 2005] [error] [client 127.0.0.1] Premature end of
script headers: randbann.pl
[Thu Nov 03 00:59:59 2005] [error] [client 127.0.0.1] (13)Permission
denied: exec of '/catalogs/grn/cgi/order.cgi' failed, referer:
http://local.eyewearcentre.com/index.html

httpd: permission denied

[Benjamin Franz]

On Thu, 3 Nov 2005, Albert A. Modderkolk wrote:

>  I get the below error when the first program is executed. randbann.pl
> is
>  755 and it reads only from a file with ww read access.  Which files are
>  used by httpd that could cause this error or what else could cause this? 
[snip]

SELinux strikes again. Look in the file /etc/selinux/config for the 
SELinux mode setting.

You will probably need to set SELinux to 'permissive' to get your scripts 
to execute (you can also try to write a SELinux policy to permit them to 
run, but that is likely to be harder to do than you want). You will need 
to reboot after editting /etc/selinux/config to make the changed mode take 
effect.

You can also do it on a temporary basis for testing without rebooting by 
running 'setenforce 0' after using 'su -' to become root (you must do the

'su -' first or it won't work).

See http://fedora.redhat.com/docs/selinux-faq-fc3/ for full information on SELinux.

-- 
Benjamin Franz

The designer of a new kind of system must participate fully in the implementation.

                                                          - Donald E. Knuth

httpd: permission denied

[Rahul Sundaram]

Benjamin Franz wrote:

>  On Thu, 3 Nov 2005, Albert A. Modderkolk wrote:
>
> > I get the below error when the first program is executed. randbann.pl is
> > 755 and it reads only from a file with ww read access. Which files are
> > used by httpd that could cause this error or what else could cause this?
>
>
>  [snip]
>
>  SELinux strikes again. Look in the file /etc/selinux/config for the 
>  SELinux mode setting.  
No need to do this. If you suspect a SELinux related issue then post to 
the fedora-selinux list.

regards
Rahul

httpd: permission denied

[Paul Howarth]

On Thu, 2005-11-03 at 01:09 +0100, Albert A. Modderkolk wrote:
>  I get the below error when the first program is executed. randbann.pl
> is
>  755 and it reads only from a file with ww read access.  Which files are
>  used by httpd that could cause this error or what else could cause this?
>  
>  Tia, Albert
>  
>  [Tue Nov 01 10:02:42 2005] [notice] Apache/2.0.54 (Fedora) configured --
>  resuming normal operations
>  [Thu Nov 03 00:59:56 2005] [error] [client 127.0.0.1] (13)Permission
>  denied: exec of '/catalogs/grn/cgi/randbann.pl' failed
>  [Thu Nov 03 00:59:56 2005] [error] [client 127.0.0.1] Premature end of
>  script headers: randbann.pl
>  [Thu Nov 03 00:59:59 2005] [error] [client 127.0.0.1] (13)Permission
>  denied: exec of '/catalogs/grn/cgi/order.cgi' failed, referer:
>  http://local.eyewearcentre.com/index.html 
Try:
# chcon -R -t httpd_sys_script_exec_t /catalogs/grn/cgi

Paul.
-- 
Paul Howarth <paul(a)city-fan.org&gt;

[Josh Coffman]

--- James Pifer <jep(a)obrien-pifer.com&gt; wrote:

>  
>  > 
>  > Other things that might interfere are mode,
>  channel (I think 1-12, but 6
>  > is usually the default for the AP), and maybe
>  others.
>  > I usually try to get the connection without
>  encryption, then enable
>  > encryption later.
>  
>  Woo-hoo. It made a connection when I turned WEP off.
>  Now the question is
>  what am I doing wrong with that? I know I have the
>  key right on the
>  command line. I have my router setup to use 128bit
>  WEP. When I look at
>  iwconfig, it does look kind of funny, because it
>  shows the key split
>  into groups of 4, like abcd-wxyz-1234 etc, and it
>  ends with just two
>  characters after the last dash. 
>  
>  Thanks so far!
>  
>  James
>   
one thing I forget about WEP is putting the "0x"
before the hex string. did you do that for wep
connection?



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

[James Pifer]

>  one thing I forget about WEP is putting the "0x"
>  before the hex string. did you do that for wep
>  connection?
>   
Oops, no I didn't. That hopefully will do it. Thanks!

[James Pifer]

>  
>  one thing I forget about WEP is putting the "0x"
>  before the hex string. did you do that for wep
>  connection?
>  
>   
When I tried that I got an error that said:
Error for wireless request "Set Encode" (8B2A) :
    invalid argument "0x[my key was here]".

I also tried creating a keys-wlan0 file under:
/etc/sysconfig/networking/devices

The only thing in the file was:
KEY=0x[my key here]

That didn't seem to work either. Can anyone elaborate on the keys-wlan0
file? I'll do some googling. 

Thanks,
James

[Jeff Vian]

On Wed, 2005-11-02 at 22:24 -0500, James Pifer wrote:
>  > 
>  > one thing I forget about WEP is putting the "0x"
>  > before the hex string. did you do that for wep
>  > connection?
>  > 
>  > 
>  
>  When I tried that I got an error that said:
>  Error for wireless request "Set Encode" (8B2A) :
>      invalid argument "0x[my key was here]".
>  
>  I also tried creating a keys-wlan0 file under:
>  /etc/sysconfig/networking/devices
>  
>  The only thing in the file was:
>  KEY=0x[my key here]
>  
>  That didn't seem to work either. Can anyone elaborate on the keys-wlan0
>  file? I'll do some googling. 
>   
You CANNOT use the 0x there.
the file should contain a line KEY='my_key_here' with the exact
displayed value from the AP in the field above.
IIRC the 128 bit key is something like 28 hex characters, but does not
contain spaces, - signs, etc.  
Copy and paste from the displayed value in the AP and it should work

It does for me, with my linksys AP.
  
>  Thanks,
>  James
>

[Josh Coffman]

--- Jeff Vian <jvian10(a)charter.net&gt; wrote:

>  On Wed, 2005-11-02 at 22:24 -0500, James Pifer
>  wrote:
>  > > 
>  > > one thing I forget about WEP is putting the "0x"
>  > > before the hex string. did you do that for wep
>  > > connection?
>  > > 
>  > > 
>  > 
>  > When I tried that I got an error that said:
>  > Error for wireless request "Set Encode" (8B2A) :
>  >     invalid argument "0x[my key was here]".
>  > 
>  > I also tried creating a keys-wlan0 file under:
>  > /etc/sysconfig/networking/devices
>  > 
>  > The only thing in the file was:
>  > KEY=0x[my key here]
>  > 
>  > That didn't seem to work either. Can anyone
>  elaborate on the keys-wlan0
>  > file? I'll do some googling. 
>  > 
>  You CANNOT use the 0x there.
>  the file should contain a line KEY='my_key_here'
>  with the exact
>  displayed value from the AP in the field above.
>  IIRC the 128 bit key is something like 28 hex
>  characters, but does not
>  contain spaces, - signs, etc.  
>  Copy and paste from the displayed value in the AP
>  and it should work
>  
>  It does for me, with my linksys AP.
>    
>  > Thanks,
>  > James
>  > 
>   
sry. should have said was for the applet. 


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

[Jeff Vian]

On Wed, 2005-11-02 at 22:24 -0500, James Pifer wrote:
>  > 
>  > one thing I forget about WEP is putting the "0x"
>  > before the hex string. did you do that for wep
>  > connection?
>  > 
>  > 
>  
>  When I tried that I got an error that said:
>  Error for wireless request "Set Encode" (8B2A) :
>      invalid argument "0x[my key was here]".
>  
>  I also tried creating a keys-wlan0 file under:
>  /etc/sysconfig/networking/devices
>  
>  The only thing in the file was:
>  KEY=0x[my key here]
>  
>  That didn't seem to work either. Can anyone elaborate on the keys-wlan0
>  file? I'll do some googling. 
>   
BTW, iwconfig and the ifup scripts know the key value is in hex, so it
needs to be exact, not with the preceding "0x" when it is entered.

>  Thanks,
>  James
>

[James Pifer]

>  one thing I forget about WEP is putting the "0x"
>  before the hex string. did you do that for wep
>  connection?
>  
>  
>   
Boy, still no luck with encryption. I've tried doing it on the command
line, through the Network config applet, using the keys-wlan0, still it
keeps failing to make a connection. 

Also, another question. I have a device out there called wifi0. Does
ndiswrapper include this device? I was playing with madwifi that uses
wifi0. I'm just wondering if I should try and remove it or leave it.
Right now it seems to be tied to wlan0. Wondering if it's causing some
of my problems with encryption. 

Thanks,
James

[Jeff Vian]

On Thu, 2005-11-03 at 08:23 -0500, James Pifer wrote:
>  > one thing I forget about WEP is putting the "0x"
>  > before the hex string. did you do that for wep
>  > connection?
>  > 
>  > 
>  > 
>  
>  Boy, still no luck with encryption. I've tried doing it on the command
>  line, through the Network config applet, using the keys-wlan0, still it
>  keeps failing to make a connection. 
>  
>  Also, another question. I have a device out there called wifi0. Does
>  ndiswrapper include this device? I was playing with madwifi that uses
>  wifi0. I'm just wondering if I should try and remove it or leave it.
>  Right now it seems to be tied to wlan0. Wondering if it's causing some
>  of my problems with encryption. 
>   
What do you mean by 'tied to wlan0'?  Does assigning the ip address to
wlan0 also assign an address to wifi0?  or something else?

If both are trying to handle the same physical device then certainly you
should remove the one you are not using.  That will remove the
possibility of interference.  I don't believe the madwifi driver is able
to handle the broadcom chipset you have.

>  Thanks,
>  James
>

[James Pifer]

>   
>  > 
>  What do you mean by 'tied to wlan0'?  Does assigning the ip address to
>  wlan0 also assign an address to wifi0?  or something else?
>  
>  If both are trying to handle the same physical device then certainly you
>  should remove the one you are not using.  That will remove the
>  possibility of interference.  I don't believe the madwifi driver is able
>  to handle the broadcom chipset you have. 
Yeah, I have a DWL-G650 I was trying to use with madwifi. 

Hard to explain the wifi0 thing. In the Network applet there are two
things listed for wireless:
Device	Nickname
wlan0	wlan0
wlan0	wifi0

Thing is, if I deactivate one, they both deactivate. That's what I meant
by tied somehow. I'll try and clean that up, although I don't think that
is affecting the wep stuff.

Yes, I took the web key directly from my router's admin page and pasted
it into the file and also on the command line. I'll keep playing with it
after getting rid of wifi0 somehow.

Thanks,
James

[Josh Coffman]

--- James Pifer <jep(a)obrien-pifer.com&gt; wrote:

>  Hard to explain the wifi0 thing. In the Network
>  applet there are two
>  things listed for wireless:
>  Device	Nickname
>  wlan0	wlan0
>  wlan0	wifi0
>   
just a guess but... could't you just remove the entry
for wifi0 in the applet?


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

[Jeff Vian]

On Wed, 2005-11-02 at 19:45 -0500, James Pifer wrote:
>  > 
>  > Other things that might interfere are mode, channel (I think 1-12, but 6
>  > is usually the default for the AP), and maybe others.
>  > I usually try to get the connection without encryption, then enable
>  > encryption later.
>  
>  Woo-hoo. It made a connection when I turned WEP off. Now the question is
>  what am I doing wrong with that? I know I have the key right on the
>  command line. I have my router setup to use 128bit WEP. When I look at
>  iwconfig, it does look kind of funny, because it shows the key split
>  into groups of 4, like abcd-wxyz-1234 etc, and it ends with just two
>  characters after the last dash. 
>   
The key entry in keys-wlan0 should be like
	KEY='the_entire_key_here'

the key must be exactly as displayed in the AP with no abcd-efgh-  type
structure.  It is case sensitive and must be the exact number of
characters (yes, the - is a character).  I use copy/paste with my web
browser interface to the AP to capture it and put it into the
configuration file for the adapter.

>  Thanks so far!
>  
>  James
>

[James Pifer]

>  The key entry in keys-wlan0 should be like
>  	KEY='the_entire_key_here'
>  
>  the key must be exactly as displayed in the AP with no abcd-efgh-  type
>  structure.  It is case sensitive and must be the exact number of
>  characters (yes, the - is a character).  I use copy/paste with my web
>  browser interface to the AP to capture it and put it into the
>  configuration file for the adapter.
>   
At this point I don't know what to say. I know I'm doing this
correctly. 
-My key in my AP's configuration has 26 characters. 
-It will only allow me to use upper case.
-I've directly copied and pasted the key.
-FC4's network applet will also only use upper case.
	-entered with 0x in front
-FC4's network applet correctly updates keys-wlan0.
	-file has KEY=[the key] WITHOUT the 0x
-My router id a DLink DI624

Is there any type of ndiswrapper debugging that can be turned on? 
I know the key works since I have a windows machine connected using the
same key. I've also tried changing the key to something else.

It's works great without encryption, and even though wep kind of sucks,
it's at least not wide open. Sorry to those of you that are helping but
getting frustrated. I'm right there with you. 

Thanks,
James

[Josh Coffman]

--- James Pifer <jep(a)obrien-pifer.com&gt; wrote:

>  > The key entry in keys-wlan0 should be like
>  > 	KEY='the_entire_key_here'
>  > 
>  > the key must be exactly as displayed in the AP
>  with no abcd-efgh-  type
>  > structure.  It is case sensitive and must be the
>  exact number of
>  > characters (yes, the - is a character).  I use
>  copy/paste with my web
>  > browser interface to the AP to capture it and put
>  it into the
>  > configuration file for the adapter.
>  > 
>  
>  At this point I don't know what to say. I know I'm
>  doing this
>  correctly. 
>  -My key in my AP's configuration has 26 characters. 
>  -It will only allow me to use upper case.
>  -I've directly copied and pasted the key.
>  -FC4's network applet will also only use upper case.
>  	-entered with 0x in front
>  -FC4's network applet correctly updates keys-wlan0.
>  	-file has KEY=[the key] WITHOUT the 0x
>  -My router id a DLink DI624
>  
>  Is there any type of ndiswrapper debugging that can
>  be turned on? 
>  I know the key works since I have a windows machine
>  connected using the
>  same key. I've also tried changing the key to
>  something else. 
I've been there before myself: non-wep worked, wep
didn't. Completely understand.

>  
>  It's works great without encryption, and even though
>  wep kind of sucks,
>  it's at least not wide open. Sorry to those of you
>  that are helping but
>  getting frustrated. I'm right there with you. 
>  
>  Thanks,
>  James 
Just to check this off the list... did non-wep work
with the mac filter on? If the mac filter on when
trying to connect with wep?

Did you get rid of the wifi0 device/connection?

When I was at the same point, I set all the settings
using the applet. made sure all net connections where
disconnected. and checked iwconfig wlan0 to make sure
the settings had been saved by the applet. then
rebooted without any connection auto connecting.

I then opened the net applet and used the connect
button to get a wep connection to my AP. eventually I
got it, even with the default 4k kernel.

start elminating things you know are fine... you know
that:

-ndiswrapper is installed and working cause non-wep
works
-you have the right windows driver cause non-wep works
-the 16k kernel is working cause non-wep works
-static ip works cause...
-?




		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

[James Pifer]

>  Just to check this off the list... did non-wep work
>  with the mac filter on? If the mac filter on when
>  trying to connect with wep?
>   
Yes, non-wep is working with the MAC filter enabled. 

>  Did you get rid of the wifi0 device/connection? 
Yes, got rid of the wifi0 junk. 

>  
>  When I was at the same point, I set all the settings
>  using the applet. made sure all net connections where
>  disconnected. and checked iwconfig wlan0 to make sure
>  the settings had been saved by the applet. then
>  rebooted without any connection auto connecting.
>  
>  I then opened the net applet and used the connect
>  button to get a wep connection to my AP. eventually I
>  got it, even with the default 4k kernel.
>   
Tried this as well. Nothing Active on boot. Reboot, modprobe
ndiswrapper, and then activiate the wireless device with wep. No go. 

>  start elminating things you know are fine... you know
>  that:
>  
>  -ndiswrapper is installed and working cause non-wep
>  works
>  -you have the right windows driver cause non-wep works
>  -the 16k kernel is working cause non-wep works
>  -static ip works cause...
>  -? 
-16K kernel works non-wep. Was locking machine with 4k kernel
-Static ip address worked in non-wep. 

Honestly not sure what else to check. I've tried so many iterations.
Sometimes I get to the point where ndiswrapper gets totally hosed with
starting and stopping wireless, that I've had to hard reset my laptop.
Maybe that's partly a lack of patience, but rmmod ndiswrapper, with the
device inactive, just hangs. 

Thanks,
James

[Rick Stevens]

On Fri, 2005-11-04 at 10:28 -0500, James Pifer wrote:
>  > The key entry in keys-wlan0 should be like
>  > 	KEY='the_entire_key_here'
>  > 
>  > the key must be exactly as displayed in the AP with no abcd-efgh-  type
>  > structure.  It is case sensitive and must be the exact number of
>  > characters (yes, the - is a character).  I use copy/paste with my web
>  > browser interface to the AP to capture it and put it into the
>  > configuration file for the adapter.
>  > 
>  
>  At this point I don't know what to say. I know I'm doing this
>  correctly. 
>  -My key in my AP's configuration has 26 characters. 
Then you're using a hex key, not an ASCII one.
 
>  -It will only allow me to use upper case. 
Again, it's hex, not ASCII.

>  -I've directly copied and pasted the key.
>  -FC4's network applet will also only use upper case.
>  	-entered with 0x in front
>  -FC4's network applet correctly updates keys-wlan0.
>  	-file has KEY=[the key] WITHOUT the 0x 
That won't work.  If you're using a hex key, you MUST have "0x" in
front of it in your keys.

>  -My router id a DLink DI624
>  
>  Is there any type of ndiswrapper debugging that can be turned on? 
>  I know the key works since I have a windows machine connected using the
>  same key. I've also tried changing the key to something else.
>  
>  It's works great without encryption, and even though wep kind of sucks,
>  it's at least not wide open. Sorry to those of you that are helping but
>  getting frustrated. I'm right there with you.  
I don't have any issues.  A 26-character key is hex.  If you want to
use ASCII, you have to tell your DI624 that, and the key will be 13
ASCII characters (and you can use mixed case).  Your key on the system
must match (no leading "0x" for ASCII).  Oh, and when you change the
key on the DI624, you must reboot it.

If you're using hex, then it's 26 HEX characters.  The clickbox on the
DI624 for hex keys MUST be set on, and you must restart the DI624.  On
the system, and you MUST have the "0x" in front of the key in your key
file.

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens(a)vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-        Brain:  The organ with which we think that we think.        -
----------------------------------------------------------------------

[James Pifer]

>  > -I've directly copied and pasted the key.
>  > -FC4's network applet will also only use upper case.
>  > 	-entered with 0x in front
>  > -FC4's network applet correctly updates keys-wlan0.
>  > 	-file has KEY=[the key] WITHOUT the 0x
>  
>  That won't work.  If you're using a hex key, you MUST have "0x" in
>  front of it in your keys.
>   
I do not agree. In the keys-wlan0 file you cannot have the 0x in front.
You only enter the 0x in the Network applet. If you have the 0x in the
file you cannot even start the device correctly. At least that's what I
get.

>  I don't have any issues.  A 26-character key is hex.  If you want
> to
>  use ASCII, you have to tell your DI624 that, and the key will be 13
>  ASCII characters (and you can use mixed case).  Your key on the system
>  must match (no leading "0x" for ASCII).  Oh, and when you change the
>  key on the DI624, you must reboot it.
>   
I never said I wanted to use ASCII. Someone else on a previous response
said to make sure case was the same. Either way, I did try ASCII, after
reconfiguring the router, and got the same results. It still will not
connect. 

>  If you're using hex, then it's 26 HEX characters.  The
> clickbox on the
>  DI624 for hex keys MUST be set on, and you must restart the DI624.  On
>  the system, and you MUST have the "0x" in front of the key in your key
>  file.

[Jeff Vian]

On Fri, 2005-11-04 at 10:00 -0800, Rick Stevens wrote:
>  On Fri, 2005-11-04 at 10:28 -0500, James Pifer wrote:
>  > > The key entry in keys-wlan0 should be like
>  > > 	KEY='the_entire_key_here'
>  > > 
>  > > the key must be exactly as displayed in the AP with no abcd-efgh-  type
>  > > structure.  It is case sensitive and must be the exact number of
>  > > characters (yes, the - is a character).  I use copy/paste with my web
>  > > browser interface to the AP to capture it and put it into the
>  > > configuration file for the adapter.
>  > > 
>  > 
>  > At this point I don't know what to say. I know I'm doing this
>  > correctly. 
>  > -My key in my AP's configuration has 26 characters.
>  
>  Then you're using a hex key, not an ASCII one.
>   
>  > -It will only allow me to use upper case.
>  
>  Again, it's hex, not ASCII.
>  
>  > -I've directly copied and pasted the key.
>  > -FC4's network applet will also only use upper case.
>  > 	-entered with 0x in front
>  > -FC4's network applet correctly updates keys-wlan0.
>  > 	-file has KEY=[the key] WITHOUT the 0x
>  
>  That won't work.  If you're using a hex key, you MUST have "0x" in
>  front of it in your keys.
>   
If you have the references to tell us where the requirement to use the
0x notation is documented I would appreciate it.

At no time in my experience have I ever needed that notation and James
experience that he has listed here at least twice reinforces that. 

Neither iwconfig nor the keys-wlan0 file will work with the 0x notation.

>  > -My router id a DLink DI624
>  > 
>  > Is there any type of ndiswrapper debugging that can be turned on? 
>  > I know the key works since I have a windows machine connected using the
>  > same key. I've also tried changing the key to something else.
>  > 
>  > It's works great without encryption, and even though wep kind of sucks,
>  > it's at least not wide open. Sorry to those of you that are helping but
>  > getting frustrated. I'm right there with you. 
>  
>  I don't have any issues.  A 26-character key is hex.  If you want to
>  use ASCII, you have to tell your DI624 that, and the key will be 13
>  ASCII characters (and you can use mixed case).  Your key on the system
>  must match (no leading "0x" for ASCII).  Oh, and when you change the
>  key on the DI624, you must reboot it.
>  
>  If you're using hex, then it's 26 HEX characters.  The clickbox on the
>  DI624 for hex keys MUST be set on, and you must restart the DI624.  On
>  the system, and you MUST have the "0x" in front of the key in your key
>  file.
>  
>  ----------------------------------------------------------------------
>  - Rick Stevens, Senior Systems Engineer     rstevens(a)vitalstream.com -
>  - VitalStream, Inc.                       http://www.vitalstream.com -
>  -                                                                    -
>  -        Brain:  The organ with which we think that we think.        -
>  ----------------------------------------------------------------------
>