From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 16:52:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 86EEA1065670 for ; Sun, 22 Jul 2012 16:52:09 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3C57F8FC14 for ; Sun, 22 Jul 2012 16:52:09 +0000 (UTC) Received: by qcsg15 with SMTP id g15so3494499qcs.13 for ; Sun, 22 Jul 2012 09:52:08 -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=YEbI6T6XeO0NaB9xB1eP0Ss7IYUpRoqpM1qRU/EY65k=; b=kzKGbWZGAQH5VvOaQQrlR2l4GDxfHSp4fIlledFRo0XzikFReYGJ0e0sJZjswk+WAE 7y8hc3Sd8IbIQosZF62/L+i0TWe8WFPlg79k73NLWogTjR7G1SYTyOU6gbrUbTmfvjmH PgAm8XVOE2UKTxTT3qqzbOSUGBJ1wC6WG4NoXuXElOO1j4754OZD8/IWtSUf8xFKd+P9 hyGs20c6yGMykgwxD9zRJ0mPxt6FBHdJ+U/IUDheEPWlQNL9ZnvORXxPWS8Z1C3C/lSj YiTDOidIKGl8clVy9Q+H8sKPHcISbRWbBuDP0iXV6WEZ6e/8kE/1fEzWHdbTYCxsSpjh yQPg== MIME-Version: 1.0 Received: by 10.224.59.13 with SMTP id j13mr20387634qah.44.1342975928425; Sun, 22 Jul 2012 09:52:08 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 09:52:08 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 12:52:08 -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:52:09 -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. Ah ok.. I'll work on setting up another FreeBSD machine. thanks -kim