Specific hidden network scan failure

Jouni Malinen j
Tue Aug 18 15:44:28 PDT 2015

On Tue, Aug 18, 2015 at 10:01:36PM +0000, Nicola Smaldone wrote:
> And this is the scan sequence for a specific hidden ssid, let's say "mynet" on channel 3:
> 1. wpa_cli -iwlan0 remove_network 0
> 2. wpa_cli -iwlan0 add_network
> 3. wpa_cli -iwlan0 set_network 0 scan_freq 2422
> 4. wpa_cli -iwlan0 set filter_ssids 1
> 5. wpa_cli -iwlan0 ap_scan 1
> 6. wpa_cli -iwlan0 set_network 0 ssid '"mynet"'
> 7. wpa_cli -iwlan0 set_network 0 scan_ssid 1
> 8. wpa_cli -iwlan0 scan

That network block 0 is not enabled. It would need to be enabled (e.g.,
"set_network 0 disabled 0") for the SSID to be used in a scan.
Furthermore, that final scan command is not a single channel scan nor
does it use that scan_ssid information. scan_freq and scan_ssid are used
only if wpa_supplicant is triggering a scan on its own during a
connection attempt (e.g., SELECT_NETWORK or REASSOCIATE with that
network block enabled).

Please also note that with the current development snapshot, you can
also run such a scan with a command like "SCAN freq=2422 ssid
6d796e6574" without having to add the network block for it just for the
purpose of scanning.

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list