linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Farina <sidhayn@gmail.com>
To: John Linville <linville@tuxdriver.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: wireless-regdb: flaw in general functionality
Date: Mon, 24 Nov 2008 17:32:20 -0500	[thread overview]
Message-ID: <492B2B74.7040404@gmail.com> (raw)

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).

Thanks,
Rick Farina

PS> those of you that are warming up to tell me "it's not legal to 
monitor cell phones" please save the key strokes.  It is not legal to 
modify, buy, sell or create a device that can monitor cell phones, if 
you already own one then it is legal to use, as it always has been and 
always will be. (FYI I've not found a device yet that can hit the cell 
phone bands.) Long ago it was promised that the FCC would never make 
listening against the law, surprisingly they have kept their promise so far.

             reply	other threads:[~2008-11-24 22:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 22:32 Richard Farina [this message]
2008-11-24 23:12 ` wireless-regdb: flaw in general functionality Luis R. Rodriguez
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=492B2B74.7040404@gmail.com \
    --to=sidhayn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).