From owner-freebsd-wireless@FreeBSD.ORG  Sun Sep 23 18:17:02 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 BF556106564A
	for <freebsd-wireless@freebsd.org>;
	Sun, 23 Sep 2012 18:17:02 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
	[IPv6:2a01:4f8:131:60a2::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 5BF388FC12
	for <freebsd-wireless@freebsd.org>;
	Sun, 23 Sep 2012 18:17:02 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
	[IPv6:2001:470:923f:1:c56d:b4e7:bb34:8fd2])
	(Authenticated sender: lev@serebryakov.spb.ru)
	by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 3BE004AC2D
	for <freebsd-wireless@freebsd.org>;
	Sun, 23 Sep 2012 22:17:01 +0400 (MSK)
Date: Sun, 23 Sep 2012 22:16:59 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
X-Priority: 3 (Normal)
Message-ID: <374430363.20120923221659@serebryakov.spb.ru>
To: freebsd-wireless@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: 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:17:02 -0000

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...

 Even more, it looks like, tcpdump sees last fiew packets from client
 multiple times, because at moment when client could not do anything,
 tcpdump SOMETIMES shows latest MCAST UDP traffic from client
 (Microsoft network) over and over again!

 AP is AR9220, 802.11gn mode.

 Client is Intel Advanced-N, but in 802.11g only mode.

-- 
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>