Hi.

leo wrote:
 > Jul 19 14:41:24 localhost kernel: ath0: association failed (reason 1)
 > for 00:20:e0:02:cb:81
 > Does anyone know what (reason 1) is? Is there anyway around this?

The answer for your question could be found by searching in the list's 
archives:

=== cut ===
You can try to disable WME. I had a similar problem with dlink cards and
accesspoint and got the same error message ("ath0: association failed
(reason 1) for...").

Run the folowing command and then compile again.
bash% export COPTS="$COPTS -DNO_WME"

I don't know if it solves your problem but it's worth a try.
=== cut ===
ref: http://thread.gmane.org/gmane.linux.drivers.madwifi.user/3437
(last post in this thread)

=== cut ===
Two common reasons for association failure:
1. the AP is configured to have 22 Mbps as a mandatory supported rate.
    That rate is not commonly available and thus associations fail unless
    the AP is reconfigured.
2. the Madwifi driver includes the WME information element in its
    association request. The AP does not ignore it (as it should) and
    fails the association.
    The only fix in this case is to disable sending the WME info element.
    In cvs HEAD this is done by compiling with NO_WME. In the next stable
    release that merges WME and WPA, this can be done with a sysctl.
=== cut ===
ref: http://thread.gmane.org/gmane.linux.drivers.madwifi.user/3311
(quoted Greg Chesson in this thread, but the other postings also contain 
some useful information)

hth.

Bye, Mike

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click