From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:57:55 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25A101065780 for ; Mon, 20 Aug 2012 16:57:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E66A18FC12 for ; Mon, 20 Aug 2012 16:57:54 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so7622360pbb.13 for ; Mon, 20 Aug 2012 09:57:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4isMrpTMRqR/eB2GisIa8figQtXsZFFp8ZMIPHnqVYs=; b=ahtX+QDcj3w2bVbvmO3F6cv1iuKJJ2DJ3RwAxfLTNSKJJF98JcaVLWtMtDFqv+5srf K4l/WvRNPie/QeQ5ujasV9gMY2gvu2KUJqyeyIWboqbPlq12vWSowdKOLUHA6MT6oloZ P2K9riNoO81Xak3LH26D1KrIdtY3FNb3zFGWLT9O2qkxnfxkKRQYegJqaFwJuwVpfWkJ HdoK8cx1s5pf4MIloE/1vWEVWlUb5junpqBSLEiU4EJ+T+2rnh/3oaHr697wtCTd+9bQ qvmO3c0GLAQmuvrQDiKzdruGPm/2KrnVrl3fvVy0Ju3sOOGgV14vVwira/DXByC/Ilks Dk0Q== MIME-Version: 1.0 Received: by 10.66.85.4 with SMTP id d4mr21696337paz.11.1345481874116; Mon, 20 Aug 2012 09:57:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 09:57:54 -0700 (PDT) In-Reply-To: <20120820165435.GO98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> <20120820160344.GM98910@zxy.spb.ru> <20120820163118.GN98910@zxy.spb.ru> <20120820165435.GO98910@zxy.spb.ru> Date: Mon, 20 Aug 2012 09:57:54 -0700 X-Google-Sender-Auth: _fFD2RIP354N-PzojTxr0CoJN-4 Message-ID: From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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: Mon, 20 Aug 2012 16:57:55 -0000 On 20 August 2012 09:54, Slawa Olhovchenkov wrote: >> Yup. Look at the channel busy statistics. YOur channel isn't busy at all. > > Oh, I am don't need utilise all bandwidth, typical use: ssh access to remote host > and lot of web traffic. And narrow uplink (~2-5Mbit/s). > > Now I do test transfer from local ftp: Right. > min avg max > tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% > (10.8 73.8 90.5 5.1) (12.2 76.7 93.2 6.8) (13.2 81.2 94.9 9.5) Right. The rx% is high as you're receiving frames. The busy count (bc%) is high because you're actively doing work on the channel. If bc% is high but rx% and tx% is low, there's some non-decodable wifi (eg too far away, or too distorted, or collision-y) non-wifi signal that's high enough to cause issues. [snip] >> Well, what do you mean by "lost traffic" ? I need some more >> information about that. > > Sometimes (may be one in 2-3 days) receiving packets on wlan0 stoped. > May be intesive traffic increase probability. > No messages in dmesg. tcpdump on wlan0 show only outgoing packets. Interface is UP. > No automatic recovery. For manual recovery I am need to kldunload/kldolad if_ath_pci. The next time it happens: * sysctl dev.ath.0.txagg=1 (I assume your interface is ath0) - that dumps some basic information about the state of the aggregation logic _AND_ the hardware TX queues; * check dmesg; * ifconfig -v wlan0 and ifconfig -v wlan0 list sta (to see if 11n is enabled). You shouldn't have to unload/reload the driver. A simple ifconfig wlan0 down ; ifconfig wlan0 up (and restarting wpa_supplicant if it was running) should be enough. (Oh, and running dhclient.) You can also enable reset+TX debugging when things hang (sysctl dev.ath.0.debug=0x3) and then do something like 'ifconfig wlan0 down'; it will then dump out the state of the hardware/software queue(s) and hopefully give me a better idea of what state the hardware/driver is in. Thanks, Adrian