wpa_supplicant 0.2.5: succesful key negotiation, kicked off by "new AP" event

Pedro Ramalhais ramalhais at serrado.net
Wed Nov 17 14:28:51 EST 2004


On Wed, 2004-11-17 at 19:20, DAVID LOSADA CARBALLO wrote:
> Hello,
> 
> I'm using wpa_supplicant 0.2.5 along with Intel ipw2100 drivers (version 1.0) on a linux 2.6.9 kernel on a Gentoo distribution. This against a Buffalo AirStation G54 access point, using a WPA-PSK configuration with AES encryption.
> 
> As what i understand from wpa_supplicant debugging output (which i can send directly to anybody willing to help me), wpa_supplicant succesfully finds the wireless LAN and performs the key negotiation:
> 
> WPA: Key negotiation completed with 00:07:40:a2:d4:98
> Cancelling authentication timeout
> EAPOL: External notification - portValid=1
> EAPOL: External notification - EAP success=1
> 
> immediately after, though, a wireless event is received:
> 
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:07:40:a2:d4:98
> 
> ("new AP", maybe still scanning?). In consequence, negotiated keys are cleared and process is kicked off again:
> 
> Association event - clear replay counter
> Associated to a new BSS: BSSID=00:07:40:a2:d4:98
> wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> EAPOL: External notification - portValid=0
> EAPOL: External notification - EAP success=0
> EAPOL: External notification - portEnabled=1
> EAPOL: SUPP_PAE entering state CONNECTING
> 
> result is that i never get a stable connection. Any clues about what to do with this problem, please?
> 
> kind regards
> 
> David Losada
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

Hi!
That's a problem with the ipw2100 driver where association events are
delayed (it's a firmware problem), so wpa_supplicant receives packets
before the association event, and when it receives the association event
it resets the keys, making authentication fail.
-- 
Pedro Ramalhais <ramalhais at serrado.net>




More information about the HostAP mailing list