From: Simon Barber <simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Subject: Re: HE (11ax) extensions
Date: Mon, 13 Feb 2017 11:42:26 -0800 [thread overview]
Message-ID: <0FB8C34C-910C-404F-97BA-18BB7F8949C4@superduper.net> (raw)
In-Reply-To: <1487014748.19813.5.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
It’s not correctly implemented on captures from Macs - it increments for every MPDU. TSF is reliable on all platforms that I’ve seen, although has different reference points for different platforms.
One things that is very odd is the different parameters for MU - 4 sets, but I’ve only ever seen 1 MPDU reported. How is this supposed to be used?
Simon
> On Feb 13, 2017, at 11:39 AM, Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
>
> On Mon, 2017-02-13 at 11:33 -0800, Simon Barber wrote:
>> For HT and VHT one of the things that is missing is the total length
>> of aggregates (including padding) - it’s in the L-SIG header, would
>> be nice to have it exposed (since most chipsets pass up everything
>> that’s in the header).
>
> I don't know about "most", but I know ours doesn't :-)
>
>> Also some standardized way to put aggregates back together. My latest
>> wireshark extension uses same TSF as that clue.
>> See https://code.wireshark.org/review/#/c/20043/
>
> We already have that, in the A-MPDU status field there's a reference
> number that's supposed to be constant within the same A-MPDU and change
> between consecutive A-MPDUs.
>
> johannes
next prev parent reply other threads:[~2017-02-13 19:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 13:23 HE (11ax) extensions Johannes Berg
[not found] ` <1486992211.19813.1.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-13 19:33 ` Simon Barber
[not found] ` <D96F5F50-5B44-487C-8FF8-36A793960B7D-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2017-02-13 19:39 ` Johannes Berg
[not found] ` <1487014748.19813.5.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-13 19:42 ` Simon Barber [this message]
[not found] ` <0FB8C34C-910C-404F-97BA-18BB7F8949C4-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2017-02-13 19:49 ` Johannes Berg
[not found] ` <1487015370.19813.7.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-13 20:08 ` Simon Barber
[not found] ` <4443A151-EFD0-44A4-A892-C40218EE0291-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2017-02-13 20:14 ` Johannes Berg
2017-02-15 8:58 ` Johannes Berg
2017-02-15 9:08 ` Guy Harris
2017-02-13 19:40 ` Johannes Berg
2017-02-15 9:05 ` Johannes Berg
2017-02-15 12:48 ` Johannes Berg
[not found] ` <1487162908.31885.1.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-22 11:54 ` Johannes Berg
[not found] ` <1487764486.2215.5.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-28 7:28 ` Johannes Berg
[not found] ` <1488266885.2388.0.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-06-27 13:41 ` Johannes Berg
2017-09-08 8:35 ` Johannes Berg
[not found] ` <1504859711.6177.12.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-10-25 11:54 ` Johannes Berg
[not found] ` <1508932475.2421.34.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-10-25 12:17 ` Arend Van Spriel
[not found] ` <CAF7Mx6qFmbyDex8VOV9sxbMXofQVk9dpzBQNK0S57GCTfbw_PA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-25 12:18 ` Johannes Berg
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=0FB8C34C-910C-404F-97BA-18BB7F8949C4@superduper.net \
--to=simon-vp0mx6+5gkqfx2apin6yfw@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=radiotap-S783fYmB3Ccdnm+yROfE0A@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).