802.1X Unicast Keys?

Raghu raghu at sraamerica.com
Mon Dec 23 16:10:24 EST 2002

> I have never tested unicast keys without setting 
broadcast keys with 
> .1x. Are you setting broadcast keys manually for both 
the stations and 
> AP? I would suggest trying with both -i13 and -b13 on 
the same command 
> line to get both keys set automatically. Please let me 
know, if there is 
$ ./hostapd -x -b13 -i13 -o192.168.1.1 -a192.168.1.1 
-stest -SSSID wlan0 
IEEE 802.1X: 00:04:5a:0d:f4:68 BE_AUTH entering state 
IEEE 802.1X: 00:04:5a:0d:f4:68 REAUTH_TIMER entering state 
IEEE 802.1X: 00:04:5a:0d:f4:68 AUTH_PAE entering state 
IEEE 802.1X: Authorizing station 00:04:5a:0d:f4:68 
IEEE 802.1X: 00:04:5a:0d:f4:68 BE_AUTH entering state IDLE 
IEEE 802.1X: 00:04:5a:0d:f4:68 AUTH_KEY_TX entering state 
IEEE 802.1X: Sending EAPOL-Key(s) to 00:04:5a:0d:f4:68 
(identifier 6) 
Individual WEP key - hexdump(len=13): bd f9 b4 6b 1c 2e 42 
46 b1 49 fc 7e ee 
Station 00:04:5a:0d:f4:68 authenticated (open system) 
Station 00:04:5a:0d:f4:68 associated (aid 1) 
Unicast key is getting generated but I am not sure if the 
same is 
sent to the Supplicant. I think only the Broadcast key is 
being sent. 
Currently I am not able to atleast ping the AP. With -b13 
option I was 
able to ping AP. 
Can you please let me know the state machine of 
transmitting the 
Broadcast key and Unicast key to the supplicant when -b13 
& -i13 
options are used on the same command? 

More information about the HostAP mailing list