> Hello, I've been using the madwifi driver with an Atheros
> Communications, Inc. AR5212 802.11abg=20
> NIC (rev 01) for a while now. When I first saw the new madwifi-ng quite
> a few months ago and tried it, I was not able to get it working. It
> apparently failed to obtain a DHCP lease or else had a problem
> associating with the AP. I ended up reverting to the working, older
> driver. Since then I've tried the ng driver several times and always
> the same problem. Just wondering if this is fixed yet or if anyone is
> aware of the problem?
Depends on what the problem in your case is. If its the problem
described in ticket #154 (http://madwifi.org/ticket/154): I fixed=20
this problem today, so it should work. If it doesn't work, please post a
detailed problem description.
"There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence." Jeremy S. Anderson