From owner-freebsd-wireless@FreeBSD.ORG  Sun Sep 23 18:21:22 2012
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
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 2A2E8106564A;
	Sun, 23 Sep 2012 18:21:22 +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 ED54E8FC08;
	Sun, 23 Sep 2012 18:21:21 +0000 (UTC)
Received: by pbbrp8 with SMTP id rp8so1704216pbb.13
	for <multiple recipients>; Sun, 23 Sep 2012 11:21:21 -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=/45TMVxPoYpqUiA1E3bMHAVCEvrgtlgr5/JFWV2v15s=;
	b=PbeV0EgIGEQCHtixv1IvPpWvyAYRuZjZEKAztUDHbedi+YjzUeEFocFniZ0ul3r46d
	vgEEpzv11RyJgEhAcl/BrRSZ6Wn9q2FNZuNj8mwO8BkMEzGA5xDpCN6UB0cqx3aFHl+5
	ENwv7aH4+0hVP2OfNjvBhtLPgUqZNQLARBhz+UNdy99059jQtg0FVTlIwJKaOMbUznwD
	hTITV3UIxSRcEKTftvzT9a8s284OZbgcIlmYUa9F6GUSW5RP+8s0oG25E3IsvwP24p7O
	LMZg044i2NXYiUZ8z5m73iyUoeDAvrLI60bL9871zp6/mDKWqx/2ytnFlGWtI4i8Py4o
	f1SQ==
MIME-Version: 1.0
Received: by 10.68.129.131 with SMTP id nw3mr31075355pbb.43.1348424481310;
	Sun, 23 Sep 2012 11:21:21 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.68.36.106 with HTTP; Sun, 23 Sep 2012 11:21:21 -0700 (PDT)
In-Reply-To: <374430363.20120923221659@serebryakov.spb.ru>
References: <374430363.20120923221659@serebryakov.spb.ru>
Date: Sun, 23 Sep 2012 11:21:21 -0700
X-Google-Sender-Auth: DoJVY7xSYQNBOARam90FGRv64Pc
Message-ID: <CAJ-Vmom8AqszpwdieG56waTowgf1qvOeC0zA94SSBv4z9pRDoQ@mail.gmail.com>
From: Adrian Chadd <adrian@freebsd.org>
To: Lev Serebryakov <lev@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-wireless@freebsd.org
Subject: Re: New ath code on AP: strange client behavioir
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Sep 2012 18:21:22 -0000

On 23 September 2012 11:16, Lev Serebryakov <lev@freebsd.org> wrote:
> Hello, Freebsd-wireless.
>
>  I've  build  new  image for my router (r240742), and now traffic stuc
>  shortly after client association.
>
>  After manual re-assotiation (diconnect/connect cycle) traffic stuck
>  after several packets (2-3MiB of traffic) again.
>
>  According to tcpdump on AP, it sees some traffic from client, and
>  send something back, but client could not resolve any name, etc...

Ok ok I've broken something. I'm currently tracking down one bug
(which may just turn out to be a hardware quirk..) so I'd really
appreciate it if you all could work together to isolate which
commit(s) broke things.

Thanks so very much and I'm sorry I've broken things!




Adrian