Problems connecting to hostap 2.0-devel

[Jouni Malinen]

On Wed, Jul 11, 2012 at 04:39:18PM -0500, Harshal Chhaya wrote:
> I am using hostapd 2.0-devel on an AR9342 with an external freeRADIUS
> server to handle the WPA2-PEAP authentication.
> 
> I can connect an Android phone (b4:07:f9:37:9f:67) to the AP but can't
> connect my embedded client (00:09:37:0d:76:77). Is the EAPOL-Start
> from the client throwing off hostapd?

It looks more like a client side issue to me.. What WLAN driver and
supplicant is used on the client?

> wlan0: STA 00:09:37:0d:76:77 IEEE 802.11: associated (aid 2)

> wlan0: CTRL-EVENT-EAP-STARTED 00:09:37:0d:76:77
> wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1
> wlan0: STA 00:09:37:0d:76:77 IEEE 802.1X: Sending EAP Packet (identifier 186)

This is an EAP-Request/Identity

> wlan0: STA 00:09:37:0d:76:77 IEEE 802.1X: received EAPOL-Start from STA

and the initial EAPOL-Start at about the same time.. This itself is fine
and expected based on the EAPOL state machines.

> wlan0: STA 00:09:37:0d:76:77 WPA: event 5 notification
> wlan0: STA 00:09:37:0d:76:77 IEEE 802.1X: aborting authentication
> wlan0: CTRL-EVENT-EAP-STARTED 00:09:37:0d:76:77
> wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1
> wlan0: STA 00:09:37:0d:76:77 IEEE 802.1X: Sending EAP Packet (identifier 171)

This is another EAP-Request/Identity (triggered by that EAPOL-Start).
This is still expected.

> wlan0: STA 00:09:37:0d:76:77 IEEE 802.1X: received EAPOL-Start from STA

But this is not.. For some reason, the station does not seem to be
replying to the identity request and just request a new start of the EAP
authentication. The AP behavior here looks correct to me based on what
hostapd log shows. To verify this, a wireless sniffer could be used to
check that the EAP-Request/Identity packet is sent and that there is no
response to it.

-- 
Jouni Malinen                                            PGP id EFC895FA