> > Such logic might be needed if kernel enforces regulatory compliance
> > after the GO_CONCURRENT relaxation conditions are no longer met
> > (station interface leaves the channel), where if such a case is true,
> > it would be appropriate to add an indication to the kernel telling it
> > that user space knows what it's doing, so the kernel will not do any
> > quiescing logic (similar to what Luis suggested).
>
> I'm not convinced that is necessary - the "quiescing" would be good I
> suppose, but there should be plenty of time before it for userspace to
> request an appropriate CSA so I don't think any additional flag is needed.
>
> Assuming we're talking about the same scenario? I guess it should be like
> this:
>
> - STA connected to AP on an "additional" channel
> - GO operating on the same channel
> - AP starts to advertise CSA
> - wpa_s will request CSA for GO as well
This also requires a fix, as currently the wpa_supplicant is not aware of the station switching channel due to AP's CSA.
> - all will be fine
Yes. The wpa_supplicant should be aware of the current usage of the channels and act accordingly, i.e., if the GO is established on a channel due to GO_CONCURRENT relaxation, it should evacuate the channel once there is no station on that channel (or on that UNII band). I'm currently enabling this logic in the wpa_supplicant.
Regards,
Ilan.
��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
