<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br>Thank very much for precise clarification.<BR> <BR>Best Regards,<br>
k.sunder<br> <BR><div>> Date: Wed, 7 Oct 2015 23:14:42 +0300<br>> From: j@w1.fi<br>> To: sunder_k@hotmail.com<br>> CC: avinashapatil@gmail.com; hostap@lists.shmoo.com<br>> Subject: Re: Non-DFS channel<br>> <br>> On Wed, Oct 07, 2015 at 06:18:13PM +0000, sunder wrote:<br>> > Issue :<br>> > A 11ac card came up with wlan0. Linux kernel 3.18 and ath10 were used.<br>> > The country code is set, say US. <br>> > <br>> > If 11ac card can find APs beaconing in the channels 5180 MHz [36], 5200 MHz [40], 5220 MHz [44], 5240 MHz [48] during its scanning using iw tool. The NO IR will get eliminated regulatory domain setting and it can start as 11ac AP with 80MHz. <br>> > <br>> > Assume, an isolated area, where there is no AP with 5GHz near vicinity. In that case, it cannot start the network.<br>> <br>> Assuming this WLAN card has been provisioned for world roaming and not<br>> for a specific country (which is likely the case for station products),<br>> this behavior is correct and expected. No user action is supposed to<br>> allow it to set up an AP on a "no IR" channel without there being<br>> sufficient external information to allow the constraint to be lifted.<br>> <br>> In any case, this is not really in scope for the hostap mailing list as<br>> this is a driver enforced constraint and something that seems to be<br>> there by design if I understood the card configuration correctly.<br>> <br>> -- <br>> Jouni Malinen PGP id EFC895FA<br></div> </div></body>
</html>