Cannot connect to AP with WPA2 and AES
marek.belisko at gmail.com
Mon Sep 25 11:52:24 PDT 2017
On Mon, Sep 25, 2017 at 7:53 PM, Jouni Malinen <j at w1.fi> wrote:
> On Mon, Sep 18, 2017 at 10:22:45PM +0200, Belisko Marek wrote:
>> I'm using raspberrypi with sdio esp8089 wifi (kernel 4.9). When trying
>> to connect to AP using WPA-PSK + AES (wpa_supplicant v2.6) I get an
>> below error.
>> nl80211: Supported cipher 00-0f-ac:4
> So the driver supports CCMP..
>> nl80211: Associate (ifindex=2)
>> * bssid=ec:4d:47:88:06:9c
>> * WPA Versions 0x2
>> * pairwise=0xfac04
>> * group=0xfac04
>> * akm=0xfac02
>> nl80211: Association request send successfully
> And accepts a connection that uses CCMP..
>> nl80211: Drv Event 38 (NL80211_CMD_ASSOCIATE) received for wlan0
>> wlan0: Associated to a new BSS: BSSID=ec:4d:47:88:06:9c
> And connects to the requested AP..
>> wlan0: WPA: Installing PTK to the driver
>> wpa_driver_nl80211_set_key: ifindex=2 (wlan0) alg=3 addr=0xf7f9e0
>> key_idx=0 set_tx=1 seq_len=6 key_len=16
>> nl80211: KEY_DATA - hexdump(len=16): [REMOVED]
>> nl80211: KEY_SEQ - hexdump(len=6): 00 00 00 00 00 00
>> nl80211: set_key failed; err=-2 No such file or directory)
>> wlan0: WPA: Failed to set PTK to the driver (alg=3 keylen=16
> But then rejects a command to set the CCMP key for the AP with which
> there is an association and using an error code that would imply the STA
> entry for that AP is not present.
> I'm not familiar with the driver used here, but someone would need to
> take a look at what it is doing in this type of case to figure out what
> needs fixing.
I found an issue in meantime. Some kernel modules ccm, ctr was missing
and that was the reason why it cannot connect to the WPA (AES or
TKIP). Mainly I got clue when saw this message: WPA: Failed to set PTK
to the driver
> Jouni Malinen PGP id EFC895FA
as simple and primitive as possible
Marek Belisko - OPEN-NANDRA
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
More information about the Hostap