From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 23 19:23:58 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 28607928 for ; Tue, 23 Oct 2012 19:23:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id E67CA8FC0C for ; Tue, 23 Oct 2012 19:23:57 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so2161099dad.13 for ; Tue, 23 Oct 2012 12:23:57 -0700 (PDT) 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=umUJYXpEqanLYseHP3bd8kryFkdqDQ9AG/UKTNHQoIc=; b=HGNRiJE9OnsQmOWwkWSS8ue6ope4rp7HbUID1C+rNdGud0w7Yv35inYMNkAH9tv0j8 aO7q/zPTGTmf+Zh7j/7EimA/Hz3g/gfKa8lX2ONI41hGDTHQdW/j/Zh50Cm+v230Jd7R GGgJpB9UjI3tI+tvYumvQM1nIjG6BhtAw0h45k6wmXl5COPIfwGovo1c2RBKP/sWXsG/ 6/A2xmUmfXvwPq1Ms1HjQJvERygS36mIdq4NzlPji5340lHRvOSII3AGfU0Ggzzb5n8H WYoaNfVIKB18KdsZvbdL1QV3u8WDa40HLxp1Nd1pA36w0HCLXOTvukItLVlKchiNGqXi p+4A== MIME-Version: 1.0 Received: by 10.66.74.65 with SMTP id r1mr37660434pav.75.1351020237195; Tue, 23 Oct 2012 12:23:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.146.233 with HTTP; Tue, 23 Oct 2012 12:23:57 -0700 (PDT) In-Reply-To: <201210231231.12237.jhugo@meraka.csir.co.za> References: <201210222000.q9MK01pm089451@freefall.freebsd.org> <201210231231.12237.jhugo@meraka.csir.co.za> Date: Tue, 23 Oct 2012 12:23:57 -0700 X-Google-Sender-Auth: ko1KcRR0MFbaLrvcCcanSosaVFs Message-ID: Subject: Re: misc/172955: [ath] 11n does not work in 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: Tue, 23 Oct 2012 19:23:58 -0000 On 23 October 2012 03:31, Johann Hugo wrote: >> Also - the WME parameters aren't parsed either, leading to your > >> observation about performance drops between 7x and 8.x. > I'm ready to test any upgrades :-) Well, I was more hoping that someone else would be interested in tackling this particular issue. It's a general stack issue affecting all ibss 802.11 behaviour, not just ath(4) and 802.11n. I _think_ I'm starting to understand how the adhoc node stuff works (ie, it's faking nodes through beacon discovery, rather than having actual association exchanged between them) but it's not clear exactly where to slice in the missing stuff. I also had no end of trouble trying to statically configure an 11a or 11na channel on an IBSS node. 11bgn channels are fine. I'd really appreciate someone stepping in here. I'm trying to finish off the power save queue handling changes and then move to finishing correcting the ps-poll support. Then I have the whole TX and RX data and control path to jiggle around to make things (more) predictable and better behaved. I really don't want to stray from this. :-) Do I have to promise free hardware and t-shirts? :-) Adrian