[Trac #857] wireless association failure cases

[Zarro Boogs per Child]

#857: wireless association failure cases
----------------------+-----------------------------------------------------
 Reporter:  marcelo   |       Owner:  marcelo
     Type:  defect    |      Status:  new    
 Priority:  high      |   Milestone:  BTest-3
Component:  wireless  |    Keywords:         
----------------------+-----------------------------------------------------
 Lilian mentions that RA set to 00:00:00:00 is the reason for some AP's
 refusing
 to associate. This might be the reason for the association failure cases
 reported at

 http://lists.infradead.org/pipermail/libertas-
 dev/2006-December/000156.html

 {{{
 2.  The issue is with CMD_GET_HW_SPEC.  Whenever I issue that command to
 the
 Marvel firmware, it returns 0s as mac address and it really zeroes out the
 reasonable mac address.

 3.  When my Dlink refuses to associate, that was because I issued the
 CMD_GET_HW_SPEC command.  And sniffing on the air confirms that the RA was
 0.

 4.  Now that I don't do CMD_GET_HW_SPEC anymore, sniffing on the air
 confirms that the RA is the reasonable mac address.  AND, I can associate
 with the Dlink now.  Actually, I can send ethernet packets in and out of
 the
 Dlink AP (sniffed on the air and tcpdump on the wired side).

 So, my main concern is CMD_GET_HW_SPEC.  I noticed that the linux driver
 issues one immediately after downloading the firmware and is expecting to
 get a valid mac address from the response.  That makes me rather nervous.
 That's all.
 }}}

 Need to confirm that the libertas driver is operating the firmware
 correctly
 and investigate these failures.

-- 
Ticket URL: <http://dev.laptop.org/ticket/857>
One Laptop Per Child <http://laptop.org/>