Re: [Madwifi-users] Status update of madwifi

[Richard S. <ma...@ri...>]

Hi,

> 1. How hard is it to make these drivers "just work"? If I downloaded
> madwifi-20030702 and attenpted to make it work with any bit of hardware
> supported by this,how much keyboard bashing would be required to set
> things up?

Well, I use the drivers on a Trustix machine that is supposed to become an=
=20
access point with a D-Link XTremeG PCI Card and setting this thing up was a=
=20
matter of writing a little script with a few modprobes, a few brctrls (Brid=
ge=20
with firewall) and one iwconfig line. I don't use WEP though since it's=20
supposed to become a captive portal.

My client is a Mandrake 9.1 laptop with the equivalent D-Link PCMCIA card=20
which loads the drivers just fine after plugging in the card. It only tries=
=20
to setup eth1 instead of ath0. Didn't look at the scripts but I guess it's =
an=20
easy fix.

>
> 2. How difficult is it to integrate these drivers into the Shrike
> pcmcia-cs, hotplug and network subsystems?

see above for part of the answer. What is Shrike?

> 3. Does the driver work better/have better performance/complain less with
> different implementations of its supported hardware?=20

I wouldn't know. Some modes seem to work fine, some not so fine. It definat=
ely=20
is work in progress but if you don't need top speed and top distances betwe=
en=20
the cards, it's already very usable (at least for my purposes with only two=
=20
machines).

> Specifically, I plan
> to purchase a Linksys WPC55AG, which contains the Atheros AR5001X+ tri-mo=
de
> chipset.=20

My D-Links are a/b/g, too. I don't know your card.

> and fill the syslog with rubbish?

Actually the driver is nice and quiet. There is some debugging options thou=
gh=20
that i didn't try yet.

Hope that helped a little,

Richard