From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: Allow scanning single channel if other VIF is associated.
Date: Tue, 28 Sep 2010 17:18:40 +0200 [thread overview]
Message-ID: <1285687120.3885.20.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4CA206F0.40607@candelatech.com>
On Tue, 2010-09-28 at 08:17 -0700, Ben Greear wrote:
> > You can run all networks in a single wpa_s instance, I believe, and then
> > it'd know about all this, right?
>
> But then, if you want to add an additional interface, you have to restart
> everything.
Well, you can add it dynamically over dbus or the unix socket control
interface.
> I was thinking that maybe I could keep the logic in wpa_s, but instead of
> all the special casing, just locate the current associated channel for the
> phy in question and populate the scan-req with that single channel.
>
> Then, I think I wouldn't have to muck with much of the scan logic..just
> a bit of code on the entry point to select the proper channel.
>
> Does that sound like a possible solution to you?
I don't care all that much, but I really don't like the in-kernel
workaround. For that, you'd have to iterate over "iw <wlanX> link" I
suppose.
johannes
next prev parent reply other threads:[~2010-09-28 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 0:07 [PATCH 1/2] ath9k: Check for identical channels when changing channels greearb
2010-09-28 0:07 ` [PATCH 2/2] mac80211: Allow scanning single channel if other VIF is associated greearb
2010-09-28 7:22 ` Johannes Berg
2010-09-28 13:50 ` Ben Greear
2010-09-28 13:57 ` Johannes Berg
2010-09-28 15:17 ` Ben Greear
2010-09-28 15:18 ` Johannes Berg [this message]
2010-09-29 5:48 ` Jouni Malinen
2010-09-29 15:27 ` Ben Greear
2010-09-28 8:51 ` [PATCH 1/2] ath9k: Check for identical channels when changing channels Felix Fietkau
2010-09-28 13:37 ` Ben Greear
2010-09-28 14:05 ` Felix Fietkau
2010-09-28 15:22 ` 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=1285687120.3885.20.camel@jlt3.sipsolutions.net \
--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).