On Mon, Nov 02, 2015 at 06:33:45PM +0100, Michal Sojka wrote: > Can this be solved by having proper/new regulatory flags on these > channels that would prohibit running AP or scanning on these channels? I'm not sure that alone is sufficient, but yes, I think this should be done as part of the solution. On the 5.9 GHz band, cfg80211 should allow only the operations modes that are appropriate for that band. > I expect that there will be quite a lot applications/devices that will > need to communicate in this band. From technical point of view, it might > be beneficial if there is one solid implementation available in the > upstream Linux. I'm not sure about the legal point of view. I agree that it would be convenient and maybe even beneficial in the end as long as it is done in a way that meets the requirements for enforcing rules on the licensed band. > Can you image this "proper regulatory rule enforcement" as a part of > upstream Linux? Do you have an idea how it would look like? I'm not sure what would be sufficient. In general, I'm hesitant on enabling any licensed bands for Wi-Fi operations by default regardless of what the kernel configuration is. > Would kernel config option + custom regdb be sufficient? That would certainly be much closer to what I'd like to see from the regulatory enforcement view point; not sure how convenient this is to use with ath9k. I think the custom regdb route (i.e., require someone to knowingly generate the explicit rules to enable the licensed bands and only distribute the regdb with these changes to properly licensed users) was one of the approaches discussed in the past for this type of use cases. -- Jouni Malinen PGP id EFC895FA
