hostapd error

[Ann Lo]

In my case, the same radio is used by client and AP. When the client
switches to a different channel, AP should follow and use the same
channel. It helps to have a way to ensure that AP does use this
channel.

Thanks,
Ann

On Mon, Mar 28, 2016 at 12:10 PM, Ben Greear <greearb at candelatech.com> wrote:
> On 03/27/2016 10:35 AM, Jouni Malinen wrote:
>>
>> On Sat, Mar 26, 2016 at 08:51:30AM -0700, Ben Greear wrote:
>>>
>>> That would not fix the case where you want to:
>>>
>>> create 80Mhz AP on CH 36  #  Might want to change primary channel
>>> create 20Mhz AP on CH 36  #  Cannot change primary channel.
>>>
>>> When 80Mhz AP is created, no other vif exists, so it has no way to know
>>> it cannot change primary channel.
>>
>>
>> If you know that you want both of those BSSes, you'd simply start the
>> second one first. If you do not know about the second one in the
>> beginning and start the first one first, you'll need to meet the
>> constraints on the primary/secondary channel.
>
>
> My system, at least, is dynamic, and I do not want to restart existing
> AP vifs if user adds or modifies a second one.  I'm building test equipment,
> so doing exactly what the user asks, as much as possible, is more important.
>
> Forcing the system to use the requested channel configuration falls under
> this category in my opinion.
>
>> I don't see how this would be of any justification against automatically
>> detecting local constraints when starting new BSSes while I see not much
>> chances of getting the configuration parameter accepted.
>
>
> Taking local constraints into account would probably be an improvement
> either way.  It would at least work more often, even if it doesn't actually
> fix *my* case.
>
> I don't know Ann's exact limitations, so possibly what you suggest would
> work
> for her.
>
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>