From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 02:58:32 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 16A75106566C for ; Mon, 23 Jul 2012 02:58:32 +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 D7A828FC0C for ; Mon, 23 Jul 2012 02:58:31 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so10709210pbb.13 for ; Sun, 22 Jul 2012 19:58:31 -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=GmIGo1/Stj9SNZDeiMYlt/DK86crOOg3ofhWFryU7+U=; b=NbMBIOZxH1AYZkegKUrOJRU0uaqhiLxbmHmMgCMbGXFd+QSgJNngVqNd5SDBSLlNQn LW8XHpK4jnRAiWps+lSBjRAEmFeU2KmAriADopXRYxqbupvwl58wo5XI2nq3Q7FHGBc4 aY/Gb4fK6yVYNJvRlhvBfhswSO0T265LkdFvw0efgmEztC1CI4UgjVM2C8Uirp49cSly WXuNT/6Uls5LFewG1yAf1tKe1L5upjXsfYXS8mzesp7peCdFoDR1NqWbaSKh9lwrwKe+ 6xX3uM07wwCfwbtHLVkE8xLUrn8xaVbJA/lhVYyg/Zc151KHXHeQnlWd0ToViWw0k1TG uZTA== MIME-Version: 1.0 Received: by 10.66.83.65 with SMTP id o1mr27506265pay.17.1343012311581; Sun, 22 Jul 2012 19:58:31 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 19:58:31 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 19:58:31 -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: Mon, 23 Jul 2012 02:58:32 -0000 On 22 July 2012 19:55, Kim Culhan wrote: > Looking at a pcap when running the ap with 4 vaps, behaving in the > usual way looking at it from > a client., cant connect to most of the ssid's. Hm, right. > Not finding anything remarkable looking at it with wireshark, would > you want to give a look > and see what you think? I'm knee deep in massaging the driver to be ready for the AR93xx and later series chips. I can give you some pointers, but I don't want to get too distracted by other things. :) What I'd do: * I'd look at the beacon interval (in TU - which is 1024 microseconds) in the beacon frames, for each VAP; * Then I'd look at whether the beacons you're seeing are occuring at regular intervals, at the above beacon intervals. Let's first establish that you're reliably transmitting each beacon correctly with the right interval, then we'll go from there. Adrian