linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Michael Renzmann <mrenzmann@madwifi-project.org>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	Pavel Roskin <proski@gnu.org>, Richard Farina <sidhayn@gmail.com>,
	John Linville <linville@tuxdriver.com>,
	wireless <linux-wireless@vger.kernel.org>,
	Michael Green <Michael.Green@Atheros.com>
Subject: Re: wireless-regdb: flaw in general functionality
Date: Wed, 26 Nov 2008 09:17:40 -0800	[thread overview]
Message-ID: <20081126171740.GB6515@tesla> (raw)
In-Reply-To: <1417.92.50.109.198.1227678824.squirrel@webmail.madwifi.org>

On Tue, Nov 25, 2008 at 09:53:44PM -0800, Michael Renzmann wrote:
> Hi.
> 
> Luis R. Rodriguez wrote:
> > When in a DFS freq, if you don't support DFS in your mode of operation,
> > then you cannot TX.
> 
> Side note: this behaviour is not required in all jurisdictions. German
> regulatory body for example allows use of non-DFS-compliant gear even on
> (at least some) DFS channels, but only with low TX power. Is that
> supported already?

Michael,

I reviewed this internally and there is disagreement on your statement
about German rules. Perhaps there is also a terminology disconnect
between "DFS" and "Radar Detection" and how this applies to a STA or an
AP.

For STA devices "DFS" is required for all Europe regdomains including
Germany for channels 52 to 140 inclusive. "DFS" for STAs means passive
scanning and no adhoc for STA devices (or Mesh, hence NO-BEACONING name
suggestion for the flag).

When on AP and on these channels the AP must do radar detection, in
Germany and rest of Europe and in all other regions. Radar detection
includes a bunch of required functions for APs which we won't get into
on this thread.

Perhaps you are thinking of old interim rules that applies in Germany
and elsewhere. But they no longer apply anyway in Europe.

  Luis

  reply	other threads:[~2008-11-26 17:17 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
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 [this message]
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=20081126171740.GB6515@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Michael.Green@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mrenzmann@madwifi-project.org \
    --cc=proski@gnu.org \
    --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).