From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Cannot bring up second VAP on recent kernels?
Date: Tue, 23 Oct 2012 09:21:23 +0200 [thread overview]
Message-ID: <1350976883.10322.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5085D66C.3060307@candelatech.com> (sfid-20121023_012747_100309_DEBCD1EF)
On Mon, 2012-10-22 at 16:27 -0700, Ben Greear wrote:
> Well, crap, it looks like it is this commit. No one considered wanting
> to run two hostapd processes on one wiphy :(
I'm not sure why you'd want to? It'll work just as well with a single
process, and *you* were the one who was so concerned about userspace
overhead first ;-)
You could fall back to monitor mode AP implementation?
johannes
prev parent reply other threads:[~2012-10-23 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 20:20 Cannot bring up second VAP on recent kernels? Ben Greear
2012-10-22 21:19 ` Felix Fietkau
2012-10-22 21:26 ` Ben Greear
2012-10-22 21:45 ` Felix Fietkau
2012-10-22 22:52 ` Ben Greear
2012-10-22 23:27 ` Ben Greear
2012-10-23 7:21 ` Johannes Berg [this message]
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=1350976883.10322.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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 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.