All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Simon Barber <simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>,
	David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Cc: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Subject: Re: [RFC] capture file timestamping
Date: Thu, 17 Sep 2015 18:51:38 +0200	[thread overview]
Message-ID: <1442508698.2821.16.camel@sipsolutions.net> (raw)
In-Reply-To: <55DE4244.9030407-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>

On Wed, 2015-08-26 at 15:48 -0700, Simon Barber wrote:
> 
> This is exactly what I was doing when I ran into the current TSFT 
> field limitations a few years ago. 

Right, I vaguely remembered that, hence the CC :)

> GPL code is here:
> 
> https://github.com/parc-wifi/wireshark

> I'm working on getting this updated for 11ac now, so revisiting some 
> of the same issues.

Ah, that's really nice! I really needed something like this the other
day, will check it out.

> The HT and VHT headers in radiotap are incomplete, and would be much 
> nicer if they could just include the signal field from the plcp 
> (perhaps with a mask to indicate parts that are missing). This would 
> be a better approach for 60GHz I think.

Yeah, can't really object to that, even if we might not be able to
provide all the data for all the hardware, and might have to re
-assemble the field from the available parsed data.

As far as our device is concerned we might perhaps be able to include
this data in firmware's monitor mode.

> I'd like to display the L-SIG txop protection on the timeline as 
> well.
> 

Good idea.


As far as the timestamp is concerned though, what would you suggest?

Also, what timestamp would be best for a tool like yours? I'm assuming
ours, which is the signal detection timestamp and inherently vague by
perhaps a dozen microseconds won't really work that well.

johannes

      parent reply	other threads:[~2015-09-17 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 10:07 [RFC] capture file timestamping Johannes Berg
     [not found] ` <1440497229.2192.28.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-08-25 16:28   ` David Young
     [not found]     ` <20150825162841.GR6823-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2015-08-25 16:46       ` Johannes Berg
     [not found]         ` <1440521168.2192.50.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-08-25 17:47           ` Guy Harris
     [not found]             ` <4E4FE63E-B636-4808-BBFF-6D2CE4EAFB2F-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2015-08-25 17:55               ` Johannes Berg
2015-08-26 22:48           ` Simon Barber
     [not found]             ` <55DE4244.9030407-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2015-09-17 16:51               ` Johannes Berg [this message]

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=1442508698.2821.16.camel@sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
    --cc=radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org \
    --cc=simon-vp0mx6+5gkqFX2APIN6yfw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.