All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Ben Greear <greearb@candelatech.com>
Cc: hostap@lists.shmoo.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] supplicant:  Enable sharing of scan results.
Date: Fri, 26 Nov 2010 22:50:02 +0200	[thread overview]
Message-ID: <20101126205002.GA4302@jm.kir.nu> (raw)
In-Reply-To: <1289950756-18452-1-git-send-email-greearb@candelatech.com>

On Tue, Nov 16, 2010 at 03:39:16PM -0800, Ben Greear wrote:
> When using multiple VIFs on the same physical radio,
> we can share scan results with sibling interfaces.
> This decreases time it takes to connect many VIFs.

Thanks! This looks reasonable. I did some cleanup and applied it.

Based on a quick test, this seemed to be able to connect over 100
station vifs using WPA2-Personal to a single AP without major problems.
Some resources are running out (just CPU?) that makes some of the 4-way
handshakes fail (timeout?), but after couple of tries, I got 116 of
124 stations connected. This is with all interfaces starting at the
same time; using some more latency there would likely make this quite a
bit more robust.

wpa_supplicant seemed to stop trying to reconnect in some cases, so this
probably triggered some bugs that need to be addressed. Anyway, manual
"wpa_cli -i<ifname> reassociate" on the missing eight vifs was able to
get all the 124 stations connected at the same time.

-- 
Jouni Malinen                                            PGP id EFC895FA

       reply	other threads:[~2010-11-26 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1289950756-18452-1-git-send-email-greearb@candelatech.com>
2010-11-26 20:50 ` Jouni Malinen [this message]
2010-11-26 21:09   ` [PATCH] supplicant: Enable sharing of scan results Ben Greear
2010-11-26 21:31     ` Jouni Malinen

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=20101126205002.GA4302@jm.kir.nu \
    --to=j@w1.fi \
    --cc=greearb@candelatech.com \
    --cc=hostap@lists.shmoo.com \
    --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.