From: Dan Williams <dcbw@redhat.com>
To: dragoran <drago01@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
ipw3945-devel <ipw3945-devel@lists.sourceforge.net>
Subject: Re: mac80211/iwlwifi + hidden ssids
Date: Wed, 10 Oct 2007 11:07:46 -0400 [thread overview]
Message-ID: <1192028866.9739.32.camel@localhost.localdomain> (raw)
In-Reply-To: <f6ca9fed0710100757gbcd364esdd94f114cfe1019@mail.gmail.com>
On Wed, 2007-10-10 at 16:57 +0200, dragoran wrote:
> On 10/10/07, Dan Williams <dcbw@redhat.com> wrote:
> >[..]
> > wpa_supplicant's support for hidden SSIDs sort of sucks; mainly because
> > the drivers implement this in different ways. wpa_supplicant says you
> > must use "ap_scan=2" for hidden SSIDs (and possibly ssid_scan=1 to do
> > specific ssid probe requests), which causes wpa_supplicant to blast all
> > settings to the card directly and not try to be smart about AP scanning
> > and selection. However, this doesn't work often because drivers are
> > inconsistent about this.
> >
> > The way it _should_ work is that if scan_ssid = 1 for a network,
> > wpa_supplicant should ask that the driver scan the specific ssid using
> > IW_SCAN_THIS_ESSID. The card would then issue specific SSID scan
> > requests on each channel during the scan, and hopefully find the AP in
> > question.
> >
> > Unfortunately, most drivers don't support IW_SCAN_THIS_ESSID. So the
> > best we can do is set AP_SCAN=2, let wpa_supplicant blow all the
> > settings to the card, and just _hope_ that the card/driver are smart
> > enough to find the hidden SSID on their own and associate. Which is
> > less often than we'd hope.
>
> so your are suggestion to use ap_scan=2 and add scan_ssid=1 to the
> network block?
> nm seems not to do this.
It should be doing this...
> btw shouldn't all mac80211 drivers either work or not work because the
> code for this is in mac80211 and not in the drivers?
Yeah, pretty much; but each driver/firmware may handle hidden ssids
slightly differently. mac80211 should bring some sanity to this area,
but I wouldn't discount variation between even mac80211 based drivers.
Dan
> I will be able to test again this friday will try this and the
> ap_scan=1 if there are other suggestion feel free to say them so I can
> add them to my "totest" list ;)
next prev parent reply other threads:[~2007-10-10 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 9:45 mac80211/iwlwifi + hidden ssids dragoran
2007-10-10 13:06 ` John W. Linville
2007-10-10 13:47 ` dragoran
2007-10-10 14:22 ` John W. Linville
2007-10-10 14:34 ` Dan Williams
2007-10-10 14:57 ` dragoran
2007-10-10 15:07 ` Dan Williams [this message]
2007-10-10 15:20 ` John W. Linville
2007-10-10 17:41 ` Johannes Berg
2007-10-10 17:43 ` [ipw3945-devel] " Ferguson, Dana R
2007-10-10 17:54 ` Ferguson, Dana R
2007-10-10 18:10 ` John W. Linville
2007-10-10 19:28 ` Tomas Winkler
2007-10-11 4:03 ` Dan Williams
2007-10-10 15:17 ` John W. Linville
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=1192028866.9739.32.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=drago01@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox