linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: David Acker <dacker@roinet.com>,
	Andrey Yurovsky <andrey@cozybit.com>,
	Michael Renzmann <mrenzmann@madwifi-project.org>,
	madwifi-devel@lists.sourceforge.net,
	madwifi-users@lists.sourceforge.net,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Madwifi-devel] Survey: What are you using MadWifi for, and why?
Date: Wed, 18 Nov 2009 16:58:12 -0500	[thread overview]
Message-ID: <1258581492.10593.24.camel@mj> (raw)
In-Reply-To: <43e72e890911171512k562f9329td56cc741dd1c5151@mail.gmail.com>

On Tue, 2009-11-17 at 15:12 -0800, Luis R. Rodriguez wrote:
> On Tue, Nov 17, 2009 at 2:54 PM, Jouni Malinen <j@w1.fi> wrote:
> 
> > Supporting half/quarter width channels sounds reasonable in general. The
> > main problem with this one seems to have been in getting someone
> > dedicated enough to go through the effort in a way that would cleanly
> > extend the regulatory framework in use with cfg80211.
> 
> I'll elaborate on this part.
> 
> There actually is no requirement to extend the regulatory framework to
> get this done.

I think we should try to err on the safe side when dealing with
regulations.

CRDA regulates the frequencies allocated for 802.11 protocol.  Part of
the protocol is collision avoidance using RTS/CTS.

Stations using half and quarter channels won't see standard width
control frames.  Likewise, standard stations won't be able to interpret
any narrow channel traffic.  Thus, the stations using different channel
width affect each other as dumb noise emitters, somewhat like bluetooth
and even microwave ovens.

My impression is that many new bands are allocated for 802.11 under
strict conditions, such as power limits, DFS and TPC.  TPC in particular
is designed to reduce interference between networks.

Is it true that no country limits transmissions in any band to the
standard channel width?  Can we reasonably rely on things staying that
way?

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-11-18 21:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2205.95.222.251.107.1258282369.squirrel@webmail.otaku42.de>
2009-11-17  1:01 ` [Madwifi-devel] Survey: What are you using MadWifi for, and why? Luis R. Rodriguez
2009-11-17 14:05   ` John W. Linville
2009-11-17 22:08     ` Marcel Holtmann
2009-11-17 16:04   ` Michael Renzmann
2009-11-17 16:38     ` Luis R. Rodriguez
2009-11-17 17:51       ` Tom Sharples
2009-11-17 18:05         ` Luis R. Rodriguez
2009-11-17 21:51       ` Bob Copeland
2009-11-17 23:23         ` Pat Erley
2009-11-18  7:23       ` Michael Renzmann
2009-11-17 17:40   ` David Acker
2009-11-17 20:57     ` Andrey Yurovsky
2009-11-17 21:37       ` Luis R. Rodriguez
2009-11-17 21:44         ` David Acker
2009-11-17 21:45           ` Luis R. Rodriguez
2009-11-17 21:53             ` David Acker
2009-11-17 22:04               ` Luis R. Rodriguez
2009-11-17 22:28                 ` David Acker
2009-11-17 22:39                   ` Luis R. Rodriguez
2009-11-17 23:39                     ` Tom Sharples
2009-11-17 23:44                       ` Luis R. Rodriguez
2009-11-17 22:54                   ` Jouni Malinen
2009-11-17 23:12                     ` Luis R. Rodriguez
2009-11-18 21:58                       ` Pavel Roskin [this message]
2009-11-18 22:08                         ` Luis R. Rodriguez
2009-11-18 23:05                           ` Jouni Malinen
2009-11-19  0:21                             ` Luis R. Rodriguez
2009-11-18 23:12                           ` Pavel Roskin
2009-11-19  0:05                             ` Tom Sharples
2009-11-17 22:06               ` Marcel Holtmann
2009-11-17 22:32                 ` David Acker
2009-11-17 23:22               ` Felix Fietkau
2009-11-18 15:35                 ` David Acker

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=1258581492.10593.24.camel@mj \
    --to=proski@gnu.org \
    --cc=andrey@cozybit.com \
    --cc=dacker@roinet.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=madwifi-devel@lists.sourceforge.net \
    --cc=madwifi-users@lists.sourceforge.net \
    --cc=mcgrof@gmail.com \
    --cc=mrenzmann@madwifi-project.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 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).