WPA - AP association Issue

Dan Williams dcbw at redhat.com
Mon Oct 29 07:12:18 EDT 2007


On Mon, 2007-10-29 at 14:42 +0530, Mr. Maloomnahi wrote:
> Hi Bryan,
> 
> Thanks again for the suggestions. I have annexed the dump below after testing with the latest code.
> 
> The firmware related code which I mentioned is precisely only for firmware based scanning and association and I do not use them if I have to run the WPA Supplicant Src Code. 
> 
> As far as the extra prints are concerned I can see them now. So is this a hostapd Src code issue or configuration file issue?
> 
> ==============
> [root at chandrasekhar wpa_supplicant-0.5.8]# ifconfig ath0 192.168.1.152 up                                                     [root at chandrasekhar wpa_supplicant-0.5.8]# iwconfig ath0 key DEAD-BEEF-AA open                                                [root at chandrasekhar wpa_supplicant-0.5.8]# ./wpa_supplicant -Dmadwifi -iath0 -c /home/prashant/authenticator/wpa_supplicant-0.5.8/EAP_TLS.conf -ddd
> Initializing interface 'ath0' conf '/home/prashant/authenticator/wpa_supplicant-0.5.8/EAP_TLS.conf' driver 'madwifi' ctrl_interface 'N/A' bridge 'N/A'
> Initializing interface (2) 'ath0'
> EAPOL: SUPP_PAE entering state DISCONNECTED
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> SIOCGIWRANGE: WE(compiled)=20 WE(source)=13 enc_capa=0xf
>   capabilities: key_mgmt 0xf enc 0xf
> WEXT: Operstate: linkmode=1, operstate=5
> Own MAC address: 00:14:78:8f:73:1f
> wpa_driver_madwifi_del_key: keyidx=0
> wpa_driver_madwifi_del_key: keyidx=1
> wpa_driver_madwifi_del_key: keyidx=2
> wpa_driver_madwifi_del_key: keyidx=3
> wpa_driver_madwifi_set_countermeasures: enabled=0
> wpa_driver_madwifi_set_drop_unencrypted: enabled=1
> Setting scan request: 0 sec 100000 usec
> Added interface ath0
> 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=0x8b19 len=8
> Received 777 bytes of scan results (3 BSSes)
> Scan results: 3
> AP count: 3
> num_prio: 0
> No suitable AP found.

This means that the scan results did not find an AP that wpa_supplicant
considers useful.  Do you have an SSID specified in the network block?
Can you provide output of 'iwlist ath0 scan' (hide BSSIDs if you wish)
and tell us which AP you're trying to connect to?

> Setting scan request: 5 sec 0 usec
> RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:14:78:8f:5e:49
> State: DISCONNECTED -> ASSOCIATED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> Associated to a new BSS: BSSID=00:14:78:8f:5e:49
> No keys have been configured - skip key clearing
> No network configuration found for the current AP

This means that you don't have a compatible network block specified in
the config file, and therefore wpa_supplicant triggers a disassociation
because you're not supposed to be connected to this AP.

> wpa_driver_madwifi_disassociate
> No keys have been configured - skip key clearing
> State: ASSOCIATED -> DISCONNECTED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> Added BSSID 00:00:00:00:00:00 into blacklist
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> wpa_driver_madwifi_del_key: keyidx=0
> wpa_driver_madwifi_del_key: keyidx=1
> wpa_driver_madwifi_del_key: keyidx=2
> wpa_driver_madwifi_del_key: keyidx=3
> wpa_driver_madwifi_del_key: keyidx=0
> State: DISCONNECTED -> DISCONNECTED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> State: DISCONNECTED -> SCANNING
> Starting AP scan (broadcast SSID)
> Trying to get current scan results first without requesting a new scan to speed up initial association
> Received 777 bytes of scan results (3 BSSes)
> Scan results: 3
> AP count: 3
> num_prio: 0
> No APs found - clear blacklist and try again
> Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
> No suitable AP found.
> Setting scan request: 0 sec 0 usec
> No enabled networks - do not scan

So you don't appear to have any valid networks in your config file.
That's the root of your problem.  Make sure you have every network in
the config file enabled and valid.

Dan

> State: SCANNING -> INACTIVE
> CTRL-EVENT-TERMINATING - signal 2 received
> Removing interface ath0
> State: INACTIVE -> DISCONNECTED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> No keys have been configured - skip key clearing
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> wpa_driver_madwifi_set_countermeasures: enabled=0
> No keys have been configured - skip key clearing
> Cancelling scan request
> Cancelling authentication timeout
> WEXT: Operstate: linkmode=0, operstate=6
> ==============
> 
> Thanks
> PPN
> 
> --
> My life has changed. What about yours?
> Log on to the new Indiatimes Mail and Live out of the Inbox!
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




More information about the HostAP mailing list