#7825 BLOC 8.2.0 (: can't complete WPA handshake with D-Link WBR-2310

[Zarro Boogs per Child]

#7825: can't complete WPA handshake with D-Link WBR-2310
------------------------+---------------------------------------------------
   Reporter:  dsd       |       Owner:  jcardona            
       Type:  defect    |      Status:  assigned            
   Priority:  blocker   |   Milestone:  8.2.0 (was Update.2)
  Component:  wireless  |     Version:  not specified       
 Resolution:            |    Keywords:  8.2.0:? relnote     
Next_action:  review    |    Verified:  1                   
  Blockedby:            |    Blocking:                      
------------------------+---------------------------------------------------

Comment(by carrano):

 Replying to [comment:37 jcardona]:
 >
 > This debug messasage:
 >
 > {{{
 > [ 1514.831250] libertas assoc: Association Request:
 > [ 1514.831261]     flags:     0x00000770
 > [ 1514.831271]     SSID:      'zocos'
 > [ 1514.831279]     chann:     11
 > [ 1514.831288]     band:      0
 > [ 1514.831296]     mode:      2
 > [ 1514.831304]     BSSID:     00:00:00:00:00:00
 > [ 1514.831314]     secinfo:
 > [ 1514.831322]     auth_mode: 1
 > }}}
 >
 > is generated when the WPA key is installed.  No association request is
 transmitted when that happens.  (I'll prepare a patch to omit this debug
 message in this situation)

 Yes, I confirm the following:

 What I was investigating were these void attempts to associate as
 registered in:
 {{{
 [ 4625.171741] libertas assoc: Association Request:
 [ 4625.171754]     flags:     0x00000752
 [ 4625.171763]     SSID:      '<hidden>'
 [ 4625.171773]     chann:     6
 [ 4625.171781]     band:      0
 [ 4625.171789]     mode:      2
 [ 4625.171798]     BSSID:     00:00:00:00:00:00
 [ 4625.171808]     secinfo:
 [ 4625.171816]     auth_mode: 1
 }}}

 These attemps to not generate equivalent assoc request frames.

 For the record, a test was performed with no NM or GUI (using
 wpa_supplicant on the
 command line):

 While observing the sniffer and the XO, I noticed the following timeline:

 1. I start the wpa_supplicant,

 2. the sniffer shows nothing while XO reports
 ioctl[SIOCGIWSCAN]:Resource temporary unavailable" 6 times

 3. dmesg registers:

 {{{
 [ 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
 }}}

 4. a assoc req frame is finally detected (and it is correctly formed).

 5. assoc completes on the XO ("CTRL-EVENT-CONNECTED").

 6. dmesg registers:
 {{{
 [ 8066.351088] libertas assoc: Association Request:
 [ 8066.351088]     flags:     0x00000c36
 [ 8066.351088]     SSID:      'Harumaki'
 [ 8066.351088]     chann:     6
 [ 8066.351088]     band:      0
 [ 8066.351088]     mode:      2
 [ 8066.351088]     BSSID:     00:14:6c:df:aa:00
 [ 8066.351088]     secinfo:   WPA
 [ 8066.351088]     auth_mode: 1
 [ 8066.351089] libertas scan: is_network_compatible() WPA: wpa_ie 0xdd
 wpa2_ie 0x0 WEP d WPA e WPA2 d privacy 0x10
 [ 8066.351089] libertas assoc: ASSOC_CMD: num rates 12
 [ 8066.351089] libertas assoc: ASSOC_CMD: capability 0x0431
 [ 8066.396652] libertas assoc: ASSOC_RESP: mac_control is 0x23
 [ 8066.396747] libertas assoc: ASSOC: lbs_associate(bssid) returned 0
 [ 8066.396781] libertas assoc: ASSOC: associated to 'Harumaki',
 00:14:6c:df:aa:00
 }}}

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