On 11.02.06 15:11:47, Reinhard Tartler wrote:
> can you please check if this bug still applies to you? There have been
> several new upstream version since you submitted this bug and I'm fairly
> sure that this bug does not apply anymore. Feel free to close this bug.

This bug is still valid and I don't understand why it is marked as
fixed-upstream, because it seems it is not.

I can't check WPA atm because I don' have a WPA-Net at hand, but WEP is
still failing. Configuration looks like this:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0

eapol_version=1
ap_scan=1
fast_reauth=1
network={
  ssid="pakulat"
  key_mgmt=NONE
  mode=0
  wep_key0=38CDAE492AB84CC..
  wep_tx_keyidx=0
}

Debug-output from wpasupplicant:
Initializing interface 'ipw0' conf '/etc/wpa_supplicant.conf' driver 'wext' 
ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 24 - start of a new network block
ssid - hexdump_ascii(len=0):
key_mgmt: 0x4
priority=1 (0x1)
Line: 29 - start of a new network block
ssid - hexdump_ascii(len=7):
     70 61 6b 75 6c 61 74                              pakulat
key_mgmt: 0x4
mode=0 (0x0)
wep_key0 - hexdump(len=13): [REMOVED]
wep_tx_keyidx=0 (0x0)
Priority group 1
   id=0 ssid=''
Priority group 0
   id=1 ssid='pakulat'
Initializing interface (2) 'ipw0'
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
SIOCGIWRANGE: WE(compiled)=19 WE(source)=16 enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3
Own MAC address: 00:04:23:7f:cf:f4
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface ipw0
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'ipw0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ipw0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:60:b3:99:15:70
State: SCANNING -> ASSOCIATED
Associated to a new BSS: BSSID=00:60:b3:99:15:70
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
EAPOL: External notification - portControl=ForceAuthorized
Associated with 00:60:b3:99:15:70
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:60:b3:99:15:70 completed (auth)
RTM_NEWLINK, IFLA_IFNAME: Interface 'ipw0' added
Scan timeout - try to get results
Received 191 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 1
0: 00:60:b3:99:15:70 ssid='pakulat' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
Selecting BSS from priority group 0
0: 00:60:b3:99:15:70 ssid='pakulat' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
   selected non-WPA AP 00:60:b3:99:15:70 ssid='pakulat'
Already associated with the selected AP.

This looked promising, but I don't get a response from the dhcp server.
And this works with coding the key and ssid into interfaces.

Huh, oh. I just see that after establishing a connection withoug
wpa_supplicant now I also get a connection with it. However removing the
module and trying "fresh" shows that it again doesn't get an ip. 

Andreas

-- 
Next Friday will not be your lucky day.  As a matter of fact, you don't
have a lucky day this year.

Attachment: pgpC9rN9uS7Py.pgp
Description: PGP signature

Reply via email to