Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vincent C Jones <v.jones@networkingunlimited.com>,
	Tomas Winkler <tomasw@gmail.com>,
	Brian Morrison <bdm@fenrir.org.uk>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: RE: iwl3945 problem with 2.6.25-rc9
Date: Sun, 20 Apr 2008 11:33:32 -0400	[thread overview]
Message-ID: <1208705612.5036.18.camel@localhost.localdomain> (raw)
In-Reply-To: <1208613091.26186.26.camel@johannes.berg>

On Sat, 2008-04-19 at 15:51 +0200, Johannes Berg wrote:
> > > I'll leave it up to you (collective you, not necessarily a personal
> > > you), how to best deal with associating with APs which are not
> > > broadcasting their SSIDs. I agree with you (personal you this time) that
> > > roaming around the country broadcasting those SSIDs does not seem
> > > particularly desirable. So how should the ability to connect to non SSID
> > > broadcasting APs be implemented? 
> > 
> > I would probably list, in network-manager, "I found (a) hidden
> > network(s)" and ask the user for an SSID to scan for actively at that
> > particular time, rather than trying to scan for all previously known
> > SSIDs even if those networks weren't hidden, as windows laptops (at
> > least those with Intel hardware but I haven't seen many others) seem to
> > do.
> 
> Or it could remember the BSSID and when it encounters the BSSID again
> scan it actively to see if it still has the same (albeit hidden) SSID.

That's what NM does; NM will cache the BSSIDs of previously associated
APs and use that to determine which APs to connect to automatically.

wpa_supplicant, unfortunately, doesn't use this trick when associating
(since it doesn't really store state at all), and therefore in the
hidden AP case, NM passes "ap_scan=1 + scan_ssid=1" to probe-scan the AP
that we want to connect to.  But that's still only _one_ AP being
probe-scanned, not 4...

There's likely some room for improvement in wpa_supplicant here, since
there's added latency waiting for the supplicant to do scans when NM
already knows exactly which AP/BSSID to connect to already, but we can't
push the exact SSID into the supplicant's config, because that would
cause the supplicant to only ever assocate with that AP (I _think_ so at
least) and therefore not roam correctly.

Dan

> My N810 behaves that way too, incidentally, it seems to first scan
> broadcast but if you then don't select a network quickly it starts
> scanning all networks directedly that it has previously saved.
> 
> johannes


  reply	other threads:[~2008-04-20 15:37 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 22:24 iwl3945 problem with 2.6.25-rc9 Marcus Furlong
2008-04-16 18:28 ` Chatre, Reinette
2008-04-16 19:01   ` Marcus Furlong
2008-04-16 19:26     ` Dan Williams
2008-04-16 19:48     ` Marcus Furlong
2008-04-16 20:04       ` Dan Williams
2008-04-16 21:22         ` Chatre, Reinette
2008-04-16 22:05           ` Marcus Furlong
2008-04-16 22:55             ` Chatre, Reinette
2008-04-17  0:06               ` Marcus Furlong
2008-04-18  3:03               ` Marcus Furlong
2008-04-18 21:46                 ` Chatre, Reinette
2008-04-18 21:57                   ` Johannes Berg
2008-04-18 22:12                     ` Chatre, Reinette
2008-04-18 22:23                       ` Brian Morrison
2008-04-18 22:35                         ` Chatre, Reinette
2008-04-18 22:38                           ` Brian Morrison
2008-04-18 22:37                         ` Johannes Berg
2008-04-18 22:39                           ` Johannes Berg
2008-04-19  0:28                             ` Tomas Winkler
2008-04-19  8:32                               ` Johannes Berg
2008-04-19 12:39                                 ` Vincent C Jones
2008-04-19 13:09                                   ` Johannes Berg
2008-04-19 13:44                                     ` Vincent C Jones
2008-04-19 13:48                                       ` Johannes Berg
2008-04-19 13:51                                         ` Johannes Berg
2008-04-20 15:33                                           ` Dan Williams [this message]
2008-04-20 15:24                                     ` Dan Williams
2008-04-20 20:39                                 ` Tomas Winkler
2008-04-21  0:14                                   ` Dan Williams
2008-04-21 18:39                                     ` Tomas Winkler
2008-04-21 19:20                                       ` Dan Williams
2008-04-21 20:47                                         ` Tomas Winkler
2008-04-20 15:28                         ` Dan Williams
2008-04-19  2:32                       ` Marcus Furlong
2008-04-22 23:02                         ` Chatre, Reinette
2008-04-23 13:23                           ` Marcus Furlong
2008-04-16 23:01           ` Marcus Furlong

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=1208705612.5036.18.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=bdm@fenrir.org.uk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.com \
    --cc=v.jones@networkingunlimited.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