From: Jouni Malinen <jouni.malinen@atheros.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/15] ath9k: Virtual interfaces and radios
Date: Thu, 12 Mar 2009 22:19:12 +0200 [thread overview]
Message-ID: <1236889152.16569.27.camel@jm-desktop> (raw)
In-Reply-To: <200903071456.03827.florian@openwrt.org>
On Sat, 2009-03-07 at 05:56 -0800, Florian Fainelli wrote:
> I am only commenting from a user point of view this feature. This definitively
> is very useful since quite a lot of people stick to madwifi instead of using
> ath5k or ath9k since there was not real support before this patch for virtual
> interfaces.
The set of patches that went in should take care of the virtual station
side. The patch I just sent out will add multi-BSSID support for AP mode
(it will require an update to hostapd, too), so this should provide
support for quite complete set of virtual interface configurations.
> One thing that I did not like with wlanconfig and I would like not to find
> with mac80211/cfg80211 is the incompatibility of some setups (i.e: AP should
> be created first, STA interface later with nosbeacon), not sure this is
> possible, but if it is, one should be able to add a virtual interface without
> knowing the state of the other interfaces before.
The goal is certainly to be able to add and remove virtual interfaces in
any order and at any time. There may be some limitations in the current
version, i.e., something might end up not working, but the configuration
part itself is not prevented. If someone finds a sequence that does not
work, I would hope it can be resolved.
> I really like the way we can create mesh point interfaces with iw, so this
> could be the user interface to configure virtual interfaces, say like this :
>
> iw dev wlan0 interface add sta0 type sta
> iw dev wlan0 interface add ap0 type master
The multi-channel operation with virtual radio (wiphy) is at somewhat
different layer than the mesh interface (vif). Anyway, if nl80211 is
extended with a command that can be used to add a new virtual wiphy,
similar iw command could be added for this use, too. Here standard
commands (iwconfig/wpa_supplicant/hostapd) can change the interface
mode, so it does not need to be specified at wiphy creation time.
As far as multi-BSSID configuration of AP mode on the same channel is
concerned, those virtual interfaces are vifs and hostapd generates them
dynamically using the same mechanism as the iw commands above.
- Jouni
next prev parent reply other threads:[~2009-03-12 20:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 17:23 [PATCH 00/15] ath9k: Virtual interfaces and radios Jouni Malinen
2009-03-03 17:23 ` [PATCH 01/15] ath9k: Cleanup multiple VIF processing Jouni Malinen
2009-03-03 17:23 ` [PATCH 02/15] ath9k: Set BSSID mask based on configured interfaces Jouni Malinen
2009-03-03 17:23 ` [PATCH 03/15] ath9k: Add data structure for supporting virtual radio/wiphy operation Jouni Malinen
2009-03-03 17:23 ` [PATCH 04/15] ath9k: Add support for multiple secondary virtual wiphys Jouni Malinen
2009-03-03 17:23 ` [PATCH 05/15] ath9k: Configure RX filter for multi-BSSID broadcast Jouni Malinen
2009-03-03 17:23 ` [PATCH 06/15] ath9k: Virtual wiphy pause/unpause functionality Jouni Malinen
2009-03-03 17:23 ` [PATCH 07/15] ath9k: Add routines for switching between active virtual wiphys Jouni Malinen
2009-03-03 17:23 ` [PATCH 08/15] ath9k: Make start/stop operations aware of " Jouni Malinen
2009-03-03 17:23 ` [PATCH 09/15] ath9k: Register larger listen interval Jouni Malinen
2009-03-03 17:23 ` [PATCH 10/15] ath9k: Pause other virtual wiphys on channel change Jouni Malinen
2009-03-03 17:23 ` [PATCH 11/15] ath9k: Check virtual wiphy state on tx() Jouni Malinen
2009-03-03 17:23 ` [PATCH 12/15] ath9k: Add workaround to recover from failed channel changes Jouni Malinen
2009-03-03 17:23 ` [PATCH 13/15] ath9k: Special processing for channel changes during scan Jouni Malinen
2009-03-03 17:23 ` [PATCH 14/15] ath9k: Add a simple virtual wiphy scheduler Jouni Malinen
2009-03-03 17:23 ` [PATCH 15/15] ath9k: Add a debugfs interface for controlling virtual wiphys Jouni Malinen
2009-03-07 13:56 ` [PATCH 00/15] ath9k: Virtual interfaces and radios Florian Fainelli
2009-03-12 20:19 ` Jouni Malinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-10 12:43 Stephen Gutknecht (hilltx)
2009-03-10 17:03 ` Jouni Malinen
2009-03-10 17:23 ` Johannes Berg
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=1236889152.16569.27.camel@jm-desktop \
--to=jouni.malinen@atheros.com \
--cc=florian@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox