From: Joerg Pommnitz <pommnitz@yahoo.com>
To: linux-wireless@vger.kernel.org
Subject: RE: RFC: Regulatory info in mac80211
Date: Wed, 6 Jun 2007 03:00:18 -0700 (PDT) [thread overview]
Message-ID: <645600.8486.qm@web51404.mail.re2.yahoo.com> (raw)
Larry Finger wrote:
> 1. The regulatory information is too dynamic to be placed in the kernel.
And not all regulatory information is public: as I wrote in a previous message:
I work for a company that has special regulatory permission to use channels
outside those freely available with tx power of up to 4W. This is a legitimate
use case that should not be forbidden by a new regdomain framework (I can always
hack around this, but that's just a hack, not a clean solution).
Regarding a user space daemon: keep in mind special use cases like NFSroot over WLAN.
> 2. The regulatory database should be in an ASCII file for easy updating. This database should be
> read by a userspace daemon that reformats the information and supplies it to mac80211 upon demand.
OK.
> 3. There should be some sort of checking to verify that the database has not been hacked to modify
> transmission power, etc. in an illegal manner. Obviously, no foolproof means of enforcing this does
> not exist; however, we should prevent the crudest form of modifications.
Define "illegal manner". For me it is perfectly legal to use channel 14 in Europe with 4W tx power. I admit that this is a
special interest, but nonetheless perfectly legal.
--
Regards
Joerg
__________________________________ Yahoo! Clever - Der einfachste Weg, Fragen zu stellen und Wissenswertes mit Anderen zu teilen. www.yahoo.de/clever
next reply other threads:[~2007-06-06 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 10:00 Joerg Pommnitz [this message]
2007-06-06 11:41 ` RFC: Regulatory info in mac80211 Johannes Berg
2007-06-06 13:46 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2007-06-06 12:14 Joerg Pommnitz
2007-06-05 20:51 Larry Finger
2007-06-05 23:35 ` Luis R. Rodriguez
2007-06-05 23:54 ` Iñaky Pérez-González
2007-06-06 4:18 ` Dan Williams
2007-06-07 7:10 ` Stefano Brivio
2007-06-07 18:52 ` Luis R. Rodriguez
2007-06-07 19:27 ` stefano.brivio
2007-06-07 21:35 ` Luis R. Rodriguez
2007-06-09 3:50 ` Daniel Drake
2007-06-11 2:44 ` Larry Finger
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=645600.8486.qm@web51404.mail.re2.yahoo.com \
--to=pommnitz@yahoo.com \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.