[PATCH] hostap: Allow disabling pri-sec channel switch.
Ben Greear
greearb
Tue Oct 13 09:46:43 PDT 2015
On 10/12/2015 01:48 PM, Jouni Malinen wrote:
> On Mon, Oct 12, 2015 at 08:51:33AM -0700, greearb at candelatech.com wrote:
>> This is helpful when running multiple different vAP on the
>> same radio, in different modes. If a vap0 starts in /a mode on channel
>> 149, then a second vap1 in / mode cannot be switching around the primary
>> channel as it normally might try to do.
>
> I will not add configuration parameters that can be used to disable
> mandatory 20/40 MHz coexistence rules in the standard. The use case you
> describe here seems to be something very special where the "conflict"
> would be with another virtual interface of the same radio. I'm not sure
> why this type of combination would be used and why the primary channel
> could not be on the same channel as the 20 MHz channel. There would need
> to be significantly more justification for something like this to be
> acceptable and the changes would likely need to be constraint to apply
> only for the case of two local virtual interface instead of applying to
> any case where other devices in radio range need coexistence actions to
> be taken.
>
Ok, thanks for the feedback.
In my case, it appears there must be an AP at the edge of our range because
sometimes vAP want to switch channels, and sometimes not. I do not have any good
way to automate configuring the vAP to work together well when some vAP may
switch channels, as far as I can tell.
I can understand why you would not want it upstream though.
Thanks,
Ben
--
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
More information about the Hostap
mailing list