• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 40 subscribers
  • Views 510 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Sometime has problem connecting to an AP with WPA2 PSK

Ed Tsang
Intellectual 290 points

 

 

 

It is on Android gingerbread with wl1273.

Some time we get into issue of not able to connect to AP with WPA2 PSK. If we "forget network" and reenter the security phase again, then it start working again?

I checked the wpa_supplicant.conf, the psk="..." is correct, key_mgmt=WPA-PSK..

On the bad case:

0-13 20:32:15.554 I/wpa_supplicant( 1862): Associated with 00:24:6c:d3:4d:22 

10-13 20:32:15.554 E/wpa_supplicant( 1862): Setting authentication timeout: 10 sec 0 usec
10-13 20:32:15.554 E/wpa_supplicant( 1862): Cancelling scan request
...
10-13 20:32:20.750 E/wpa_supplicant( 1862): Ongoing Scan action...
10-13 20:32:20.750 E/wpa_supplicant( 1862): CMD: DRIVER SCAN-PASSIVE
10-13 20:32:25.554 I/wpa_supplicant( 1862): Authentication with 00:24:6c:d3:4d:22 timed out.

 

On good case: I will see after Associated

10-13 21:33:11.117 E/wpa_supplicant( 2452): Wireless event: cmd=0x8c02 len=164

10-13 21:33:11.117 E/wpa_supplicant( 2452): CMD: DRIVER RSSI-APPROX

10-13 21:33:11.117 E/wpa_supplicant( 2452): RX EAPOL from 00:24:6c:d3:4d:e2

 

10-13 21:33:11.117 E/wpa_supplicant( 2452): Setting authentication timeout: 10 sec 0 usec

10-13 21:33:11.132 E/wpa_supplicant( 2452): State: ASSOCIATED -> 4WAY_HANDSHAKE

...

10-13 21:33:11.148 E/wpa_supplicant( 2452): Wireless event: cmd=0x8c02 len=164

10-13 21:33:11.148 E/wpa_supplicant( 2452): RX EAPOL from 00:24:6c:d3:4d:e2

10-13 21:33:11.179 E/wpa_supplicant( 2452): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE

10-13 21:33:11.179 I/wpa_supplicant( 2452): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00

10-13 21:33:11.179 E/wpa_supplicant( 2452): RX EAPOL from 00:24:6c:d3:4d:e2

10-13 21:33:11.179 E/wpa_supplicant( 2452): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE

...

10-13 21:33:11.242 I/wpa_supplicant( 2452): WPA: Key negotiation completed with 00:24:6c:d3:4d:e2 [PTK=TKIP GTK=TKIP]

10-13 21:33:11.250 E/wpa_supplicant( 2452): Cancelling authentication timeout

10-13 21:33:11.250 E/wpa_supplicant( 2452): State: GROUP_HANDSHAKE -> COMPLETE

Any hint from any one?  0x8c02 seem to be driver specific ASCII string. Why we are not seeing this, could this be the AP on the other side?

Ed


 

  • 0
    TI__Genius 9240 points

    Hi Ed,

     

    It looks like the association was successful however the authentication failed even before starting the WPA 4 way handshake, in that case there might be environmental issue that can cause the AP or the station to not receiving the other side frames.

     

    When it happens, can you wait for about 3 minutes and let me know if eventually it does connect?  In addition can you get a sniffer trace? I would like to see the Authentication stage with WLAN sniffer so I can get more understanding of what is going on, on the air.

     

    Regards,

    Eyal

     

  • 0 in reply to Eyal a
    Intellectual 290 points

    It still fail after a long wait.

    I will look for a wifi sniffer.

    I also have the both debug ports wired out (one for BT, one for wif??). Will the logger trace help?

  • 0 in reply to Ed Tsang
    TI__Genius 9240 points

    Hi Ed,

    thanks, currently i would need a WLAN Sniffer log to make progress

    Regards,

    Eyal