>From the RSN log, the dual 4-way handshakes succeeded, but the GTK was not installed: nl80211: set_key failed; err=-22 Invalid argument) and it looks like there was a problem marking the peer authorized: AUTH: 48:45:20:3b:31:75 authorizing port Could not set station 48:45:20:3b:31:75 flags for kernel driver (errno=11) Ray On Mon, Jun 13, 2016 at 7:42 AM, Vincent CESSON <vincent.cesson@xxxxxxxx> wrote: > Hi Amitkumar, > > Here are the wpa_supplicant logs (with CONFIG_IBSS_RSN=y enabled) from the > two devices. Beside wpa_supplicant, I manually set IPs 192.168.1.xy with > command "ifconfig mlan0 192.168.1.xy" and then I try to ping each other, > without success. > > Vincent > > > > Le 2016-06-13 15:40, Amitkumar Karwar a écrit : >> >> Hi Vincent, >> >>> From: Vincent CESSON [mailto:vincent.cesson@xxxxxxxx] >>> Sent: Monday, June 13, 2016 7:09 PM >>> To: Amitkumar Karwar >>> Cc: Raymond Hayes; linux-wireless@xxxxxxxxxxxxxxx >>> Subject: RE: mwifiex+wpa_supplicant cannot set up WPA/WPA2 ADHOC >>> >>> About the strange behaviour with the two devices connecting despite the >>> bad passwords, I made a little mistake: on the device 2, wpa_supplicant >>> was not built with option CONFIG_IBSS_RSN=y. But still, device 1 should >>> not accept device 2... >>> >>> Note that with option CONFIG_IBSS_RSN=y enabled on both devices, WPA-PSK >>> connection does not work, even with the right password... >>> >> >> I see. Please share the wpa_supplicant logs with CONFIG_IBSS_RSN=y >> enabled for analysis. >> >> Regards, >> Amitkumar -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
