RadioTap Archive on lore.kernel.org
 help / color / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Guy Harris <guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org,
	aviya.erenfeld-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: [FINAL] timestamp field
Date: Fri, 05 Aug 2016 12:49:14 +0200
Message-ID: <1470394154.2977.36.camel@sipsolutions.net> (raw)
In-Reply-To: <3D113CB9-8919-47DB-96C1-9E40AB9AC9D6-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>

On Fri, 2016-08-05 at 03:46 -0700, Guy Harris wrote:
> On Aug 4, 2016, at 10:48 PM, Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org
> > wrote:
> 
> > Since there was no objection, reposting as final - will adopt in a
> > week
> > from now unless there are any final objections.
> > 
> > The definition can be found at
> > http://www.radiotap.org/suggested-fields/timestamp
> 
> Does the fact that the Wireshark patch doesn't involve an
> FT_ABSOLUTE_TIME field mean that the time stamps aren't relative to
> some fixed time such as the UNIX epoch, so that they can be used to
> calculate the time between two events but not the wall-clock time of
> a single event?

I don't see a way to make them absolute, but it's something we could
consider adding perhaps? Maybe eventually wifi hardware will have some
clock sync with something.

Right now my main use-case is going to be exporting the timestamp from
the hardware, which isn't like the existing MACTIME, and then using
that to synchronize two or more captures (by finding common frames,
like beacons).

I must admit I hadn't thought about absolute times in the context of
radiotap at all.

johannes

  parent reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05  5:48 Johannes Berg
     [not found] ` <1470376101.2977.7.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2016-08-05 10:46   ` Guy Harris
     [not found]     ` <3D113CB9-8919-47DB-96C1-9E40AB9AC9D6-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2016-08-05 10:49       ` Johannes Berg [this message]
2016-08-12  7:45   ` [ADOPTED] " Johannes Berg

Reply instructions:

You may reply publically 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=1470394154.2977.36.camel@sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=aviya.erenfeld-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=guy-FrUbXkNCsVf2fBVCVOL8/A@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

RadioTap Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/radiotap/0 radiotap/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 radiotap radiotap/ https://lore.kernel.org/radiotap \
		radiotap@radiotap.org
	public-inbox-index radiotap

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.netbsd.radiotap


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git