From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 9 23:06:04 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 510FFF25 for ; Sun, 9 Dec 2012 23:06:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id D5B278FC08 for ; Sun, 9 Dec 2012 23:06:03 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hm9so759319wib.13 for ; Sun, 09 Dec 2012 15:05:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=A9xBKh6eaT0Vmazhc1ZvQ2loyCA6OLVnaflT0DGdJnw=; b=yt8qqeEqJTwDBKYSkMI8ZIZGby90WTCfnpIiyhyw4leKttWKPWWXugb7W6iKGEi+6W 8dnE21aeIzmbOS8vqAg3oZFs1khW7sG+3vKwXJUTAXrUUbovVa+CVYZBK8eJ/qDzxnYI eUE4nGdbhV/G8sqcpXp9uRdP0k85/kNjnHm+g3df0DQ0pFWjkM3Rf2cy0NEcUvC4S6/f VvNweANkmO25XtPcUgb2DYonAOqWmvdQuS99PV7KdevMB4zBgMbE5myvXvvT2/5bhtzI QTyf1n/obkfb6nTQPlVVwvS17qM2jk+n8wRxHK7ZwaJ1fCzyNbLuPUN+QgYEARDUIvxL TRCA== MIME-Version: 1.0 Received: by 10.216.139.140 with SMTP id c12mr4785705wej.46.1355094357607; Sun, 09 Dec 2012 15:05:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sun, 9 Dec 2012 15:05:57 -0800 (PST) In-Reply-To: <201205181133.57403.jhugo@meraka.csir.co.za> References: <201205181133.57403.jhugo@meraka.csir.co.za> Date: Sun, 9 Dec 2012 15:05:57 -0800 X-Google-Sender-Auth: 2MncjpugENqFvEPyu0I4Qx9pq0A Message-ID: Subject: Re: [ath] Degraded throughput - adhoc mode From: Adrian Chadd To: Johann Hugo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 09 Dec 2012 23:06:04 -0000 On 18 May 2012 02:33, Johann Hugo wrote: > Hi > > We have an outdoor wifi mesh network with various atheros adapters configured > in adhoc mode. (FreeBSD-9) Hi, Please try -HEAD. I _think_ I've handled the WME configuration side of things right in IBSS mode. The problem with IBSS is that nodes are automatically created whenever frames are received; then a beacon frame will update the current configuration. So if you create an IBSS STA node based on receiving a data frame (and not a beacon) then it may create things with no WME config, and it'll just default to the default (non-aggressive mode) WME parameters. Now, my -HEAD patch may actually be incorrect, because it changes the global WME config for that particular device; there's no real per-node WME configuration unfortunately. I don't have a very large IBSS setup to test how this works in practice and I will admit I haven't sat down and really tried to understand / implement IBSS stuff in any useful fashion. But it did come up and it did parse the WME IE correctly. So just make sure you configure the WMM parameters on both sides to have aggressive BE parameters (aifs 2, cwmin4, cwmax 10, txop 64) and then reassociate. I may end up reverting the WME IE parsing for now and just requiring people statically configure the WME parameters on each node. I'll experiment some more and then commit it to -HEAD. But the ath IE parsing works and I now see fast-frames used in adhoc mode, which will bump the throughput up a bit on the non-11n NICs. Adrian