From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 02:08: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 0D7BD106564A for ; Mon, 23 Jul 2012 02:08: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 B411A8FC0A for ; Mon, 23 Jul 2012 02:08:08 +0000 (UTC) Received: by qcsg15 with SMTP id g15so3593484qcs.13 for ; Sun, 22 Jul 2012 19:08:02 -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=QRB4x5kS53zvO9z6UYJ1ywPjHTPoxbu0iVXrsiAxWQ8=; b=iEfpPyGvRjDZX6upDZlF01WqhSFUPNTvDXOUHYo/7a5iMKDFBoRXsgL0E1MUI10rbG yIGtBeEMJK2NfiYz420bNl4n++Vs1NtMxbyxLaG68yqbvP3CXovZ7Y+F7dVyrqC3IpD0 s5cbCVN1v08KfoAQMpTwMVtOxLzricSraranxxg2G3D0o8gZ8EW6jHrwkg/c6RoZcRbn hyjwhCsn4zXTc8HSTTwQAcDHWxPTjQmhSdI3fbNo7uIyXTFRCmMdfS+fhDyD0WIeF8fw 6SAf95eNwWHGRkB/nEwvx7eDshopamzkbQnd1LixT+0X1UYewnJW3Tv5ivUT6paPQtZu 33PA== MIME-Version: 1.0 Received: by 10.224.59.13 with SMTP id j13mr22117131qah.44.1343009282600; Sun, 22 Jul 2012 19:08:02 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 19:08:02 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 22:08:02 -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: Mon, 23 Jul 2012 02:08: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. I've setup another machine running -current and have it running in monitor mode. Some output looks like: 21:38:55.159960 709697219us tsft 1.0 Mb/s -21dB signal -96dB noise antenna 1 2437 MHz 11g Beacon (ap1) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] ESS CH: 6 21:38:55.211339 709748597us tsft 1.0 Mb/s -14dB signal -96dB noise antenna 1 2437 MHz 11g Beacon (ap2) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] ESS CH: 6, PRIVACY 21:38:55.236939 709774195us tsft 1.0 Mb/s -13dB signal -96dB noise antenna 1 2437 MHz 11g Beacon (ap3) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] ESS CH: 6, PRIVACY 21:38:55.243399 709780617us tsft MCS 7 -55dB signal -96dB noise antenna 1 2437 MHz 11g ht/40+ CF +QoS Data IV:68e Pad 20 KeyID 0 21:38:55.243403 709780661us tsft short preamble 24.0 Mb/s -18dB signal -96dB noise antenna 1 2437 MHz 11g Acknowledgment RA:90:f6:52:75:eb:99 21:38:55.243859 709780972us tsft short preamble 24.0 Mb/s -17dB signal -96dB noise antenna 1 2437 MHz 11g Request-To-Send TA:fe:d1:11:38:3c:e5 21:38:55.243863 709781016us tsft short preamble 24.0 Mb/s -53dB signal -96dB noise antenna 1 2437 MHz 11g Clear-To-Send RA:fe:d1:11:38:3c:e5 Looks like its good to go in monitor mode. -kim