From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 03:03:02 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 55685106564A for ; Mon, 23 Jul 2012 03:03:02 +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 01AB98FC14 for ; Mon, 23 Jul 2012 03:03:01 +0000 (UTC) Received: by qaat11 with SMTP id t11so952860qaa.13 for ; Sun, 22 Jul 2012 20:03:01 -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=DWjX73TdAgxQ7cSYMPPfmJIxJUZ5BZ0sASs2a7LSfAw=; b=obkSTHNXPstzup4uLcuyoGtGHnHBaYNFzkwOX9Zpcb9PggM/hMit5yNX8M4XxgI86j rBi7BY+FhowaQHafEUxHUbLX6CmqajLD343eg9s9dcDCwuwCu/MQ774/UBWRPDD7dRYX oTD1MTRTiyPMFtJQkI4PiIf7J+hdKVrL+O4kMORoh43xteEGd5CnRhzrwVsqIMt3zD3U l3OjuOaBopufRaOkGeV7/v/4lYjmq/XDx9ezMJfBF9D3WTOdWph/NRaZ7V8badsymrED kv4mnBhLW90Ww5ecYzzeyfIjtauBYX4xFf0ChvrwoQQo6AV+QDD86+51jMi3zwjqmMw/ 0qxQ== MIME-Version: 1.0 Received: by 10.224.71.11 with SMTP id f11mr3657193qaj.41.1343012581494; Sun, 22 Jul 2012 20:03:01 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 20:03:01 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 23:03:01 -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 03:03:02 -0000 On Sun, Jul 22, 2012 at 10:58 PM, Adrian Chadd wrote: > 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. Very good, that direction is greatly appreciated and I'll follow up with it. thanks -kim