No subject

bogus at bogus at
Sat Jan 3 07:49:37 PST 2009

"Connection Established"
But, after that, hostapd sent "EAP-Failure" to terminate the connection.
the hostapd debug trace looks like:
EAP-WSC: WPS processing completed successfully - report EAP failure
EAP: EAP entering state SELECT_ACTION
EAP: getDecision: method failed -> FAILURE
EAP: EAP entering state FAILURE
EAP: Building EAP-Failure (id=3D203)
IEEE 802.1X: 00:22:b0:6b:0a:32 BE_AUTH entering state FAIL
Could anybody give me some clue?
Your inputs are highly appreciated.
Content-Type: text/html; charset=us-ascii

<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Hi, Everybody,</DIV>
<DIV> </DIV>
<DIV>I found the reason.</DIV>
<DIV> </DIV>
<DIV>Actually WPS in hostadp 0.6.7 works perfectly, the reason why D-Link adapter can't</DIV>
<DIV>associate to AP is that the adapter use "auto" as default encrypt method. After adding</DIV>
<DIV>line "wpa_pairwise=TKIP CCMP" into hostapd conf file, everything works well.<BR></DIV>
<DIV> </DIV>
<DIV><BR>--- On <B>Mon, 1/19/09, Tom Tang <I><tom_z79 at></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid">From: Tom Tang <tom_z79 at><BR>Subject: <SPAN>hostapd</SPAN> 0.6.7 with WPS support<BR>To: HostAP at<BR>Date: Monday, January 19, 2009, 8:04 PM<BR><BR>
<DIV id=yiv53354338>
<TABLE cellSpacing=0 cellPadding=0 border=0>
<TD vAlign=top>
<DIV id=yiv681613113>
<DIV id=yiv1423080648>
<DIV>Hi, </DIV>
<DIV> </DIV>
<DIV>I try to use WPS PBC mode to associate hostapd 0.6.7 from D-Link USB WUA-1340</DIV>
<DIV>adapter. It looks the WPS negotiation works well because the "successful" messages</DIV>
<DIV>are printed out from hostapd debug trace such as:</DIV>
<DIV>WPS: Negotiation completed successfully<BR>Received new WPA/WPA2-PSK from WPS for STA 00:22:b0:6b:0a:32<BR>...</DIV>
<DIV> </DIV>
<DIV>From the D-Link utility side,  the pop-up window also shows:</DIV>
<DIV>"Connection Established"</DIV>
<DIV> </DIV>
<DIV>But, after that, hostapd sent "EAP-Failure" to terminate the connection.</DIV>
<DIV>the hostapd debug trace looks like:</DIV>
<DIV>EAP-WSC: WPS processing completed successfully - report EAP failure<BR>EAP-WSC: MSG -> FAIL<BR>EAP: EAP entering state SELECT_ACTION<BR>EAP: getDecision: method failed -> FAILURE<BR>EAP: EAP entering state FAILURE<BR>EAP: Building EAP-Failure (id=203)<BR>IEEE 802.1X: 00:22:b0:6b:0a:32 BE_AUTH entering state FAIL<BR>...</DIV>
<DIV> </DIV>
<DIV>Could anybody give me some clue?</DIV>
<DIV>Your inputs are highly appreciated.</DIV>
<DIV> </DIV>
<DIV> </DIV>


More information about the Hostap mailing list