From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-qg0-f52.google.com ([209.85.192.52]:48081 "EHLO mail-qg0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751581AbaEVTLy (ORCPT ); Thu, 22 May 2014 15:11:54 -0400 Received: by mail-qg0-f52.google.com with SMTP id a108so6540180qge.11 for ; Thu, 22 May 2014 12:11:54 -0700 (PDT) Message-ID: <537E4C81.3060001@gmail.com> (sfid-20140522_211158_823750_17E04A7C) Date: Thu, 22 May 2014 15:14:09 -0400 From: Rick Farina MIME-Version: 1.0 To: "John W. Linville" , Ben Greear CC: "linux-wireless@vger.kernel.org" Subject: Re: Question on regulatory settings. References: <537E2ABB.6030302@candelatech.com> <537E36E3.6040205@candelatech.com> <20140522183007.GE12779@tuxdriver.com> In-Reply-To: <20140522183007.GE12779@tuxdriver.com> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 05/22/2014 02:30 PM, John W. Linville wrote: > On Thu, May 22, 2014 at 10:41:55AM -0700, Ben Greear wrote: >> On 05/22/2014 09:50 AM, Ben Greear wrote: >>> Hello! >>> >>> I'm having issues where when we add several ath10k NICs to a system, >>> the regulatory domain goes quite restricted.. There is an ath9k NIC >>> with eeprom over-ride hack, and user-space sets regdomain to 'US'. >>> >>> Later, when registering ath10k, at least one of those NICs registeres >>> as 'TW'. The ending domain looks like this: >>> >>> [root@lf1011-13060017 ~]# iw reg get >>> country 98: DFS-UNSET >>> (2402 - 2472 @ 40), (N/A, 30) >>> (5270 - 5330 @ 40), (N/A, 17), DFS >>> (5735 - 5835 @ 80), (N/A, 30) >>> >>> >>> I tried adding a hack to ath10k to zero out the ar->ath_common.regulatory.current_rd, >>> but in fact it seems to be reported as zero to begin with. >>> >>> I am obviously missing something. Either my hacks to ath10k are not >>> sufficient, or possibly the system is getting regulatory info from >>> somewhere else? >>> >>> Any ideas where else it might be getting the idea it should be in TW >>> domain? Can it get this from beacons from other systems? > > FWIW, yes it can get this information from beacons. > >> Ahh, sneaky nasty code....it was being set based on the timezone >> of all things! > > You're welcome... ;-) To be fair, when I travel I rarely set my timezone at all, and when I do I normally make sure the offset is right and not much else. It's easily possible to have timezone set for a country you aren't in just because the offset matches. I'm not saying I have a better idea, but I am saying that timezone is very unreliable to determine position. Thanks, Zero_Chaos > >> Looks like you can override this behaviour with the command >> below if you are of a mind to do so: >> >> echo COUNTRY=US > /etc/sysconfig/regdomain > > I don't know any better way to set a reasonable default for the > regulatory domain. If you have other suggestions, I'd be interested > in hearing them. > > Thanks, > > John >