From owner-freebsd-mobile@FreeBSD.ORG Mon Oct 22 02:39:15 2007 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D4C816A417 for ; Mon, 22 Oct 2007 02:39:15 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id E2DA413C4BE for ; Mon, 22 Oct 2007 02:39:14 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l9M2cuAv023889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Oct 2007 19:38:57 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <471C0D40.7050303@errno.com> Date: Sun, 21 Oct 2007 19:38:56 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.6 (X11/20070814) MIME-Version: 1.0 To: AT Matik References: <20071021003032.D2DA04500E@ptavv.es.net> <200710210033.22682.asstec@matik.com.br> In-Reply-To: <200710210033.22682.asstec@matik.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: o.com; whitelist Cc: freebsd-mobile@freebsd.org Subject: Re: Problems running ath with bgscan enabled X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2007 02:39:15 -0000 AT Matik wrote: > On Saturday 20 October 2007 22:30:32 Kevin Oberman wrote: > >> My bgscan interval was the default 300 and almost every 5 minutes I >> would lose connectivity, often for over a minute. When I made the >> association between the bgscan interval and the drop-outs, I did an >> "ifconfig ath0 -bgscan" and things stabilized immediately. No further >> problems. >> >> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) >> ath0: mem 0xb4000000-0xb400ffff irq 11 at device 2.0 on >> pci11 ath0: mac 5.9 phy 4.3 radio 3.6 >> >> This is really not acceptable for default behavior as it won't be clear >> to many how to fix it. Is it expected or is something wrong? >> >> > > I believe it is so but as you already did, when you like to associate only to > the AP of your wpa config you should set -bgscan and eventually 'roaming > manual' also, if I am not wrong this is described in ifconfig's manpage > > wpa_supplicant works fine w/ bgscan. When the bgscan's complete wpa_supplicant receives an event and retrieves the scan results. It then decides whether or not to roam. There is no need to manually configure the device. OTOH the scanning+roaming code in wpa_supplicant is very simplistic and I don't have a lot of experience with how well it does roaming. I believe it will only join ap's that are listed in the config file so it shouldn't roam arbitrarily. Without a log it's virtually impossible to comment on reports/complaints. And even w/ a wpa_supplicant log it's also useful to understand if there are other events that trigger scanning and/or roaming--like beacon miss events. Hence the need for logs and statistics. Sam