radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Guy Harris <guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Re: Assigning a new DLT_ value for "standardized" radiotap?
Date: Wed, 17 Feb 2010 09:27:52 +0100	[thread overview]
Message-ID: <1266395272.4006.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5F21AFA5-4D4C-49A0-A228-A1177630E366-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 368 bytes --]

On Tue, 2010-02-16 at 18:08 -0800, Guy Harris wrote:
> The presence-bit-number collisions mentioned on the radiotap Web site
> appear to be due to OpenBSD doing its own thing:
> 
> 	14: FCS in OpenBSD, RX Flags in the standard and assigned for that in
> NetBSD and Linux

Didn't I go and add a preferences setting to wireshark for this
collision?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2010-02-17  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  2:08 Assigning a new DLT_ value for "standardized" radiotap? Guy Harris
     [not found] ` <5F21AFA5-4D4C-49A0-A228-A1177630E366-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2010-02-17  8:27   ` Johannes Berg [this message]
     [not found]     ` <1266395272.4006.0.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2010-02-17  8:38       ` Gábor Stefanik
     [not found]         ` <69e28c911002170038q2a401120l369b5dffaa016e01-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-17 18:49           ` Guy Harris

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=1266395272.4006.0.camel@jlt3.sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=guy-FrUbXkNCsVf2fBVCVOL8/A@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).