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

Zarro Boogs per Child bugtracker at laptop.org
Mon Sep 8 20:28:19 EDT 2008


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

Comment(by jcardona):

 We were able to replicate on joyride-2346.

  1. Configure the WBR-2310 security as WPA-Personal, TKIP+PSK
  2. On the xo, associate with wpa_supplicant
  3. Observe that wpa_status never transitions into the 'COMPLETED' state:

 {{{
 # while true; do wpa_cli status | grep state; sleep 1; done
 wpa_state=SCANNING
 wpa_state=SCANNING
 wpa_state=ASSOCIATING
 wpa_state=ASSOCIATING
 wpa_state=ASSOCIATED
 wpa_state=ASSOCIATED
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=SCANNING
 wpa_state=SCANNING
 wpa_state=ASSOCIATING
 wpa_state=ASSOCIATED
 wpa_state=ASSOCIATED
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 wpa_state=GROUP_HANDSHAKE
 }}}

 We were unable to capture the EAPOL-GTK with our sniffer and so cannot
 confirm dsd's hypothesis.
 But we could pass encrypted unicast traffic to the AP which confirms that
 the PTK was properly installed.  Unicast traffic is interrupted
 periodically when wpa_supplicant restarts the wpa_state machine:

 {{{
 64 bytes from 192.168.4.1: icmp_seq=8 ttl=127 time=2.35 ms
 64 bytes from 192.168.4.1: icmp_seq=9 ttl=127 time=2.31 ms
 64 bytes from 192.168.4.1: icmp_seq=10 ttl=127 time=2.50 ms
 64 bytes from 192.168.4.1: icmp_seq=11 ttl=127 time=2.45 ms
 64 bytes from 192.168.4.1: icmp_seq=12 ttl=127 time=2.39 ms
 64 bytes from 192.168.4.1: icmp_seq=13 ttl=127 time=4.31 ms
 64 bytes from 192.168.4.1: icmp_seq=14 ttl=127 time=2.88 ms
 64 bytes from 192.168.4.1: icmp_seq=15 ttl=127 time=2.27 ms
 64 bytes from 192.168.4.1: icmp_seq=16 ttl=127 time=2.39 ms
 64 bytes from 192.168.4.1: icmp_seq=17 ttl=127 time=2.38 ms
 64 bytes from 192.168.4.1: icmp_seq=23 ttl=127 time=2.29 ms
 ....................................^^.....................
 64 bytes from 192.168.4.1: icmp_seq=24 ttl=127 time=2.26 ms
 64 bytes from 192.168.4.1: icmp_seq=25 ttl=127 time=2.34 ms
 64 bytes from 192.168.4.1: icmp_seq=26 ttl=127 time=2.66 ms
 64 bytes from 192.168.4.1: icmp_seq=27 ttl=127 time=21.8 ms
 64 bytes from 192.168.4.1: icmp_seq=28 ttl=127 time=3.50 ms
 64 bytes from 192.168.4.1: icmp_seq=29 ttl=127 time=2.24 ms
 64 bytes from 192.168.4.1: icmp_seq=30 ttl=127 time=2.32 ms
 64 bytes from 192.168.4.1: icmp_seq=31 ttl=127 time=2.35 ms
 64 bytes from 192.168.4.1: icmp_seq=32 ttl=127 time=2.33 ms
 64 bytes from 192.168.4.1: icmp_seq=39 ttl=127 time=3.46 ms
 ....................................^^.....................
 64 bytes from 192.168.4.1: icmp_seq=40 ttl=127 time=3.25 ms
 64 bytes from 192.168.4.1: icmp_seq=41 ttl=127 time=3.03 ms
 64 bytes from 192.168.4.1: icmp_seq=42 ttl=127 time=2.46 ms
 64 bytes from 192.168.4.1: icmp_seq=43 ttl=127 time=3.52 ms
 64 bytes from 192.168.4.1: icmp_seq=44 ttl=127 time=2.30 ms
 64 bytes from 192.168.4.1: icmp_seq=45 ttl=127 time=2.87 ms
 64 bytes from 192.168.4.1: icmp_seq=46 ttl=127 time=4.71 ms
 64 bytes from 192.168.4.1: icmp_seq=47 ttl=127 time=2.52 ms
 64 bytes from 192.168.4.1: icmp_seq=48 ttl=127 time=2.60 ms
 64 bytes from 192.168.4.1: icmp_seq=55 ttl=127 time=7.75 ms
 ....................................^^.....................
 }}}

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


More information about the Bugs mailing list