Simple wpa_supplicant question

Martin Samuelsson hostap at cos.user.lysator.liu.se
Tue Mar 15 05:02:32 EST 2005


Dear list,

I have been using wpa_supplicant for a while now, since waproamd got
orphaned by it's author. Until recently it has been working perfectly
because all networks encountered have been open and thus not needed key
configuration.

However now I'm daily using a network with a WEP key and can't get it to
work for me. Could anyone please give me a hint?

I've read all the documentation and the configuration provided in the
Debian package, but not fully understood it.

Doing things'n'stuff manually works. I.e. giving a command like the
following brings the interface up.

	iwconfig eth0 essid helllo key s:world ap 00:02:2D:61:4F:32 ¹

A simple case like this brings me to believe that I should go for a config
looking something like what's included below:

	network={
		ssid="helllo"
		bssid=00:02:2D:61:4F:32
		key_mgmt=NONE
		wep_key0="world"
		wep_tx_keyidx=0
		priority=1000
	}

However when trying to use the software now I get the following output: (The
exclamation marks are what I feel look like bad lines)

	Setting scan request: 0 sec 0 usec
	Starting AP scan (broadcast SSID)
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
	Scan timeout - try to get results
	Received 748 bytes of scan results (4 BSSes)
	Scan results: 4
	Selecting BSS from priority group 1000
	0: 00:02:2d:61:4f:13 ssid='helllo' wpa_ie_len=0 rsn_ie_len=0
	   skip - no WPA/RSN IE
	1: 00:02:2d:61:4f:32 ssid='helllo' wpa_ie_len=0 rsn_ie_len=0
	   skip - no WPA/RSN IE
	2: 00:07:40:9f:14:71 ssid='helllo' wpa_ie_len=0 rsn_ie_len=0
	   skip - no WPA/RSN IE
	3: 00:80:5a:22:ae:a2 ssid='OTHER' wpa_ie_len=0 rsn_ie_len=0
	   skip - no WPA/RSN IE
	   selected non-WPA AP 00:02:2d:61:4f:32 ssid='helllo'
	Trying to associate with 00:02:2d:61:4f:32 (SSID='helllo' freq=0 MHz)
	Cancelling scan request
	Automatic auth_alg selection: 0x1
	wpa_driver_ipw_set_auth_alg: auth_alg=0x1
	No keys have been configured - skip key clearing
	wpa_driver_ipw_set_key: alg=WEP key_idx=0 set_tx=1 seq_len=0 key_len=5
	wpa_driver_ipw_set_drop_unencrypted: enabled=1
	wpa_driver_ipw_set_wpa: enabled=0
!	ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
!	ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
	Setting authentication timeout: 5 sec 0 usec
	EAPOL: External notification - portControl=ForceAuthorized
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
	Wireless event: cmd=0x8b1a len=19
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
!	Authentication with 00:00:00:00:00:00 timed out.
	wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
	wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
	wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
	wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
	EAPOL: External notification - portEnabled=0
	EAPOL: External notification - portValid=0
	Setting scan request: 0 sec 0 usec
	EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
	Starting AP scan (specific SSID)
	Scan SSID - hexdump_ascii(len=6):
	     73 65 63 72 65 74                                 secret
!	ioctl[SIOCSIWSCAN{,EXT}]: Operation not supported
	Failed to initiate AP scan.
	Setting scan request: 10 sec 0 usec

Is there something I've missed in my configuration or doesn't wpa_supplicant
work with WEP encrypted networks and the ipw2100?

Any help appreciated. I'm running Debian/Sarge with wpasupplicant
0.3.8-1, which should also be the latest upstream release, right?
--
/Martin

[1] The network identifying data has been changed to protect the innocent, but they
    are all ascii and their lengths match. (The HW addresses however are real)



More information about the HostAP mailing list