From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 14 08:26:22 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84B9A106564A for ; Tue, 14 Feb 2012 08:26:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 193048FC0A for ; Tue, 14 Feb 2012 08:26:21 +0000 (UTC) Received: by wibhn14 with SMTP id hn14so6230959wib.13 for ; Tue, 14 Feb 2012 00:26:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=aGrv+PL/VgTf58BjxmdKRYB12mylT44uKfE/juaZYo8=; b=TfUkS/mkm7YMoPdzQjwapCtC39YSPEXBL6BfTcbDq17rDfAGvvI6qO7nQb37ptZLMN ZMI3m2i+LrJ5ZhkqFQXEZ7eiIS6Xe/TAEZ9seRltbOHSiwoIZJrQTF+BOPNjSa0Gzp75 0Vbwg177fnzvOJTFwSeyF5dcBNqQcRkB8cCxM= MIME-Version: 1.0 Received: by 10.180.78.6 with SMTP id x6mr1981504wiw.18.1329207981054; Tue, 14 Feb 2012 00:26:21 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.175.136 with HTTP; Tue, 14 Feb 2012 00:26:21 -0800 (PST) In-Reply-To: References: Date: Tue, 14 Feb 2012 00:26:21 -0800 X-Google-Sender-Auth: asoIcm1Zw0cqphnhRyjIBOBuBXQ Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Fragment number of first fragment != 0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Feb 2012 08:26:22 -0000 Lemme check into this a little more.. adrian On 14 February 2012 00:19, Monthadar Al Jaberi wrote: > Hi, > > I found that in FreeBSD current the first fragment will have a > fragment number = 1 in function ieee80211_fragment. > > But according to 802.11-2007, 9.4 Fragmentation page 279: > "...The fragments shall be sent in order of lowest fragment number to > highest fragment > number, where the fragment number value starts at zero, ..." > > This also holds on the 802.11-2011 draft 12: > "The fragment number is set to 0 in the first or only fragment of an > MSDU or MMPDU and is > incremented by one for each successive fragment of that MSDU or MMPDU." > > I checked Linux 3.3-rc3 code and there I see them having a check on rx side > if (frag == 0) { /* This is the first fragment of a new frame. */ > and on tx side they put: > fragnum = 0; > > On Madwifi 0.9.4 in function ieee80211_encap: > fragnum = 0; > > So should we change our fragno to be 0? > > br, > > -- > Monthadar Al Jaberi > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"