linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Eduard GV <eduardgv@gmail.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	hostap@lists.shmoo.com, Matt Smith <Matt.Smith@atheros.com>
Subject: Re: Initial automatic channel selection implementation
Date: Tue, 24 May 2011 17:21:00 -0400	[thread overview]
Message-ID: <4DDC213C.1080708@gnu.org> (raw)
In-Reply-To: <BANLkTi=o5XFTK8d3B-PsKh95ELbWMuVPwA@mail.gmail.com>

On 05/24/2011 02:07 PM, Eduard GV 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).
>
> I disagree. Sometimes it is better to have adjacent channel
> interference (from partially overlapping channels) than co-channel
> interference. I could provide some references if you're interested.

My point is that we should play safe, at least when the algorithm is 
simple.  We should try to avoid the situation when our AP chooses a 
channel with no other APs but with a lot of cross-channel interference 
(either at the time of the scanning or later).

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2011-05-24 21:21 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 [this message]
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
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=4DDC213C.1080708@gnu.org \
    --to=proski@gnu.org \
    --cc=Matt.Smith@atheros.com \
    --cc=eduardgv@gmail.com \
    --cc=helmut.schaa@googlemail.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).