From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [RFCv1] mac80211: Adds Software / Virtual AMP 80211
Date: Thu, 19 Apr 2012 16:39:09 +0300 [thread overview]
Message-ID: <20120419133907.GD16002@aemeltch-MOBL1> (raw)
In-Reply-To: <4F9012E9.1040409@sipsolutions.net>
Hi Johannes,
On Thu, Apr 19, 2012 at 06:28:09AM -0700, Johannes Berg wrote:
> On 4/18/2012 11:36 PM, Andrei Emeltchenko wrote:
> >>>>No, this is incorrect. If one device wants to connect on one
> >>>>channel, the other typically has to use the same channel. If one
> >>>>device wants to scan, the other will be affected. Some hardware may
> >>>>support switching around between two channels, but might also
> >>>>support more than 2 virtual interfaces, so again they won't be
> >>>>independent.
> >>>
> >>>BTW: which devices can switch channels?
> >>
> >>None today, I'm working on it.
> >
> >If this is not possible how people setup wireless hotspot using virtual
> >interfaces and run wpa_supplicant and hostapd on each separately.
> >Like here:
> >
> >http://linuxalfi.wordpress.com/2011/11/08/connectify-for-linux-with-single-wireless-interface/
>
> Of course it's possible. Are you deliberately misunderstanding me?
>
> You cannot use more than one channel today. We are changing that. To
> do good channel management, rather than hard-coding it in your
> config, you want to run a single wpa_s controlling all interfaces.
Can wpa_supplicant be an AP? I though that functionality is split to
hostap and wpa_supplicant.
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2012-04-19 13:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 12:11 [RFCv1] Draft Software/Virtual AMP80211 Andrei Emeltchenko
2012-04-10 12:11 ` [RFCv1] mac80211: Adds Software / Virtual AMP 80211 Andrei Emeltchenko
2012-04-10 12:26 ` Julian Calaby
2012-04-10 12:47 ` Andrei Emeltchenko
2012-04-10 16:39 ` Johannes Berg
2012-04-10 21:17 ` Marcel Holtmann
2012-04-10 21:20 ` Johannes Berg
2012-04-10 21:24 ` Johannes Berg
2012-04-11 7:11 ` Andrei Emeltchenko
2012-04-18 2:03 ` Johannes Berg
2012-04-18 12:15 ` Andrei Emeltchenko
2012-04-18 14:38 ` Johannes Berg
2012-04-18 14:52 ` Andrei Emeltchenko
2012-04-18 15:09 ` Johannes Berg
2012-04-18 15:39 ` Mat Martineau
2012-04-19 6:36 ` Andrei Emeltchenko
2012-04-19 13:28 ` Johannes Berg
2012-04-19 13:39 ` Andrei Emeltchenko [this message]
2012-04-19 14:21 ` Johannes Berg
2012-04-10 21:29 ` Marcel Holtmann
2012-04-11 7:05 ` Andrei Emeltchenko
2012-04-18 2:07 ` Johannes Berg
2012-04-18 11:20 ` Andrei Emeltchenko
2012-04-18 11:51 ` Marcel Holtmann
2012-04-18 12:10 ` Andrei Emeltchenko
2012-04-18 12:15 ` Marcel Holtmann
2012-04-18 12:33 ` Andrei Emeltchenko
2012-04-18 13:11 ` Marcel Holtmann
2012-04-18 13:22 ` Andrei Emeltchenko
2012-04-18 14:29 ` Marcel Holtmann
2012-04-18 15:02 ` Andrei Emeltchenko
2012-04-18 14:34 ` Johannes Berg
2012-04-18 14:56 ` Marcel Holtmann
2012-04-18 14:30 ` 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=20120419133907.GD16002@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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