Problems making WPA work with ndiswrapper/broadcom
Donald Teed
dteed
Wed Aug 18 04:08:17 PDT 2004
Yes, now that I'm getting this close, I've started launching
dhcpcd just before wpa_supplicant, on wlan0. I'm using
slackware 9 in this test.
I'll get back about the AP model later today, and I'll try
a longer time out on authentication.
I'm using ndiswrapper 0.9 - the first to support WPA
as far as I'm aware. Hmmm, there is a .10 pre-release now.
Maybe I'll try it.
One thing worth noting is that the broadcom wireless ethernet
is out in a few different revisions and I'm using rev 3.
There is no difference in the lspci -n output between that
and rev 2 (I have another very similar Dell D600).
We have seen some differences in the system stability when
ndiswrapper 0.8 was used on the two machines. The rev 3
machine would lock up when booting with no AC power and
loading ndiswrapper, and also when using the winmoodem
(which I believe shares the same mini-PCI part).
The same tests (with the disk moved to the older machine)
were done on the machine with rev 2 chipset and no lockups occurred
in these situations. Unfortunately we have 4494 machines
with the rev 3 broadcom wireless, and 6 with the rev 2.
Again, this is using:
02:03.0 Network controller: Broadcom Corporation: Unknown device 4320 (rev 03)
Subsystem: Dell Computer Corporation: Unknown device 0003
Flags: bus master, fast devsel, latency 32, IRQ 7
Memory at fafee000 (32-bit, non-prefetchable) [size=8K]
02:03.0 Class 0280: 14e4:4320 (rev 03)
--Donald Teed
On Wed, 18 Aug 2004, Giridhar Pemmasani wrote:
>
> You need to start dhclient/dhcpcd/pump (or whatever tool you use to
> configure your interface) at the same time. Are you starting it?
>
> --
> Giri
>
>
More information about the Hostap
mailing list