From: Ben Hutchings <ben@decadent.org.uk>
To: linux-wireless@vger.kernel.org
Subject: IW_SCAN_CAPA_ESSID vs hidden ESSID
Date: Sun, 01 Jun 2008 22:14:44 +0100 [thread overview]
Message-ID: <1212354884.4722.26.camel@deadeye.i.decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
Since upgrading from Linux 2.6.24 to .25, I have found that
NetworkManager cannot associate my Intel wireless card, handled by the
ipw2200 driver, with my AP, which has a hidden SSID.
NetworkManager thinks that wpa_supplicant should be able to scan for
specific hidden SSIDs if the underlying driver advertises
IW_SCAN_CAPA_ESSID, which ipw2200 does since 2.6.25:
/* Use "AP_SCAN 2" if:
* - The wireless network is non-broadcast and the driver doesn't support
* scanning specific SSIDs
* - The wireless network is Ad-Hoc
* - The wireless driver does not support WPA (stupid drivers...)
*/
is_adhoc = (nm_ap_get_mode(ap) == IW_MODE_ADHOC);
if (is_adhoc || !supports_wpa)
ap_scan = "AP_SCAN 2";
else if (!nm_ap_get_broadcast (ap))
ap_scan = self->priv->has_scan_capa_ssid ? "AP_SCAN 1" : "AP_SCAN 2";
However, this doesn't work because the scan results just have an empty
string or "<hidden>" (not consistently, which is weird).
So one of these components is doing the wrong thing. Is it that:
1. ipw2200 or ieee80211 should copy the selected ESSID into scan results
2. wpa_supplicant should not check the ESSID of scan results if it has
already selected an ESSId
3. NetworkManager should not expect IW_SCAN_CAPA_ESSID to mean that this
will work
?
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-06-01 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 21:14 Ben Hutchings [this message]
2008-06-02 13:58 ` IW_SCAN_CAPA_ESSID vs hidden ESSID Dan Williams
2008-07-21 1:12 ` Ben Hutchings
2008-06-02 17:45 ` Dan Williams
2008-06-15 23:20 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1212354884.4722.26.camel@deadeye.i.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.