Re: Cannot bring up second VAP on recent kernels?

[Ben Greear <greearb@candelatech.com>]

On 10/22/2012 03:52 PM, Ben Greear wrote:
> 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
>


Well, crap, it looks like it is this commit.  No one considered wanting
to run two hostapd processes on one wiphy :(

commit 5e760230e42cf759bd923457ca2753aacf2e656e
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Fri Nov 4 11:18:17 2011 +0100

     cfg80211: allow registering to beacons

     Add the ability to register to received beacon frames
     to allow implementing OLBC logic in userspace. The
     registration is per wiphy since there's no point in
     receiving the same frame multiple times.

     Signed-off-by: Johannes Berg <johannes.berg@intel.com>
     Signed-off-by: John W. Linville <linville@tuxdriver.com>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com