From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 29 13:46:40 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD402106566B for ; Sun, 29 Apr 2012 13:46:40 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 49B638FC14 for ; Sun, 29 Apr 2012 13:46:40 +0000 (UTC) Received: by lagv3 with SMTP id v3so1925790lag.13 for ; Sun, 29 Apr 2012 06:46:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=wzBvPSsXhSDFEbM7hQYQmM5HJeLkWqI4T58mwLImjP8=; b=d+C9S1r2EHMo54NgUSW0MWoMK6vce4/P+QEmFE6m71VSrKQibnMhiJfXp2b/zezbCV ird+Uq2eZ6+dmaGDTpPcfZI6c5wZ4GdblyIrZPkI7yaF2NooNmcABBvbbDxp8d0SB/ap fSMEL+MjzPAMzWQ/vCaSY8XoR9oA7Wm2rivvQss3zhOyS1QLL0EGsP5OtFAAmgEFMyAC r++hG389HEbdwt/2t/p9hqRqu9CxrnZV7RnU6xgQzlzjtlwvk9JYZPxHmRpOruPqh5M9 XDPeGY2y6QopjoAAqM03tKkF8SeGphSiN795pa0yjjPkYeNuZ08ryoSWG4gQTkm1J9Bc iztg== MIME-Version: 1.0 Received: by 10.112.17.233 with SMTP id r9mr8491667lbd.67.1335707199058; Sun, 29 Apr 2012 06:46:39 -0700 (PDT) Sender: bschmidt@techwires.net Received: by 10.152.122.145 with HTTP; Sun, 29 Apr 2012 06:46:39 -0700 (PDT) X-Originating-IP: [88.65.53.6] In-Reply-To: <665189217.20120429172958@serebryakov.spb.ru> References: <665189217.20120429172958@serebryakov.spb.ru> Date: Sun, 29 Apr 2012 15:46:39 +0200 X-Google-Sender-Auth: nfDxqNQcwQHU8MT9XpzobKrYzTQ Message-ID: From: Bernhard Schmidt To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkjcGsq3KqkMi39FQqTRIDRqa08LBLIkpTnbqrgyShhxTvGGhfHRRJz/l/uCD9/uc7rrDi6 Cc: freebsd-wireless@freebsd.org Subject: Re: AP automatic channel selection? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 29 Apr 2012 13:46:40 -0000 On Sun, Apr 29, 2012 at 15:29, Lev Serebryakov wrote: > Hello, Freebsd-wireless. > > =A0Is =A0it possible to implement automatic channel selection by AP, with > =A0ath driver? > > =A0Some SOHO routers have such functionality. > > =A0I mean, that =A0card =A0could =A0monitor =A0channels =A0activity =A0li= ke =A0new > =A0"athsurvey" tool does, say, one per minute, and switch to channel > =A0which was least busy for, say, last 10 minutes. It should not switch > =A0more often tan same 10 minutes (all configurable) in any case. > > =A0It seems, that in my environment, channels' occupation depends on > =A0time of day very much, and what is good for morning is not so good > =A0for night. Those APs I know which do auto channel selection scan all channels once and select one where the least traffic has been seen. This is a one time thing, before bringing up the AP itself, as monitoring once a channel has been brought up is close to impossible. To do so, the hardware would have to switch to another channel, check what's going one and switch back to the service channel. While this happens no clients can be served because the hardware is obviously not on the service channel. This has been seen as to disruptive for anyone who thought about implementing such a feature. I'm not to familiar with the survey tool, but I guess it does also have to switch channels. If you don't care about your clients loosing connection for a bit, you could obviously stop the AP, do a scan (or use the survey tool) and based on the results select another channel before bringing up the AP again. I'm not aware that anyone has done something like that already, though, writing a script doing just that shouldn't be too hard. --=20 Bernhard