From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 15:22:16 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 8B11F1065672 for ; Sun, 22 Jul 2012 15:22:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5DB858FC08 for ; Sun, 22 Jul 2012 15:22:16 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so9984684pbb.13 for ; Sun, 22 Jul 2012 08:22:16 -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=QM3NAITJd/hSaskckZdcdGn+Xs0gi2PDTVTvXg+E5pQ=; b=lO9kmxImyHe3jYQcghfyu0yRqq8EAXYTD+maWmEks6uJ3niZfSGDH2VIbvhwiMTn4H 8/XhhyhMwy+rzPJINZ9jFpxWs8Akd/8qs+8Wetkip22zYvEkbd+pYG/0dGx7+Jw3S1Ns 9MhIIKU6eLMMmwZ9UcPdf0YgC8SFU80ZgmcAyirxiI5bCJ9B0y5wJ6K3p0ldp11amkq7 kSxsiNiaz5dx9JjZTf9lBry3S+ZAOMvwaACtou7HkRD2MpX8sbQ4J1/eXAPIBT/QLv75 sMNs5KXzjLPsLMtDCGF4k9M08mcQoATOIP/2YwsiW6kKHv0tUt3g5cQII4DiVqpcYEy1 4CMQ== MIME-Version: 1.0 Received: by 10.66.72.163 with SMTP id e3mr24635306pav.42.1342970536156; Sun, 22 Jul 2012 08:22:16 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 08:22:16 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 08:22:16 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan 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 15:22:16 -0000 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. Adrian