From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 22 18:52:49 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id ABC74A4D; Fri, 22 Feb 2013 18:52:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by mx1.freebsd.org (Postfix) with ESMTP id 25D05282; Fri, 22 Feb 2013 18:52:48 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id fg15so765893wgb.1 for ; Fri, 22 Feb 2013 10:52:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=yY1aEo+/kxbjBGfFgZsZ7ixANK/BgnsLp3lMX2i+mBQ=; b=UOQJW1ubotNTvwqlHNA+XGqYDMplGcJhvwlhk8CLjyFpq5xKQ3I1WbT57i2t0cK89P 66+Ni7YfLL9kJfVetmlqL1iD28n5hcpqjeE63L1j1Kannc6TGC9vBqC0XvJKOdWnMwFG n4Qh/CgO/S+pCjEuEefLICpIK6mZD8eG4720njJX801D4gSx0MYRXoEgn5yJNhAjwR7h 4PlbGKxX5/PNBgvRE6/vQlIw3497vNRuKd5m0jNODfa+53e63UeN2IH8tO/FOvUEWu1Q +bniCFYEfsx17Bfib5MtAjRvEFMN2XCKoK6yezRm92hoLuGms2+SwWCY4BZxNO/ZRTnX xFdg== MIME-Version: 1.0 X-Received: by 10.180.24.229 with SMTP id x5mr333889wif.17.1361559167892; Fri, 22 Feb 2013 10:52:47 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.74.194 with HTTP; Fri, 22 Feb 2013 10:52:47 -0800 (PST) In-Reply-To: References: <201302180246.r1I2kocv064092@freefall.freebsd.org> <201302221933.25718.bschmidt@techwires.net> <201302221947.24307.bschmidt@techwires.net> Date: Fri, 22 Feb 2013 10:52:47 -0800 X-Google-Sender-Auth: qyEa_ldvdSXhacXUjYF3hbsF5-Q Message-ID: Subject: Re: kern/176201: [net80211] [patch] 11n station includes unrelated ht params into ASSOC_REQ packet From: Adrian Chadd To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-bugs@freebsd.org, PseudoCylon , 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: Fri, 22 Feb 2013 18:52:49 -0000 Hm, it's possible in my sleep deprived state that I'm on the right but wrong track here. The OP problem is that we're not advertising the right capabilities when we associate, right? Why aren't we just advertising the VAP ampdumax and ampdudensity no matter what the operating mode? Why are we capping those parameters to the learnt-from-AP parameters? Adrian