Why does supplicant lose the SSID?

Sriharsha Vedurmudi svedurumudi
Thu Oct 4 08:02:55 PDT 2007


Friends,
 The supplicant is losing the SSID (after associating with the AP)
when it is trying to process the received EAPOL frame 1/4. I get the
message:
WPA: No SSID info found (msg 1 of 4).
The code shows that when the state machine has NULL for SSID, this
comes up. Under what circumstances will the state machine lose the
SSID info after association? I am trying to write a driver, using
driver_wext, to test WPA-PSK feature of a new upcoming chip.
The access point is sending the first EAPOL frame 4 times (in which
one or two times the FCS check fails) and then disassociating the sta.

Here is the dump for clarity:

Received 186 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:14:6c:e0:73:b5 ssid='TEST_WPA' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   selected based on WPA IE
   selected WPA AP 00:14:6c:e0:73:b5 ssid='TEST_WPA'
Try to find non-WPA AP
Trying to associate with 00:14:6c:e0:73:b5 (SSID='TEST_WPA' freq=2437 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00
00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
LinkMode: -1
Operstate:5
WEXT: Operstate:
linkmode=-1
operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b1a len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:14:6c:e0:73:b5
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
  key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
  key_length=32 key_data_length=0
  replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_nonce - hexdump(len=32): ac 97 b5 e4 99 fa 9c 93 ef b7 37 9e 16 3a 62 5d e
4 d5 6d c9 99 7f 3f 9f 18 61 14 6a 69 ab c3 9a
  key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: No SSID info found (msg 1 of 4).


Please let me know if anyone has any idea why this is happening.

Best regards,
Sriharsha.




More information about the Hostap mailing list