On Thu, Mar 8, 2012 at 1:59 PM, Seth Forshee <seth.forshee@xxxxxxxxxxxxx> wrote: > On Thu, Mar 08, 2012 at 11:51:03AM -0800, Luis R. Rodriguez wrote: >> On Thu, Mar 8, 2012 at 11:45 AM, Quan, David <dquan@xxxxxxxxxxxxxxxx> wrote: >> > I think there is to it more than SW. >> > Where ever you get this card, is the card tested and regulatory approved for those countries, DFS or not? >> >> Seth, what driver are you using? I know you are using a BCM43224 card. >> >> > It is possible that this card is only regulatory tested for non DFS channels, but now you enable them for passive. >> >> That's a good point. >> >> > This means that yes, you are save and not violate DFS rules because you are in passive mode. However, you are in complete violation if the STA finds an AP on that DFS channel and then connects and transmits as this STA is not allow to transmit on that channel since it is not approved. > > I was thinking about this some more. I still don't understand why it > makes sense to omit these frequencies from the world domain. Isn't the > point of geographic domains to communicate the rules for wherever the > user happens to be at the time? Yes > Does the core regulatory support really > ever know which frequencies the hardware has ben approved for, even > among those it already allows? It depends, some drivers are hacks, some drivers are vendor supported. For those driver with vendor support yes, you do know what the hardware should have been approved for. For reversed engineers drivers, no. Problem with using frequencies a card was not properly tested with is that those frequencies may not have calibrated data for it on the actual card, this may take the card out of compliance. > It seems to me that it's the job of the driver to communicate > hardware-specific regulatory hints. It is! > So _if_ passive scanning of the DFS > frequencies is allowed worldwide (I emphasize the if because I don't > know whether or not that's true), why should the world domain not allow > this? This is what I am in agreement with but you are missing that some cards do not have programmed certain frequencies on them certain calibration information. For DFS -- its a pain, and DFS is one of the areas where regulatory bodies tend to be more proactive on enforcing so the better thing to do is to avoid these at all costs -- unless the driver knows it can certainly use them. Fortunately today we get proper vendor support for all 802.11 drivers now on Linux so moving forward this is not an issue and I rather have safer and cautious code in place than not, specially for DFS. Luis -- 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
