Re: [PATCH] cfg80211: restrict AP beacon intervals

[Ben Greear <greearb@candelatech.com>]

On 05/09/2011 10:20 AM, Steve Brown wrote:
> On Mon, 2011-05-09 at 18:49 +0200, Johannes Berg wrote:
>> On Mon, 2011-05-09 at 09:46 -0700, Ben Greear wrote:
>>> On 05/09/2011 09:41 AM, Johannes Berg wrote:
>>>> From: Johannes Berg<johannes.berg@intel.com>
>>>>
>>>> Multiple virtual AP interfaces can currently try
>>>> to use different beacon intervals, but that just
>>>> leads to problems since it won't actually be done
>>>> that way by drivers. Return an error in this case
>>>> to make sure it won't be done wrong.
>>>
>>> I think there is no problem with having different beacon
>>> intervals, as long as they are all a multiple of
>>> the smallest interval and the driver does things properly.
>>>
>>> I'm not sure ath9k or ath5k currently supports this properly,
>>> but there was a patch floating around for a while that did
>>> this for ath9k I think...
>>
>> If you really care greatly about having different beacon intervals (and
>> I don't see why you would?) then maybe you can think how we can enforce
>> and advertise that to userspace. For now, I'm more comfortable just
>> restricting it.
>>
>> johannes
>
> I posted a patch for different beacon intervals to the ath9k list last
> Jan. This was to allow both a mesh (interval 1000) and ap (interval 100)
> vif on the same radio. This combination seems useful, at least for me.

Could you re-post this against latest wireless-testing?  I should
be able to do some testing on this and maybe we can get it pushed
upstream...

Ben

>
> Steve


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