linux-kernel - Re: ath5k - strange regulatory domain change

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 7 Aug 2009 09:48:04 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Chris Clayton <chris2553@...glemail.com>
Cc:	Frans Pop <elendil@...net.nl>, linux-wireless@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: ath5k - strange regulatory domain change

On Fri, Aug 07, 2009 at 01:56:43PM +0100, Chris Clayton wrote:
> Thanks Frans,
> 
> 2009/8/7 Frans Pop <elendil@...net.nl>:
> > Chris Clayton wrote:
> >> Because of some problems with my Belkin Wireless G card  (model
> >> F5D7010) and the rt61pci driver, I've started to use a "no-name" card
> >> that is supported by the ath5k driver.
> >>
> >> A problem is that I have come across is that for some reason the CN
> >> regulatory domain is being set automatically. This doesn't happen with
> >> the Belkin (rt61) card. I have the following line in
> >> /etc/modprobe.d/modprobe.conf to set the regulatory domain to GB:
> >>
> >> options cfg80211 ieee80211_regdom=GB
> >
> > This issue has already been discussed extensively (after I reported it).
> > Please see the following thread: http://lkml.org/lkml/2009/7/8/421. It
> > contains a lot of information from the wireless maintainers.
> >
> 
> To sum this up then (as I understand things):
> 
> 1. I am the system administrator (root);
> 2. I am using a valid (albeit deprecated from 2.6.31) method to tell
> the wireless infrastructure that I want the regulatory domain set to
> GB;
> 3. GB is a valid code; and
> 4. the wireless infrastructure sets the regulatory domain to CN.
> 5. in 2.6.30, the wireless infrastructure does what I (the root user)
> tell it to do.
> 
> That's a regression in my book. Oh well! I do have the iw and crda
> applications installed, so I've taken that route of setting the
> regulatory domain to GB.

Are you actually getting the wrong regulatory rules enforced?  Or are
you merely bothered that it is reporting "CN" instead of "GB"?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/