On Thu, Jul 2, 2015 at 5:09 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Thu, 2015-07-02 at 11:44 +0200, Janusz Dziedzic wrote: >> >> > The issue above can probably easily fixed by doing the BSS update >> > after >> > the "direct probe responded" though, no? Like this: >> > https://p.sipsolutions.net/67f9212f0f9f3642.txt >> > >> This was my first idea, but in such case I suspect we will send >> another direct probe while bss->proberesp_ies will be not set and >> ieee80211_probe_auth() will send second probe_req? Yes, if the seuqnce number is not set the second probe resp also gets dropped. > But why would it not be set? We do rely on ieee80211_rx_bss_info() > setting it, after all. The probe resp is dropped early in the rx_path so this call is not made. -- 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
