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


On Thu, 09 Sep 2010 15:03:40 -0700, Ben Greear <greearb@candelatech.com>
wrote:
> With the patch below against latest wireless-testing, I can create two
> STA on the same ath9k phy0 and have them send traffic to each other.
> I tested only un-encrypted STAs at this point.

After connecting them to the same AP, presumably?

> It seems the tx logic hangs after a bit, so there are still issues, but
> I'm not sure if that is something introduced by my patch or some
> existing ath9k bug.
> 
> Please let me know if this is a viable approach.

> +       /* If we have more than one virtual station, turn on
PROMISC_IN_BSS
> +        *  --Ben
> +        */
> +       list_for_each_entry_rcu(sdata, &local->interfaces, list) {
> +               if (!sdata->dev || !netif_running(sdata->dev))
> +                       continue;
> +
> +               if (sdata->vif.type == NL80211_IFTYPE_STATION) {
> +                       avifs++;
> +                       if (avifs > 1)
> +                               break;
> +               }
> +       }
> +       if (avifs > 1)
> +               new_flags |= FIF_PROMISC_IN_BSS;
> +

This seems weird. Why do you need to be *promisc* within a given
BSS if you are multiple stations? You already have two MAC addrs
that you need to accept, so that should be fine, i.e. you don't
need to be promisc in the BSS. If ath9k needs to, it should be in
the driver. So NAK on this change for sure.

> @@ -440,7 +440,7 @@ int sta_info_insert_rcu(struct sta_info *sta)
> __acquires(RCU)
> 
>          spin_lock_irqsave(&local->sta_lock, flags);
>          /* check if STA exists already */
> -       if (sta_info_get_bss(sdata, sta->sta.addr)) {
> +       if (sta_info_get(sdata, sta->sta.addr)) {

I don't understand this change. These functions are the same
if sdata is in managed mode.

johannes

  reply	other threads:[~2010-09-09 22:51 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 [this message]
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

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=7fa0decef9a717c1562ee155bba78ce9@localhost \
    --to=johannes@sipsolutions.net \
    --cc=greearb@candelatech.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 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).