Comment 23 for bug 715438

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Reassigning to the linux package. Seems like the orinoco driver for this pccard wrongly reports supporting scans, and this is why NM uses ap_scan=1 rather than ap_scan=2:

        /* Check for the ability to scan specific SSIDs. Until the scan_capa
         * field gets added to wireless-tools, need to work around that by casting
         * to the custom structure.
         */
        scan_capa_range = (struct iw_range_with_scan_capa *) ⦥
        if (scan_capa_range->scan_capa & NM_IW_SCAN_CAPA_ESSID) {
                priv->has_scan_capa_ssid = TRUE;
                nm_log_info (LOGD_HW | LOGD_WIFI,
                             "(%s): driver supports SSID scans (scan_capa 0x%02X).",
                             nm_device_get_iface (NM_DEVICE (self)),
                             scan_capa_range->scan_capa);
        } else {
                nm_log_info (LOGD_HW | LOGD_WIFI,
                             "(%s): driver does not support SSID scans (scan_capa 0x%02X).",
                             nm_device_get_iface (NM_DEVICE (self)),
                             scan_capa_range->scan_capa);
        }

If the scan_capa parameter (which comes from the kernel, essentially a SIOCGIWRANGE ioctl call) returns 0x01, ap_scan=1 is used, otherwise NM uses ap_scan=2 for wpasupplicant.