From owner-freebsd-wireless@FreeBSD.ORG  Tue Dec 11 21:06:58 2012
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
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 50968E24
 for <freebsd-wireless@freebsd.org>; Tue, 11 Dec 2012 21:06:58 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com
 [209.85.212.170])
 by mx1.freebsd.org (Postfix) with ESMTP id CC2A78FC14
 for <freebsd-wireless@freebsd.org>; Tue, 11 Dec 2012 21:06:57 +0000 (UTC)
Received: by mail-wi0-f170.google.com with SMTP id hq7so2428870wib.1
 for <freebsd-wireless@freebsd.org>; Tue, 11 Dec 2012 13:06:56 -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=1htEXF7fUpzzn5yidvDMteW0wjJ0OxMSd17WeRDr+54=;
 b=H+kAiZP7tEg1SN4eCZEqWl92lH8Cz4++ICjde5luO3lH/ZW46X9Bl32vFeUQn8M7Vl
 8YgbYW4WWYE66mkDqT5M+ueVdvhZKlKR/Hwj4k9VsAIkInbPdmgz176Uefkvql3iwjgT
 3SKFrOWzwLHmEZxnKLTuCNN33xjfX6dgXfx63yIDZ7BjkPUhZKPWMOmU4gyufX2azv89
 uZCMFtVdug1iVsj0eD2au6vHmqVKUCAYiQGzxNGm53K1Am3wiytS+BSKYC84Ufc8LXIt
 MsjbTe2xJ/KLEPG0OwkjS0esTWX9vHMo7SvlGtcvXeHI1tLmQ5oUBxu7ZKptyI0WSQE1
 s+4w==
MIME-Version: 1.0
Received: by 10.180.102.101 with SMTP id fn5mr18972264wib.19.1355260016664;
 Tue, 11 Dec 2012 13:06:56 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.217.57.9 with HTTP; Tue, 11 Dec 2012 13:06:56 -0800 (PST)
In-Reply-To: <CAFZ_MYJdeJghUZX+_aeMKp28++1juZCqs_sqT=PCNYEnA4GnJQ@mail.gmail.com>
References: <CAFZ_MYJdeJghUZX+_aeMKp28++1juZCqs_sqT=PCNYEnA4GnJQ@mail.gmail.com>
Date: Tue, 11 Dec 2012 13:06:56 -0800
X-Google-Sender-Auth: Bq9tNHC9TCs7dpYDyJT_I2kFIyw
Message-ID: <CAJ-Vmo=rOYAOr2vw+VdQKwy-ud=UU6W1jUUVS-6CPGD4WE2sxQ@mail.gmail.com>
Subject: Re: 11n in adhoc mode
From: Adrian Chadd <adrian@freebsd.org>
To: PseudoCylon <moonlightakkiy@yahoo.ca>
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 21:06:58 -0000

Hm, you may be right; but I disabled HT protection entirely and stuck
it on a very quiet channel.

It's possible both ends were colliding with each other though.

I did add some HT update code to the adhoc beacon processing, though.
It's just not entirely clear how to handle that given the nature of
IBSS - ie, every peer may have some different idea of what the
protection mode is.

It's possible that it should be learnt once when you join the BSS,
much like how the adhoc scan pick code checks for a few things
matching before it joins that BSS.


Adrian