On Sat, 2008-04-05 at 11:09 +0200, Johannes Berg wrote: > > Another unrelated bug (sorry, testing often finds unrelated bugs) is > > that scanning with specific ESSID was returning non-matching APs. I > > mean "iwlist wlan0 scan my_essid", which would still report many > > different ESSIDs. It's inconvenient when the driver can sense 22 APs at > > once :) > > Heh. I'm not sure what the desired behaviour is, if you do that scan > we'll give you everything we found but will scan actively for that > particular SSID. The man page (sigh) only says: > > This command take optional arguments, however most drivers will > ignore those. The option essid is used to specify a scan on a > specific ESSID. The option last do not trigger a scan and read > left-over scan results. > > Which isn't quite clear, but seems to match what we do. Maybe iwlist > should filter it? I tried scanning for ESSID that no AP has. Most time I only get response from one AP, which is an old Linksys BEFW11S4 v4 (802.11b only). Sometimes one or two other APs appear. But it some cases, all 22 or 23 APs in range appear in the list. The easiest way to reproduce it is to scan without ESSID and then with ESSID. Then the second scan will return all APs found in the first scan. But run the scan with the ESSID several times, and at some point the list goes down to that dumb Linksys. I'm fine with scanning without filtering. It's more important that we let users control what probe requests are being sent. But I think we should be consistent and avoid returning results of scans with different parameters. -- Regards, Pavel Roskin -- 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
