<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 6/23/11 6:14 PM, Panagiotis Georgopoulos wrote:
<blockquote cite="mid:007d01cc31f2$dfa5bf50$9ef13df0$@lancs.ac.uk"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US"> I am trying to
reduce the time it takes to associate to an Access Point. I
realized that with the default wpa_supplicant settings (i.e.
ap_scan=1) there is a scan that the interface does with
probe requests to all channels before the association. This
is essentially a 800-1000 ms delay which I would like to
remove completely.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<br>
</div>
</blockquote>
I always thought the initial scan was to get an overview of what
SSIDs were available on what channels. In order to associate with a
given SSID/BSSID the driver would either need to try channels until
it found it, or do an initial scan of all channels to get an
overview. My first question would be whether the driver always
starts the scan at the same channel (presumably ch 1) or does it
start on the channel to which it has been previously set? If the
latter, and you could potentially limit the number of channels in
the scan to the single channel you know the AP is on, then it might
be a solution. I'm am no expert on this code so I'm just
shotgunning here.<br>
<br>
Marty<br>
<br>
</body>
</html>