hostapd-0.6.9 configed into WEP configuration but auth inopensystem way (Jouni Malinen)

[aaaaa aaaaa]

Hi Jouni 

Thanks for your information.

 

I want to use WEP shared key authentication. No need to use 802.1x and eap_server.

Now my hostapd.conf looks like:

 

auth_algs=2

# Static WEP key configuration
wep_default_key=0
wep_key0=123456789a

#ieee8021x=0
#eap_server=0

 

===.config===

CONFIG_DRIVER_NL80211=y
LIBNL=/usr/src/libnl
CFLAGS += -I$(LIBNL)/include
LIBS += -L$(LIBNL)/lib

LIBSSL=/home/zimmer/802/openssl-0.9.8i
CFLAGS += -I$(LIBSSL)/include
LIBS += -L$(LIBSSL)
#eap_server=1

 

Problem is :

On PC client, I can see the ssid with WEP encrypt capacibility.

But after I enter the password and click connect, hostapd shows: 

 

authentication: STA=00:16:6f:1b:32:05 auth_alg=0 auth_transaction=1 status_code=0 wep=0
Unsupported authentication algorithm (0)
authentication reply: STA=00:16:6f:1b:32:05 auth_alg=0 auth_transaction=2 resp=13 (IE len=0)


I think it should be (2), why client sends (0)?

Did I still miss something in .config or hostapd.conf?

I use standard 2.6.29 kernel and hostapd-0.6.9, have not modified anything.

 

Manfred


> 
> > I tried to config the hostapd.conf into WEP-40 mode.
> > 
> > But when I run hostapd and connect to it, the server alway run in a open system auth mode :(
> 
> And that would be because you configured hostapd to use open system with
> WEP.. Based on your comment here, it sounds like you would like to use
> shared key authentication instead(?).
> 
> > I feel puzzled. Does hostapd-0.6.9 supports WEP encrypt mode? Or I should use 0.5.8 version?
> 
> Both 0.6.9 and 0.5.8 support WEP and WEP can be used with both open
> system and shared key authentication.
> 
> > ===hostapd.conf===
> 
> > auth_algs=1
> 
> 1 = open system
> 2 = shared key
> 3 = allow either
> 
> > ieee8021x=1
> > eapol_version=2
> > eap_message=hello
> > 
> > wep_key_len_broadcast=5
> > wep_key_len_unicast=5
> > wep_rekey_period=300
> > eapol_key_index_workaround=0
> 
> However, this makes me think that maybe you do not want to use shared
> key authentication after all and are thinking of using IEEE 802.1X
> instead(?). If that is the case, please note that it will use open
> system authentication as far as IEEE 802.11 authentication is concerned
> and that will only be followed by EAPOL authentication.
> 
> > eap_server=1
> 
> If you are planning on using the internal EAP server, you will also need
> to configure it properly (eap_user_file, certificate/private key, etc.)
> as shown in the example hostapd.conf.
> 
> -- 
> Jouni Malinen PGP id EFC895FA
> 
> 


_________________________________________________________________
Windows Live?: Keep your life in sync. Check it out!
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_012009
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20090618/79076892/attachment-0001.htm