Modify

Opened 9 years ago

Closed 9 years ago

#1947 closed defect (fixed)

can not associate with the AP using WPA2-PSK

Reported by: xlighting@… Owned by: developers
Priority: normal Milestone:
Component: packages Version:
Keywords: Cc:

Description

hardware: bcm4704 + bcm5325A2 + atheros AR5006
software: KAMIKAZE (bleeding edge), hostapd 0.5.7, madwifi-ng r2420-20070602
summary: my laptop(intel 2200BG) running XP can not associate with the AP when the AP is in WPA2-PSK mode (AES/CCMP),but WPA-PSK (TKIP) works

dmesg:

wlan: 0.8.4.2 (svn r2420)
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.30.13 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, REGOPS_FUNC)
ath_rate_minstrel: 1.2 (svn r2420)

Minstrel automatic rate control algorithm.

Look around rate set to 10%
EWMA rolloff level set to 75%
Max Segment size in the mrr set to 6000 us

wlan: mac acl policy registered
ath_pci: 0.9.4.5 (svn r2420)
PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
PCI: Fixing up device 0000:00:01.0
ath_pci: switching rfkill capability off
ath_pci: ath_pci: switching per-packet transmit power control off
wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 10.5 phy 6.1 radio 6.3
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0x40000000, irq=6
device ath0 entered promiscuous mode
br-lan: port 2(ath0) entering learning state
br-lan: topology change detected, propagating
br-lan: port 2(ath0) entering forwarding state

when in WPA2-PSK mode, the hostapd confg says:

root@OpenWrt:~# cat /var/run/hostapd-ath0.conf
driver=madwifi
interface=ath0
bridge=br-lan
ssid=myssid
debug=0
wpa=2
wpa_pairwise=CCMP
wpa_passphrase=mypassword

but iwpriv shows:

root@OpenWrt:~# iwpriv ath0 get_wpa
ath0      get_wpa:2
root@OpenWrt:~# iwpriv ath0 get_keymgtalgs
ath0      get_keymgtalgs:2

I read the madwifi manual, it says "wpa 2"means wpa2-psk, but "keymgtalgs 2" means TKIP.

with these cofigs, I can not associate with AP. in logread, there is no hostapd-related row.

I try to modify with iwpriv to set "wpa 3" and "keymgtalgs 3"(use "iwpriv ath0 wpa 3" and "iwpriv ath0 keymgtalgs 3" ), then the association starts but I can not get IP via DHCP, logread says:

Jan  1 00:15:27 OpenWrt daemon.info hostapd: ath0: STA 00:15:00:1b:60:70 IEEE 802.11: associated
Jan  1 00:15:31 OpenWrt daemon.info hostapd: ath0: STA 00:15:00:1b:60:70 IEEE 802.11: deauthenticated due to local deauth request
Jan  1 00:15:31 OpenWrt daemon.info hostapd: ath0: STA 00:15:00:1b:60:70 IEEE 802.11: disassociated

if you just modify wpa OR keymgtalgs, the association will not start.

while in TKIP mode, the iwpriv says:

root@OpenWrt:~# iwpriv ath0 get_wpa
ath0      get_wpa:1
root@OpenWrt:~# iwpriv ath0 get_keymgtalgs
ath0      get_keymgtalgs:2

and the logread:

Jan  1 00:43:35 OpenWrt daemon.info hostapd: ath0: STA 00:15:00:1b:60:70 IEEE 802.11: associated
Jan  1 00:43:36 OpenWrt daemon.info hostapd: ath0: STA 00:15:00:1b:60:70 WPA: pairwise key handshake completed (WPA)
Jan  1 00:43:36 OpenWrt daemon.info hostapd: ath0: STA 00:15:00:1b:60:70 WPA: group key handshake completed (WPA)

Attachments (0)

Change History (6)

comment:1 Changed 9 years ago by xlighting@…

update latest svn, replace AR5006 with atheros AR5004, nothing changed

comment:2 follow-up: Changed 9 years ago by Marcus

If you use windows (the standard wireless tool on winxp) download the microsoft patch to updete the software at the last version of WPA protocol.
The standard version of winXP SP2 with the latest update not support WPA2; work only with WPA+TKIP!!!

comment:3 in reply to: ↑ 2 Changed 9 years ago by Some XP and Kamikaze user

Replying to Marcus:

If you use windows (the standard wireless tool on winxp) download the microsoft patch to updete the software at the last version of WPA protocol.
The standard version of winXP SP2 with the latest update not support WPA2; work only with WPA+TKIP!!!

The hotfix that is needed is 893357

You can view the article and download at http://support.microsoft.com/kb/893357

comment:4 follow-up: Changed 9 years ago by xlighting@…

Sorry I don't have this Hotfix installed...I just try Windows Update and install all updates there..I'll try the KB893357 and the latest svn to see if it works, thank you all that keep focus on this "issue".

comment:5 in reply to: ↑ 4 Changed 9 years ago by anonymous

Replying to xlighting@gmail.com:

Sorry I don't have this Hotfix installed...I just try Windows Update and install all updates there..I'll try the KB893357 and the latest svn to see if it works, thank you all that keep focus on this "issue".

after install KB893357, the associate succeed, so this is my own configuration problem..sorry for wasting your time, please close the ticket...

comment:6 Changed 9 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.