linux-kernel - Re: [cfg80211 / iwlwifi] setting wireless regulatory domain doesn't work.

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]

Message-ID: <CAB=NE6V-RSnqbAC-0tfYK=WGJLp1aPC2UpFDurs49h+wXr9UfQ@mail.gmail.com>
Date:	Wed, 11 Dec 2013 16:38:13 +0100
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	Sander Eikelenboom <linux@...elenboom.it>
Cc:	"Berg, Johannes" <johannes.berg@...el.com>,
	"Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: [cfg80211 / iwlwifi] setting wireless regulatory domain doesn't work.

On Wed, Dec 11, 2013 at 4:17 PM, Sander Eikelenboom
<linux@...elenboom.it> wrote:
> Since i haven't got a response to this yet and after having the troubled machine back:
> The problem is still present in linux 3.13-rc3

Keep in mind regulatory hints for Intel or Atheros cards do nothing
other than help compliance further given that the cards already have
their own regulatory data, the user input / hint is only going to
reduce the card's channels further. That said the fact that you are
not seeing a regulatory domain being set is an issue provided you have
CRDA installed or use CONFIG_CFG80211_INTERNAL_REGDB. Keep in mind
that the latest version of wireless-regdb had a signature issue
reported by users and not sure if that is cleared yet, so that would
also prevent the wireless-regdb being read even if CRDA was present.
To rule that out try putting the db.txt into net/wireless/db.txt and
compile with CONFIG_CFG80211_INTERNAL_REGDB for now.

Then send the dmesg output, no need for all that fluffy intel debug
log as its not useful in this case.

  Luis
--
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/