Hi Johannes, > On May 22, 2018, at 3:52 PM, Johannes Berg <[email protected]> wrote: > > On Tue, 2018-05-22 at 15:49 -0500, Denis Kenzior wrote: > >> Okay, so we need to use NL80211_BSS_PRESP_DATA if we want to filter out >> scan results that are coming from beacons, right? > > You could do that, yes. In non-hidden cases you get the beacon/probe > response data combined, in hidden cases you may get the beacon data > separately and the (second, third, ...) entry with probe response data > will come with beacon data too. > > I'm not really sure what value that would have though. In general, you > might want to not display hidden SSIDs as such or at all in the UI.
Right. The intent here is to handle auto-connect to hidden networks. So if we have provisioned a network that is hidden, and we see hidden networks via beacons, we want to scan for our provisioned hidden SSIDs and only get the probe response results. > >> So what's the practical use of the flush flag? Or is that something >> that was meant to be 'for-testing-only'? > > I think you misunderstand? The value is that it ensures that nothing is > present in the list that was received *before* the scan. > We misunderstood how it was supposed to work, but no, I get how things work now. I’m just curious what other potential uses this flag might have. Regards, -Denis
