From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 4 03:40:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0AE20E99 for ; Wed, 4 Dec 2013 03:40:24 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B679C1D03 for ; Wed, 4 Dec 2013 03:40:23 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id x13so1669140qcv.15 for ; Tue, 03 Dec 2013 19:40:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=axAUWpQD+H9i1Eawr4dDKs6O1/teWIzqg4NBPwZ98QA=; b=Ukyz0N3n1sUe/htWbWPHxI8y7AiCr+OeGNxNUF7d3YFjxQqFRPiXgolbvOYeMdeJDz m5i1Lrn4GHDbPDhfYKGOd4zhEvRgVw0o1oZ4L+aY9qINw39VuyI1nTGLmtaP7R2kthm4 xmhsYceebX49rxZRnFE8mdlbtRp2ZnYnMyKwDQsCV6XquuZV7brboEHs8lFc4qq1sMJ+ utTxaFl9/TBuC+SiaE9Ib+vBuq+jQe41oL+nwr/gHkZsSg3sUDnT0YG3K+qSGtQK0afn AaRYMggB9n2PIeI26xsjMBwfZlQWa2WiAXwWcyf/dDA2B+RhggFrzIzSHd41dTYFMTBi Qrsw== MIME-Version: 1.0 X-Received: by 10.229.56.200 with SMTP id z8mr131250660qcg.1.1386128422933; Tue, 03 Dec 2013 19:40:22 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Tue, 3 Dec 2013 19:40:22 -0800 (PST) In-Reply-To: References: <46B1EFC5-1AA4-4E51-B199-D4CDACEEA0AC@netgate.com> Date: Tue, 3 Dec 2013 19:40:22 -0800 X-Google-Sender-Auth: 9N3FqLGRXvtZmWtv40jk0h4LVlU Message-ID: Subject: Re: Channel interference scan and manual selection From: Adrian Chadd To: Tek Wiz Content-Type: text/plain; charset=ISO-8859-1 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:40:24 -0000 On 3 December 2013 19:32, Tek Wiz wrote: > Yes, the interference can be calculated by averaging the beacon RSSI (dB) of > the overlapping channels, e.g. for channel 6, the beacon RSSI of channels 4, > 5, 6, 7, 8 are averaged. Normally channels 1, 6, and 11 are chosen, although > other channels may have less interference, in order to be a 'good neighbor'. Sure. But we can also look at what kinds of frames we actually receive during a sample window. What I'd also like to do is finally add receive power histogram support. Ie, look at the RSSI of all the frames you receive, stick them in buckets, respond to the power histogram action request frames, use them for this.. that doesn't require any driver support. Just net80211 work in the RX path. -adrian