802.1x-MD5 test faild
wayne
warren001
Mon Dec 20 19:23:43 PST 2004
Hi,
Below is the debug message. It seems that wpa supplicant did set the
key, but
after associating with the AP, it will delete the key.
What I use to verify is simple, just type "iwconfig ath0" to see if the
key is set to the driver.
Initializing interface 'ath0' conf 'wpa_supplicant.conf' driver 'default'
Configuration file 'wpa_supplicant.conf' ->
'/root/hostap-12232004-make-ok-for-madwifi/wpa_supplicant/wpa_supplicant.con
f'
Reading configuration file
'/root/hostap-12232004-make-ok-for-madwifi/wpa_supplicant/wpa_supplicant.con
f'
Priority group 0
id=0 ssid='Cisco1231g'
Initializing interface (2) 'ath0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:11:22:33:44:55
wpa_driver_madwifi_set_wpa: enabled=1
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=10):
31 32 33 31 67 1231
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b1a len=23
Wireless event: cmd=0x8b19 len=12
selected non-WPA AP 00:33:44:55:66:77 ssid='Cisco1231g'
Trying to associate with 00:33:44:55:66:77 (SSID='Cisco1231g' freq=2462 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_key: alg=WEP key_idx=1 set_tx=1 seq_len=0 key_len=10
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
wpa_supplicant_initiate_eapol
Wireless event: cmd=0x8b1a len=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:33:44:55:66:77
Association event - clear replay counter
Associated to a new BSS: BSSID=00:33:44:55:66:77
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Associated with 00:33:44:55:66:77
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:33:44:55:66:77
Setting authentication timeout: 10 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=1
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
77 61 79 6e 65 40 44 45 4d 4f wayne at DEMO
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:33:44:55:66:77
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=2
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
77 61 79 6e 65 40 44 45 4d 4f wayne at DEMO
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:33:44:55:66:77
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=4 id=3
EAP: EAP entering state GET_METHOD
EAP: initialize selected EAP method (4, MD5)
EAP: EAP entering state METHOD
EAP-MD5: generating Challenge Response
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:33:44:55:66:77
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: Workaround for unexpected identifier field in EAP Success: reqId=4
lastId=3 (these are supposed to be same)
EAP: EAP entering state SUCCESS
EAPOL: IEEE 802.1X for plaintext connection; no EAPOL-Key frames required
WPA: EAPOL processing complete
Cancelling authentication timeout
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_BE entering state IDLE
WPA: EAPOL frame too short, len 46, expecting at least 99
Regards,
Wayne
----- Original Message -----
From: "Jouni Malinen" <jkmaline at cc.hut.fi>
To: <hostap at shmoo.com>
Sent: Tuesday, December 21, 2004 10:37 AM
Subject: Re: Re : 802.1x-MD5 test faild
> On Tue, Dec 21, 2004 at 07:56:03AM +0800, wayne wrote:
>
> > I've downloaded 0.3.2 to test, but it seems that the wep key
> > does not set to the driver when using 802.1x-md5.
> > Does the profile need special care ?
> >
> > network={
> > ssid="test"
> > key_mgmt=IEEE8021X
> > scan_ssid=1
> > eap=MD5
> > identity="wayne at DEMO"
> > password="1234"
> > eapol_flags=0
> > wep_key1="1234567890"
> > wep_tx_keyidx=1
> > }
>
> Is that really index 1 for the key, not 0? How did you verify that the
> WEP key is not being set to the driver? Did you look at the
> wpa_supplicant debug log? I did not run a complete test, but I verified
> that the driver did indeed show the WEP key when configured in this way.
>
> --
> Jouni Malinen PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>
> ==========================================================
> ????93?~?????@?????q???V?m???U???????i?I
> http://edm-prg.epaper.com.tw/click.php?ad_code=296911
> ==========================================================
> SkypeOut ?????[0.7??/?? ???j??0.9??/?? ???Y???R>>
> http://skype.pchome.com.tw/skypeout.htm
> ==========================================================
More information about the Hostap
mailing list