From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 16:53:28 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 66DB9106564A for ; Sun, 22 Jul 2012 16:53:28 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 13A4A8FC08 for ; Sun, 22 Jul 2012 16:53:27 +0000 (UTC) Received: by qaat11 with SMTP id t11so849844qaa.13 for ; Sun, 22 Jul 2012 09:53:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=n6iSDqM6WGRqtUhToQLho0JsX/QjbLE0PJ70MUyTOzo=; b=MXNW6O3yF93ttJJHNNVbMb53aUd0usaKWSfZSXHd+3QvMxmTdEReY0pd75FnsM0BwB KGaI//1C725UpPFwqDC8DMM9LsJr1H1j1BusLVGLutkusDTDGnTG8xL7aXk6katfYCIk Vefe4omJ+Lb1aKr+poglwhG0nHea/Qg/YmxoZBftHan7bqUem2VWT7OtMZanAvzhGpqI +gYNt1bGxnNP81wQ1FOllQygi41+apt5aXg78FfC3zXqh4NHGkC5UgVdb/E29xR6VnUd 1vzJjaizGbU9zQq2mk+Zlcd9PtkEi1x1U0m4536rNm4+xnzbpg4WCU4spu787nfS8RWk oLIA== MIME-Version: 1.0 Received: by 10.224.101.193 with SMTP id d1mr20475517qao.20.1342976007433; Sun, 22 Jul 2012 09:53:27 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 09:53:27 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 12:53:27 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current 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: Sun, 22 Jul 2012 16:53:28 -0000 On Sun, Jul 22, 2012 at 11:22 AM, Adrian Chadd wrote: > Hm, ok. > > So I'd start diagnosing this by setting up another FreeBSD device in > monitor mode on that channel and capturing some beacons. > Then take a look in wireshark and make sure you're seeing beacons consistently. > > I bet the beacon timer and beacon slot configuration is all subtly > messed up, leading to this mess. Oh and I'll need another 11n-capable card. -kim