From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Richard Farina <sidhayn@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless-regdb: flaw in general functionality
Date: Mon, 24 Nov 2008 15:12:04 -0800 [thread overview]
Message-ID: <20081124231204.GN6245@tesla> (raw)
In-Reply-To: <492B2B74.7040404@gmail.com>
On Mon, Nov 24, 2008 at 02:32:20PM -0800, Richard Farina wrote:
> First of all I would like to say that the entire idea and function
> behind crda is vastly improved from the old regulatory settings hard
> coded in the kernel. In light of this, however, we all seem to be
> avoiding a very clear part of reality.
>
> crda and the regulatory database restrain the channels that a person can
> legally transmit on based on their (presumed) current regulatory
> legislation. Unfortunately, when I learned about radios I was taught
> that radios can RECEIVE as well as transmit. In fact, in the USA (the
> country I live in and hence where I am most familiar with the laws) it
> is 100% legal to monitor any frequency that you desire. crda clearly
> misses that fact and doesn't permit proper legal operation of the radio
> device.
>
> crda and the regulatory database should be modified so that I can use my
> cards in the legal manner prescribed by the FCC (my regulatory body here
> in the USA).
The reguluatory database is designed with 802.11 in mind, its database
also provides enablement on frequency, not disablement. By default
cfg80211 disallows everything except what is listed for the current
regulatory domain being used.
Your point about not being able to listen is a good one, and a patch to
update the the US in consideration of part 15 rules would be
appreciated. Keep in mind we have flags for such things:
-Passive scan
-No-IBSS
We should probably rename no-ibss to no-beaconing though as that is the
real meaning inention behind it.
Luis
next prev parent reply other threads:[~2008-11-24 23:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 22:32 wireless-regdb: flaw in general functionality Richard Farina
2008-11-24 23:12 ` Luis R. Rodriguez [this message]
2008-11-24 23:21 ` Pavel Roskin
2008-11-24 23:26 ` Luis R. Rodriguez
2008-11-25 2:26 ` Richard Farina
2008-11-25 2:31 ` Pavel Roskin
2008-11-26 0:19 ` Luis R. Rodriguez
2008-11-26 0:35 ` Pavel Roskin
2008-11-26 1:02 ` Luis R. Rodriguez
2008-11-26 3:10 ` Richard Farina
2008-11-26 17:05 ` Luis R. Rodriguez
2008-11-26 5:53 ` Michael Renzmann
2008-11-26 17:17 ` Luis R. Rodriguez
2008-11-26 19:55 ` Michael Renzmann
2008-11-26 20:04 ` Johannes Berg
2008-11-27 5:26 ` Michael Renzmann
2008-11-26 17:19 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081124231204.GN6245@tesla \
--to=lrodriguez@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sidhayn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).