From owner-freebsd-stable@FreeBSD.ORG Mon Sep 18 17:30:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D54D616A415 for ; Mon, 18 Sep 2006 17:30:21 +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 3381743D68 for ; Mon, 18 Sep 2006 17:30:21 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k8IHUIqJ005288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Sep 2006 10:30:20 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <450ED7AA.6090801@errno.com> Date: Mon, 18 Sep 2006 10:30:18 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: dmitry@karasik.eu.org References: <20060918083139.GA59966@tetsuo.karasik.eu.org> In-Reply-To: <20060918083139.GA59966@tetsuo.karasik.eu.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ath0 weak connectivity X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 17:30:21 -0000 Dmitry Karasik wrote: > Hi, > > Has anyone experienced problems with ath0 giving bad connectivity on > 6.1-STABLE? My wireless card reported as Atheros 5212 rapidly loses > connectivity if I move it more than 2-3 meters away from the access > point, but the same notebook connects well from under windows. > > I tried both kernel with both old device ath_rate_sample and ath_rate_onoe, > tried to play with AP's settings, changed transmit rate and beacon > interval, nothing helps. One interesting thing though is that "ifconfig ath0 > scan" reports my station as configured to 119ms beacon interval, while > it is set to 100ms actually. > > Anything else I can try? > ifconfig ath0 scan doesn't report your local configuration, it triggers a scan and reports the scan results. If your local station thinks the beacon internal is 119ms when it's really 100ms then something is very confused but it's unlikely to cause "bad connectivity" (unless you're operating the station in power save mode which isn't currently possible). I do not understand what "bad connectivity" means. If you provide information like the mac+phy revs for the card, hal version, and statistics from programs like athstats then it might be possible to identify what's wrong. Otherwise look at turning on debugging at the net80211 layer with wlandebug. Both athstats and wlandebug are found in src/tools/tools (under net80211 and ath respectively). Sam