802.1x: EAP/TLS - xsupplicant and hostap wep enabled

[pof]

In addition to my previous e-mail, I've tried to issue this command in
both, the client and the hostAP machines and got the same results:

# hostap_crypt_conf wlan0 ff:ff:ff:ff:ff:ff WEP

and I see this in the logs:

Dec  1 01:12:17 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
802.11: authentication OK (open system)
Dec  1 01:12:17 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
802.11: authenticated
Dec  1 01:12:17 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
802.11: association OK (aid 1)
Dec  1 01:12:17 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
802.11: associated (aid 1)
Dec  1 01:12:22 nimble kernel: wlan0: RX: IEEE 802.1X frame
Dec  1 01:12:22 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
802.1X: received EAPOL-Start from STA
Dec  1 01:12:22 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
802.1X: unauthorizing port
Dec  1 01:12:51 nimble kernel: wlan0: RX: IEEE 802.1X frame
Dec  1 01:12:51 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
802.1X: received EAPOL-Start from STA
Dec  1 01:13:22 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
802.1X: unauthorizing port

but xsupplicant still replyes:

No authenticator found! Assuming the port is authorized!

Do you know what am I doing wrong here? or where can I find some
documentation about this?

Take care,

	Pau.

On Mon, 2003-12-01 at 00:59, pof wrote:
> On Sun, 2003-11-30 at 21:28, Michael Richardson wrote:
> 
> >     pof> I have succeeded with EAP/MD5 and EAP/TLS always with wep disabled.
> >     pof> Now I want to test with  EAP/TLS and wep enabled:
> > 
> >   As far as I understand, if you are using Xsupplicant and EAP-*, then you
> > will have dynamic WEP enabled. 
> 
> The actual problem is that if I set wep_key_len_broadcast=5
> wep_key_len_unicast=5 and wep_rekey_period=300 in hostapd.conf then I
> don't get authenticated, and I see this in the logs when I launch
> xsupplicant on the client machine:
> 
> Dec  1 00:46:29 nimble kernel: wlan0: encryption configured, but RX
> frame not encrypted (SA=00:90:d1:06:5b:9f)
> Dec  1 00:46:50 nimble hostapd: wlan0: STA 00:90:d1:06:5b:9f IEEE
> 802.1X: unauthorizing port
> 
> I get authenticated without problems if I comment out the 3 parameters 
> mentioned above in hostapd.conf.
> 
> Does the client require any special config for WEP?
> 
> 
> >   I.e. if you turn on static WEP, it won't work, because you need to
> > associate with the AP in the clear, do EAP and arrive at WEP keys.
> 
> I thought that if I set up the same static WEP key in both the client
> machine and the hostAP machine it would work. 
> 
> Kind Regards,
> 
> 	Pau.
-- 
 .----------------------------------------------.
|  Pau Oliva Fora         http://pof.eslack.org  |
|  KeyID: 665D05B533539E02 available at keyserv  |
 `----------------------------------------------'
         In Googlis non est, ergo non est.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20031201/7355676e/attachment.pgp