#8672 LOW Not Tri: Misleading association request output

[Zarro Boogs per Child]

#8672: Misleading association request output
----------------------+-----------------------------------------------------
 Reporter:  carrano   |         Owner:  jcardona     
     Type:  defect    |        Status:  new          
 Priority:  low       |     Milestone:  Not Triaged  
Component:  wireless  |       Version:  not specified
 Keywords:            |   Next_action:  never set    
 Verified:  0         |     Blockedby:               
 Blocking:            |  
----------------------+-----------------------------------------------------
 Turning on the assoc flag (0x100) in lbs_debug, will output association
 related messages to the kernel ring buffer.

 As explained by Javier, the entry flags contains a bit mask that tells the
 association thread what to do, as the example bellow:

 {{{
 flags:     0x00000f76
 }}}

 An actual association request will only be generated if bit 1 (0x2) or bit
 5 (0x20) are set, meaning that a new BSSID or an SSID have been
 configured.  When the association thread is invoked with (flags & 0x22) ==
 0, other tasks are executed, like disabling WEP keys or WPA.

 For these other tasks the correspondent association block (as exemplified
 bellow) will bring bogus information:

 {{{
 [ 8062.259465] ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 8063.289970] libertas assoc: Association Request:
 [ 8063.289983]     flags:     0x00000750
 [ 8063.289992]     SSID:      '<hidden>'
 [ 8063.290001]     chann:     6
 [ 8063.290010]     band:      0
 [ 8063.290018]     mode:      2
 [ 8063.290026]     BSSID:     00:00:00:00:00:00
 [ 8063.290036]     secinfo:
 [ 8063.290044]     auth_mode: 1
 }}}

-- 
Ticket URL: <http://dev.laptop.org/ticket/8672>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system