From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 4 03:04:03 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6A88A85 for ; Wed, 4 Dec 2013 03:04:03 +0000 (UTC) Received: from mail-oa0-f52.google.com (mail-oa0-f52.google.com [209.85.219.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A61D31A5F for ; Wed, 4 Dec 2013 03:04:03 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id h16so16110376oag.11 for ; Tue, 03 Dec 2013 19:03:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=7AfpMg4e7M1yO+DIS7BsCPUIl9MCfvUGLbityK2o6Zc=; b=kvK/zf836HPfhR7CWitH6dB9BQ0ISoZMLJWnc+4mXaDxVSdEUW1lmNlO2yLtxY+62f V5Tkck52Mk7la6ldXbipw3AHdf/SqMTfFs8dM7iyz1sDiZAVNUmY49BztJNtoEqmqdbW LsPWurWG9HNbJ+da0bVcGQlrDZqbTeNx22vDhYEV4xU0VJWgtoia5WWj8U7753lraAdV e4LNs433mC+QqCIrfda3Z+DbfdmpJPG/mGtwyEi3WID0n1VbPDmq61LbYIu0E56/b9Hs SYKe2YCIiciAhrSbSCHtAOfrfzUCh5FQBFrbyWdxl/4e4dfj8SPm60x++JBBDMXzjqNB Appw== X-Gm-Message-State: ALoCoQlv/NDcATxYhX5KXO85qqqlLItUAoNNbXysmeapNlq8m5G9azcSFxT3+RgbRbmsPQ24YziY X-Received: by 10.182.55.65 with SMTP id q1mr61291476obp.2.1386126237690; Tue, 03 Dec 2013 19:03:57 -0800 (PST) Received: from [172.21.0.33] (67-198-60-238.static.grandenetworks.net. [67.198.60.238]) by mx.google.com with ESMTPSA id xs17sm27142774oeb.1.2013.12.03.19.03.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Dec 2013 19:03:56 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: Channel interference scan and manual selection From: Jim Thompson In-Reply-To: Date: Tue, 3 Dec 2013 21:03:55 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <46B1EFC5-1AA4-4E51-B199-D4CDACEEA0AC@netgate.com> References: To: Adrian Chadd X-Mailer: Apple Mail (2.1822) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 03:04:04 -0000 On Dec 3, 2013, at 7:56 PM, Adrian Chadd wrote: > Now, ideally it'd actually check the channel for interference and > channel busy status, and use _that_ metric. Ideally, it would attempt to get co-channel with other APs on the same = channel. Especially in 2.4GHz (or any of the 5GHz bands). Because you would *much* rather share the air (via collision avoidance) = than raise the noise floor for someone (everyone) else. And, given that everyone has a DC receiver these days, there are NO = =93non-overlapping channels=94. jim