<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Hi Jouni <BR>
Thanks for your information.<BR>
<BR>
I want to use WEP shared key authentication. No need to use 802.1x and eap_server.<BR>
Now my hostapd.conf looks like:<BR>
<BR>
auth_algs=2<BR>
# Static WEP key configuration<BR>wep_default_key=0<BR>wep_key0=123456789a<BR>
#ieee8021x=0<BR>#eap_server=0<BR>
<BR>
===.config===<BR>
CONFIG_DRIVER_NL80211=y<BR>LIBNL=/usr/src/libnl<BR>CFLAGS += -I$(LIBNL)/include<BR>LIBS += -L$(LIBNL)/lib<BR>
LIBSSL=/home/zimmer/802/openssl-0.9.8i<BR>CFLAGS += -I$(LIBSSL)/include<BR>LIBS += -L$(LIBSSL)<BR>#eap_server=1<BR>
<BR>
Problem is :<BR>
On PC client, I can see the ssid with WEP encrypt capacibility.<BR>
But after I enter the password and click connect, hostapd shows: <BR>
<BR>
authentication: STA=00:16:6f:1b:32:05 auth_alg=0 auth_transaction=1 status_code=0 wep=0<BR>Unsupported authentication algorithm (0)<BR>authentication reply: STA=00:16:6f:1b:32:05 auth_alg=0 auth_transaction=2 resp=13 (IE len=0)<BR><BR>
I think it should be (2), why client sends (0)?<BR>
Did I still miss something in .config or hostapd.conf?<BR>
I use standard 2.6.29 kernel and hostapd-0.6.9, have not modified anything.<BR>
<BR>
Manfred<BR>
<BR>> <BR>> > I tried to config the hostapd.conf into WEP-40 mode.<BR>> > <BR>> > But when I run hostapd and connect to it, the server alway run in a open system auth mode :(<BR>> <BR>> And that would be because you configured hostapd to use open system with<BR>> WEP.. Based on your comment here, it sounds like you would like to use<BR>> shared key authentication instead(?).<BR>> <BR>> > I feel puzzled. Does hostapd-0.6.9 supports WEP encrypt mode? Or I should use 0.5.8 version?<BR>> <BR>> Both 0.6.9 and 0.5.8 support WEP and WEP can be used with both open<BR>> system and shared key authentication.<BR>> <BR>> > ===hostapd.conf===<BR>> <BR>> > auth_algs=1<BR>> <BR>> 1 = open system<BR>> 2 = shared key<BR>> 3 = allow either<BR>> <BR>> > ieee8021x=1<BR>> > eapol_version=2<BR>> > eap_message=hello<BR>> > <BR>> > wep_key_len_broadcast=5<BR>> > wep_key_len_unicast=5<BR>> > wep_rekey_period=300<BR>> > eapol_key_index_workaround=0<BR>> <BR>> However, this makes me think that maybe you do not want to use shared<BR>> key authentication after all and are thinking of using IEEE 802.1X<BR>> instead(?). If that is the case, please note that it will use open<BR>> system authentication as far as IEEE 802.11 authentication is concerned<BR>> and that will only be followed by EAPOL authentication.<BR>> <BR>> > eap_server=1<BR>> <BR>> If you are planning on using the internal EAP server, you will also need<BR>> to configure it properly (eap_user_file, certificate/private key, etc.)<BR>> as shown in the example hostapd.conf.<BR>> <BR>> -- <BR>> Jouni Malinen PGP id EFC895FA<BR>> <BR>> <BR><BR><br /><hr />Windows Live™: Keep your life in sync. <a href='http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_012009' target='_new'>Check it out!</a></body>
</html>