linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com>
Cc: hostap@lists.shmoo.com, linux-wireless@vger.kernel.org
Subject: Re: Initial automatic channel selection implementation
Date: Tue, 24 May 2011 13:04:56 -0400	[thread overview]
Message-ID: <4DDBE538.1090902@gnu.org> (raw)
In-Reply-To: <1105241841310.6936@somehost>

On 05/24/2011 12:44 PM, Cristian Ionescu-Idbohrn wrote:
> On Tue, 24 May 2011, Pavel Roskin wrote:
>>
>> Speaking of channels, I think only some channels should be eligible for
>> automatic selection (that would be 1, 6 and 11 in the 2.4 GHz range).
>
> May I ask what the rationale behind that may be?

That's a safe distance between channels.  That's why channels 1, 6 and 
11 are used more often than others.

Our algorithm make select, say, channel 3.  That may be the most quiet 
channel at the moment.  We may use absolutely the best algorithm to 
determine that.  However, it is likely that APs operating on channels 1 
and 6 would eventually appear in vicinity, and out AP would interfere 
with both of them instead of just one of them.

Using a car analogy, consider channels 1, 6 and 11 like lanes on a 
highway.  Using other channels would be like driving between lanes.  It 
may seem safe, but only in absence of other traffic.

It's possible that the list of autoselectable channels could be country 
specific.  I would hate to add complexity to CRDA.  Hopefully we could 
device a simple algorithm to find the autoselectable channels based on 
the CRDA data.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2011-05-24 17:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 12:48 Initial automatic channel selection implementation Luis R. Rodriguez
2011-05-24 14:27 ` Helmut Schaa
2011-05-24 18:07   ` Eduard GV
2011-05-24 21:21     ` Pavel Roskin
2011-05-24 22:54   ` Luis R. Rodriguez
2011-05-25 12:19     ` Helmut Schaa
2011-05-25 14:37       ` Luis R. Rodriguez
2011-05-25 14:45         ` Helmut Schaa
2011-05-25 15:01           ` Luis R. Rodriguez
2011-05-25 19:20             ` Felix Fietkau
2011-05-25 19:24               ` Luis R. Rodriguez
2011-05-25 19:27                 ` Luis R. Rodriguez
2011-05-25 20:01                   ` Luis R. Rodriguez
2011-05-26 10:45                   ` Felix Fietkau
2011-05-26 23:45                     ` Luis R. Rodriguez
2011-05-27  0:23                       ` Felix Fietkau
2011-05-27  0:59                         ` Luis R. Rodriguez
2011-06-02 22:36                           ` Luis R. Rodriguez
2011-06-02 23:49                             ` Felix Fietkau
2011-06-03  5:23                               ` Luis R. Rodriguez
2011-05-26  7:37         ` Jouni Malinen
2011-05-24 15:28 ` Pavel Roskin
2011-05-24 16:44   ` Cristian Ionescu-Idbohrn
2011-05-24 17:04     ` Pavel Roskin [this message]
2011-05-25  4:24       ` Helmut Schaa
2011-05-25  4:39         ` Adrian Chadd
2011-05-25  8:08         ` Cristian Ionescu-Idbohrn

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=4DDBE538.1090902@gnu.org \
    --to=proski@gnu.org \
    --cc=cristian.ionescu-idbohrn@axis.com \
    --cc=hostap@lists.shmoo.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 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).