On Sun, 2014-02-02 at 19:20 +0000, Peer, Ilan wrote: > I do not think that this will be needed, as current wpa_supplicant > logic is not aware of the GO_CONCURRENT and INDOOR_ONLY flags (leaving > them ignored) and does not allow instantiating an AP/GO on channels > marked with NO_IR. In addition as this feature must be enabled under > CONFIG_ONUS, I expect that whoever uses it uses know what's is doing. Ok, thanks for the clarification. I wasn't sure how existing wpa_s versions would treat this. > 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 - all will be fine If wpa_s is broken, then at the time that the CSA actually kicks in the GO would be stopped, since it didn't switch channel, but I don't think there's a need for any additional flags. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
