Hi Janusz, > -----Original Message----- > From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless- > owner@xxxxxxxxxxxxxxx] On Behalf Of Janusz Dziedzic > Sent: Sunday, June 28, 2015 00:49 > To: Peer, Ilan > Cc: linux-wireless@xxxxxxxxxxxxxxx; chaitanya.mgit@xxxxxxxxx; Johannes > Berg > Subject: Re: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - > direct probe issue > > On 24 June 2015 at 14:20, Peer, Ilan <ilan.peer@xxxxxxxxx> wrote: > > Hi Janusz, > > > > Any chance you can check if the attached patch fixes the issue you > reported? > > > > Thanks in advance, > > > I just check the mac80211/cfg80211 code, and I am not sure this direct probe > could work correctly. > > Function ieee80211_rx_mgmt_probe_resp() is interesting. > Seems we call > ieee80211_rx_bss_info() -> ieee80211_bss_info_update -> > cfg80211_inform_bss_width_frame() -> cfg80211_bss_update() -> this could > set bss->proberesp_ies and after that check: > > if (ifmgd->auth_data && !ifmgd->auth_data->bss->proberesp_ies && > ether_addr_equal(mgmt->bssid, ifmgd->auth_data->bss->bssid)) { > /* got probe response, continue with auth */ > sdata_info(sdata, "direct probe responded\n"); > > So, ifmgd->auth_data->bss->proberesp_ies could be set before check? > > BTW, During my tests (no matter which card used) I never saw this msg: > sdata_info(sdata, "direct probe responded\n"); And always saw 3 failed direct > probes. > I think that you have a point here. Regardless, even without this, the auth timer would expire and we should be able to continue the auth flow as we should have the probe now. Ilan. ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
