From: Pat Erley <pat-lkml@erley.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Witold Sowa <witold.sowa@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Till Kamppeter <till.kamppeter@gmail.com>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
lsb-discuss@lists.linux-foundation.org
Subject: Re: Linux wireless GSoC 2010 project ideas
Date: Mon, 01 Feb 2010 23:25:27 -0500 [thread overview]
Message-ID: <4B67A937.70406@erley.org> (raw)
In-Reply-To: <20100201221252.GA30758@emergent.ellipticsemi.com>
On 02/01/10 17:12, Nick Bowler wrote:
> On 22:14 Mon 01 Feb , Maxim Levitsky wrote:
>> 2 - Allow a wireless card to associate to several APs at once (if they
>> share the frequency).
>> Implement this at least for ath5/9k. Madwifi had that feature. Maybe
>> ath9k has. If it has that feature, test it.
>
> I haven't actually tried this particular case, but this is ostensibly
> already supported by mac80211: iw allows you to create several wireless
> interfaces that share a phy, which can then be configured into different
> modes (I've used station + monitor successfully in the past).
>
With ath9k I have used:
AP + MP
AP + STA
AP + AP (Open and WPA2)
using both the debug interface to ath9k's internal multi-vif support
(never tested MP with ath9k multi-vif) and mac80211. I know that
if you use the ath9k internal method, you can operate on multiple
channels at a sacrifice to throughput. I have not tested if mac80211
supports multiple channels.
It's as easy as:
AP+MP and AP+STA:
Start Hostapd
Create interface with iw
use second interface.
AP+AP
Configure hostapd for multiple bss
start hostapd
Pat Erley
next prev parent reply other threads:[~2010-02-02 4:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 21:38 Linux wireless GSoC 2010 project ideas Luis R. Rodriguez
2010-01-28 22:06 ` Till Kamppeter
2010-01-28 22:14 ` Luis R. Rodriguez
2010-02-04 4:52 ` Hin-Tak Leung
2010-02-17 17:07 ` [lsb-discuss] " Alexey Khoroshilov
2010-01-28 23:15 ` Frederic Weisbecker
2010-01-28 23:23 ` Luis R. Rodriguez
2010-01-28 23:31 ` Greg KH
2010-01-28 23:41 ` Frederic Weisbecker
2010-01-28 23:51 ` Till Kamppeter
2010-03-09 22:43 ` Frederic Weisbecker
2010-03-12 8:12 ` Till Kamppeter
2010-03-18 3:40 ` Frederic Weisbecker
2010-03-12 8:59 ` Till Kamppeter
2010-03-12 9:38 ` [lsb-discuss] " Denis Silakov
2010-03-12 9:57 ` Till Kamppeter
2010-03-21 19:49 ` Frederic Weisbecker
2010-01-31 21:03 ` Witold Sowa
2010-01-31 21:20 ` Johannes Berg
2010-02-01 18:01 ` Luis R. Rodriguez
2010-02-01 20:14 ` Maxim Levitsky
2010-02-01 20:17 ` david
2010-02-01 21:31 ` Maxim Levitsky
2010-02-03 9:23 ` Holger Schurig
2010-02-01 22:12 ` Nick Bowler
2010-02-02 4:25 ` Pat Erley [this message]
2010-02-03 9:25 ` Holger Schurig
2010-02-03 14:24 ` pat-lkml
2010-02-03 18:48 ` Luis R. Rodriguez
2010-02-05 5:16 ` Pat Erley
2010-02-05 15:49 ` Luis R. Rodriguez
2010-02-04 8:32 ` Kalle Valo
2010-02-04 22:36 ` Pat Erley
2010-02-22 21:25 ` Luis R. Rodriguez
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=4B67A937.70406@erley.org \
--to=pat-lkml@erley.org \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lsb-discuss@lists.linux-foundation.org \
--cc=maximlevitsky@gmail.com \
--cc=mcgrof@gmail.com \
--cc=till.kamppeter@gmail.com \
--cc=witold.sowa@gmail.com \
/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.