linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RFC:  Allow multiple STA connected to same AP.
Date: Fri, 10 Sep 2010 09:52:51 -0700	[thread overview]
Message-ID: <4C8A6263.5020306@candelatech.com> (raw)
In-Reply-To: <848696fe638aa1c29d8420fc9186fee9@localhost>

On 09/10/2010 09:37 AM, Johannes Berg wrote:
>
> On Thu, 09 Sep 2010 21:52:31 -0700, Ben Greear<greearb@candelatech.com>
> wrote:
>
>> After some more debugging, it seems at least part of the problem is that
>> ath9k uses ieee80211_iterate_active_interfaces_atomic to determine which
>> MACs to add to the BSSID mask.  But, before things are associated
> properly,
>> sdata isn't 'running', so ath9k doesn't calc the mask properly.
>>
>> Looks a bit like chicken-and-egg issue, and for some reason, it doesn't
>> seem to happen with WPA (but then, WPA doesn't authenticate properly
>> either).
>>
>> Maybe a new iterator is needed to get interfaces that want to go active
>> (maybe by determining if sdata->dev is 'UP') ?
>
> Err, that's exactly what the active interfaces iterator does. sdata is
> in fact 'running' as soon as the interface is UP.

Maybe that bssidmask logic runs before sdata is actually brought up
then.  I'll keep poking at things.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2010-09-10 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 22:03 RFC: Allow multiple STA connected to same AP Ben Greear
2010-09-09 22:51 ` Johannes Berg
2010-09-09 23:01   ` Ben Greear
2010-09-09 23:08     ` Johannes Berg
2010-09-10  4:52       ` Ben Greear
2010-09-10 16:37         ` Johannes Berg
2010-09-10 16:52           ` Ben Greear [this message]

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=4C8A6263.5020306@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).