help: association failure

[Ronak Chokshi]

Marcelo / Jim / Dan,
The failure codes (3 and 4) that you are seeing are, in fact, associated
to one of the IEEE 802.11 failure codes that you listed in your email
below. The Marvell firmware actually maps them to numbers 1 - 4
according to the table below before sending the Assoc Command Response
to the host.

Status Code Mapping for Association Response currently implemented in
FW:

IEEE Status Code 		Marvell Status Code
0 			-> 	0x0000 ASSOC_RESULT_SUCCESS
13 			-> 	0x0004 ASSOC_RESULT_AUTH_REFUSED
14 			-> 	0x0004 ASSOC_RESULT_AUTH_REFUSED
15 			-> 	0x0004 ASSOC_RESULT_AUTH_REFUSED
16 			-> 	0x0004 ASSOC_RESULT_AUTH_REFUSED
others 		-> 	0x0003 ASSOC_RESULT_REFUSED
------------------------------------------------------------

0x0001 ASSOC_RESULT_INVALID_PARAMETERS
- Currently not used

0x0002 ASSOC_RESULT_TIMEOUT
- Internal Timer expired
for waiting Assoc Rsp from AP

This has been a very old code and is definitely not the right thing to
do. But we have already correctly this (i.e. the host gets to know the
actual status code that we get from the Association response frame from
the AP) in our later versions of the firmware for other products. I am
trying to correct this in the firmware scheduled to be sent to OLPC
later this month.

Thanks
Ronak

-----Original Message-----
From: Marcelo Tosatti [mailto:marcelo at kvack.org] 
Sent: Friday, December 01, 2006 4:57 PM
To: Dan Williams
Cc: javier at cozybit.com; Marcelo Tosatti; Ronak Chokshi; Luis Carlos Cobo
Rus; Alan Cunningham; libertas-dev at lists.infradead.org
Subject: Re: help: association failure

On Fri, Dec 01, 2006 at 10:40:41AM -0500, Dan Williams wrote:
> On Thu, 2006-11-30 at 21:27 -0800, Javier Cardona wrote:
> > Hi Marcelo,
> > 
> > We'll try to reproduce this in the office tomorrow.  But before we
try
> > that, can you tell us what version of FW and driver are you running?
> > Could you provide the output of ethtool -i ethX?
> 
> I've also gotten an assoc failure code of '2' at various times.  We're
> using pretty old Orinoco-based APs here at the OLPC office, not sure
if
> that has anything to do with it.

The issue appears to happen on low quality links. For some reason the
AP rejects such association requests. Having the board closer to the AP
makes it all work.

Strange thing is that the ipw2200 associates happily on poor quality
links.

Need further investigation, we're lacking details.