From: Ben Greear <greearb@candelatech.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Cannot bring up second VAP on recent kernels?
Date: Mon, 22 Oct 2012 15:52:09 -0700 [thread overview]
Message-ID: <5085CE19.2000505@candelatech.com> (raw)
In-Reply-To: <5085BE64.6030802@openwrt.org>
On 10/22/2012 02:45 PM, Felix Fietkau wrote:
> On 2012-10-22 11:26 PM, Ben Greear wrote:
>> On 10/22/2012 02:19 PM, Felix Fietkau wrote:
>>> On 2012-10-22 10:20 PM, Ben Greear wrote:
>>>> Anyone successfully using more than one virtual AP on
>>>> 3.3 or higher kernels? It works fine for me on 3.0.32,
>>>> but my 3.3.8 and 3.5.7 kernels (and a few similar ones)
>>>> all fail with errors like this below:
>>>>
>>>> Hardware is ath9k 3x3 9380 NIC.
>>> Are you using one hostapd instance per vap, or one hostapd instance for
>>> all of them?
>>
>> One hostapd per VAP.
> I had issues with that a long time ago. Use one hostapd instance for all
> vaps on the same wiphy, that'll work better.
Well, that would be a lot of user-space churn for me, so I think
I'll try to figure out why it's failing and see if I can fix it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-10-22 22:52 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 [this message]
2012-10-22 23:27 ` Ben Greear
2012-10-23 7:21 ` 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=5085CE19.2000505@candelatech.com \
--to=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.