From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:36:05 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 D67E9106566C for ; Mon, 20 Aug 2012 16:36:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 699FA8FC0A for ; Mon, 20 Aug 2012 16:36:05 +0000 (UTC) Received: by dadr6 with SMTP id r6so2423657dad.13 for ; Mon, 20 Aug 2012 09:36:05 -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=IaYYMqtFkR8s5e3VPnH2pkUQ8tb+vW4dhKRQ4elDRjQ=; b=w5h7E7kqfIQYygqHqkuC7RK9UbfpFJNzJ+YPR/2SIAJrq6bSN2b5W/c7TEnZxLu/93 p4quLPomTq49QJcTHl+5ulA1IxYuNz6ShYwnQzqWmUvwA0PnWx22D+JajCCIyQpqrrdH LvVjUg8Dr+XOxIREs/4ITfIcszZyxsis+aOWzCy5eCzvz27bRefQGhvuMudrLnDwl5RS e9Vark5JrUhqFlnjqoBnwq0uyoNZp7VZBVCvQ2OV788r/T6s7ULsOrK+XEE+8RAMt2uP 6oKcEqZsVo/MIea3BLYZzraIrQsVlggx1qtmimlRAiL1CdDjLbBfBp1PCQFDUep18Ngp j1Lg== MIME-Version: 1.0 Received: by 10.66.75.195 with SMTP id e3mr30932437paw.32.1345480564908; Mon, 20 Aug 2012 09:36:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 09:36:04 -0700 (PDT) In-Reply-To: <20120820163118.GN98910@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> Date: Mon, 20 Aug 2012 09:36:04 -0700 X-Google-Sender-Auth: znxVPG_r2YGpzve2ksCgd7U61UE 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:36:05 -0000 On 20 August 2012 09:31, Slawa Olhovchenkov wrote: >> The main issues I see right now are very likely due to noisy >> environments and ANI behaving poorly. > > How you detect noisy environments? > (some output from athsurvey?) Yup. Look at the channel busy statistics. YOur channel isn't busy at all. > What level of noisy is acpetable in terms of athsurvey and in terms of > physicaly units? (I can use Cisco Spectrum Expert for survey, but not > simultaneously with this card). Anything bursty, wide or narrow band, will cause issues. > What is ANI? Ambient/Automatic Noise Immunity. There's some code which adjusts some PHY parameters to do with signal sizing and offset; however I may have (more) broken it. I need to sit down and add some further debugging and write an inspection tool or two to figure out exactly what's going on. > What I need to try in next time of lost traffic? > (no messages in console in this situation, nothing about "ath0: device > timeout" nor "ath0: bb hang detected (0x4), resetting"). > > Do I need to enable some debug? Well, what do you mean by "lost traffic" ? I need some more information about that. Adrian