radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Bill Stafford <bill.stafford-BUHhN+a2lJ4@public.gmane.org>
To: radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Re: MCS field: RFA
Date: Tue, 02 Feb 2010 21:24:38 -0800	[thread overview]
Message-ID: <C33B109A-9A6C-4931-8A69-5147A418E8B5@me.com> (raw)
In-Reply-To: <20100202195424.GE1060-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>

On Feb 2, 2010, at 11:54 AM, David Young wrote:
> On Mon, Feb 01, 2010 at 10:09:37PM +0000, Bill Stafford wrote:
>> 
>> So the bandwidth options for a packet when the device is tuned to a 40 MHz
>> channel are:
>> 40 MHz (full 40 MHz bandwidth packet)
>> 20L (20 MHz packet in the lower 20 MHz of the 40 MHz channel)
>> 20U (20 MHz packet in the upper 20 MHz of the 40 MHz channel)
>> 
>> When tuned to a 20 MHz channel, the packets can only be 20MHz
> 
> My recollection of 802.11n may be incorrect, but aren't 20L and 20U HT
> transmission channels aliases for the same center frequency and width as
> a 20 MHz HT/legacy channel?

As I understand it, those transmission modes, and rx attributes,
do represent packets on the the air that look just like packets
sent by a device tuned to the 20 MHz channels. So if a device is
on the 40 MHz channel that is the pair of {36,40}, then when it
transmits a 20L packet, it should be received by a device tuned
to the 20 MHz channel 36 just as if the transmitter had been
tuned to 36. So in that way you could think of it as an
alias---at least from what you would see on the air. But packet
reception would be from a radio that is really tuned to a 40 MHz
wide channel. I've got to assume that the transmit side would
also be operating in a 40 MHz mode as it generated the 20U or 20L
packet. So these transmit/receive modes are different than being
tuned to a 20 MHz channel.

I think it is an important piece of information for capture on
both transmit and receive. For instance, if a capture shows that
a receiver is getting a higher rate of packet errors when it
receives 20L packets from the 40 MHz channel pair {36,40}, than
it is when receiving 20 MHz packets while tuned to 36, then you
might be suspicious of how well the 20L decode is working. If the
capture just reported 20 MHz packets on 36 in both cases, you
would not have anything to go on. Same sort of example for tx.

Also, on use of RadioTap as an app level 802.11 packet format,
you would want to be able to make the distinction between
remaining on a 40 MHz channel and sending a 20L packet, and
actually switching to lower 20 MHz channel and sending a packet.

-Bill

  parent reply	other threads:[~2010-02-03  5:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 14:26 MCS field: RFA Matteo Croce
     [not found] ` <40101cc31001260626g4a47b7c6gde6f99e477e69ac9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-26 17:47   ` David Young
     [not found]     ` <20100126174728.GV1060-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2010-01-27  9:36       ` Johannes Berg
     [not found]         ` <1264584965.25642.15.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2010-01-27 15:30           ` David Young
     [not found]             ` <20100127153002.GC1060-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2010-01-27 15:32               ` Matteo Croce
2010-02-01 22:09                 ` Bill Stafford
     [not found]                   ` <loom.20100201T230554-2-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-02-02 18:24                     ` Johannes Berg
2010-02-02 19:54                     ` David Young
     [not found]                       ` <20100202195424.GE1060-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2010-02-03  5:24                         ` Bill Stafford [this message]
     [not found]                           ` <C33B109A-9A6C-4931-8A69-5147A418E8B5-BUHhN+a2lJ4@public.gmane.org>
2010-02-04  1:11                             ` Joshua (Shiwei) Zhao
     [not found]                               ` <d521a2311002031711i4293ae26i8c460aa3f41997e6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-04  5:50                                 ` Bill Stafford
     [not found]                                   ` <1F39C830-A521-456A-A5FA-2FC97914A74A-BUHhN+a2lJ4@public.gmane.org>
2010-02-04  6:14                                     ` Joshua (Shiwei) Zhao
2010-03-25 23:50                         ` David Young
     [not found]                           ` <20100325235000.GX414-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2010-03-26  4:57                             ` Johannes Berg
     [not found]                               ` <1269579436.4581.0.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2010-08-09 12:10                                 ` Johannes Berg
2010-02-02 17:36 ` Bill Stafford
     [not found]   ` <loom.20100202T174119-204-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-02-02 18:20     ` Johannes Berg
2010-02-02 18:24     ` David Young
2010-02-06 20:02 ` MCS field: RFA (wireshark patch) Bill Stafford
     [not found]   ` <loom.20100206T204036-824-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-02-06 20:31     ` Johannes Berg
2011-04-18  9:49 ` MCS field: RFA Roberto Riggio
     [not found]   ` <loom.20110418T114722-716-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-04-18 10:01     ` Johannes Berg
     [not found]       ` <1303120873.3588.5.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2011-04-18 10:06         ` Roberto Riggio
     [not found]           ` <BANLkTikV_YxYnFxjHrFE7XgYfi1T7J=3Tw@mail.gmail.com>
     [not found]             ` <BANLkTikV_YxYnFxjHrFE7XgYfi1T7J=3Tw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-20 13:12               ` Roberto Riggio
     [not found]                 ` <4DAEDBAB.5070100-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
2011-04-21 15:04                   ` Matteo Croce
     [not found]                     ` <BANLkTi=psWmOSJXDRQvGC2ABwYfR=8EFrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-22  7:07                       ` Roberto Riggio
2010-08-30 21:21 Bill Stafford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C33B109A-9A6C-4931-8A69-5147A418E8B5@me.com \
    --to=bill.stafford-buhhn+a2lj4@public.gmane.org \
    --cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).