From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 03:54:52 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A0944697 for ; Sat, 16 Feb 2013 03:54:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x229.google.com (wg-in-x0229.1e100.net [IPv6:2a00:1450:400c:c00::229]) by mx1.freebsd.org (Postfix) with ESMTP id 0DF7A839 for ; Sat, 16 Feb 2013 03:54:51 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id ds1so1400306wgb.0 for ; Fri, 15 Feb 2013 19:54:51 -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=XV9m8zRtBCxL90ezXkqz5qF2To5Md4xk+OfmiV6YjmI=; b=ra6sBy2H4TQxcxvSimHuRGwIX35txqoWd5ya+IFFSW61qzO7C/hnTZkUIuR8hKHRIh OeWj/hfuGWUNKtaWiY5FRG5kb6yy+XRVSlYi3f9/bDJo0X1R9Ghh+ulgSD2UiWe3yRPi EnqWwByXuiON39nDstzzB6tYkQsw9kV51N8UDG0ndkZBYYn9Urc7b9fwgC3vAHZVKpVZ 95wzqSiqP5beWIWUCpTc3O4pUFcUGidfkkXQCNhdKQENYbAPuknuF/mIY7VkxLvnF+7N ruml0Sx1YAEuY4Je+bYRh9yIY7qlRBrnYiP2JNb9oc65dXr0Zz6OoesYG0+CBeTSIj+y 4Veg== MIME-Version: 1.0 X-Received: by 10.194.7.136 with SMTP id j8mr8018543wja.38.1360986891231; Fri, 15 Feb 2013 19:54:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Fri, 15 Feb 2013 19:54:51 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 19:54:51 -0800 X-Google-Sender-Auth: rSolrXkfKk1oruKhnO8j9vKk89s Message-ID: Subject: Re: negotiating HT params at assoc in sta mode From: Adrian Chadd To: PseudoCylon 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: Sat, 16 Feb 2013 03:54:52 -0000 On 15 February 2013 18:21, PseudoCylon wrote: > On Fri, Feb 15, 2013 at 6:20 PM, Adrian Chadd wrote: >> Hm, that sounds right, what's the code doing wrong? > > Currently, it seems the sta sends back ht params the ap included in a > PROBE_RESP packet. So, the ap could send ampdu packets bigger (in > byte) than the sta can handle or packet gaps are different from the > sta wants after ba session is created. (During ba session negotiation, > these params are not exchanged, only window sizes (frame count), seq > #, and token.) Right. yes, we should be negotiating the ampdu density to be the maximum of what the AP and STA can associate. Same deal with IBSS peers (and mesh peers too, eventually.) Adrian