From owner-freebsd-wireless@FreeBSD.ORG Thu May 9 17:26:13 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 04D9B427; Thu, 9 May 2013 17:26:13 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id ABB76F52; Thu, 9 May 2013 17:26:12 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:242e:a5ba:b7f8:e9f7]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id D1F344AC57; Thu, 9 May 2013 21:26:09 +0400 (MSK) Date: Thu, 9 May 2013 21:26:04 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <89601766.20130509212604@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.sp b.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> <94971208.20130503122811@serebryakov.spb.ru> <105246227.20130509004931@serebryakov.spb.ru> <510232154.20130509211849@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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: Thu, 09 May 2013 17:26:13 -0000 Hello, Adrian. You wrote 9 =D0=BC=D0=B0=D1=8F 2013 =D0=B3., 21:23:20: AC> When you say "recover fast", what's that mean? First time I call forced bstuck several times, but it seems, that client re-associate after first one. For second time (AP was rebooted after first experiment) client lost association (According to interface status on Windows), but I was not fast enough to call "sysctl" by hands, it re-associated by itself. --=20 // Black Lion AKA Lev Serebryakov