Linux wireless drivers development
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: Daniel Golle <daniel@makrotopia.org>
Cc: battlemesh@ml.ninux.org, gnunet-developers@gnu.org,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: [Battlemesh] wifibroadcast
Date: Sun, 23 Apr 2017 00:01:41 +0200	[thread overview]
Message-ID: <1806801.tVQKAhPZbv@prime> (raw)
In-Reply-To: <20170422153703.GE1681@makrotopia.org>

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

Hi Daniel,

On Saturday, April 22, 2017 5:37:03 PM CEST Daniel Golle wrote:
> Hi Simon,
> 
> On Fri, Apr 21, 2017 at 09:55:03PM +0200, Simon Wunderlich wrote:
> > Hi Daniel,
> > 
> > >     mac80211: Parse legacy and HT rate in injected frames
> > 
> > Yup, Sven was so kind and helped with this. :D
> > 
> > I'm experimenting with some opportunistic routing ideas ...
> 
> I just realized that the radiotap headers are still not part of the
> UAPI exported by the kernel. How is one supposed to go about this
> issue? Have lots of diverging local copies of ieee80211_radiotap.h?

Propose a patch and send it to linux wireless to move it? :)

> And change all the kernel-specific types (u16 and such) into their
> corresponding userland types (u_int16)...?

Hmm, uapi is full with __u16, __u32, ... see linux/types.h

> 
> I'd be glad if you can share your idea about proper and/or intentional
> use of the kernel's radiotap capabilities...

Well, there is a radiotap parser in the kernel which is quite useful for 
reading (net/wireless/radiotap.c). And there is a radiotap library which also 
does parsing [1] (seems it's based on the kernel implementation), referenced 
from radiotap.org [2]. What is missing (or at least I didn't find it and 
implemented something on my own) is a library/function to build radiotap 
headers (i.e. for writing). There are quite a few things to consider (padding, 
alignment, etc). To make it useful, you would also need to build ieee80211 
headers at the same time ...

I have some rough working C code for all of that (integrated into something 
bigger), not sure if it would be useful to make a library out of it.

I don't have an idea about "proper" usage though. Since Johannes seems to 
maintain most of that radiotap stuff, I'm CC'ing him and linux-wireless. Maybe 
there is already more than what we know. :)

Cheers,
      Simon

[1] https://github.com/radiotap/radiotap-library/blob/master/radiotap.c
[2] http://www.radiotap.org/

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

       reply	other threads:[~2017-04-22 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANjd3nfeiGgaHMcgOyKOKhRRKEwnn43VgC4GRcw-fuCkCdg2zQ@mail.gmail.com>
     [not found] ` <2945991.ay5rM9MeUZ@prime>
     [not found]   ` <20170422153703.GE1681@makrotopia.org>
2017-04-22 22:01     ` Simon Wunderlich [this message]
2017-04-25 14:37       ` [Battlemesh] wifibroadcast 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=1806801.tVQKAhPZbv@prime \
    --to=sw@simonwunderlich.de \
    --cc=battlemesh@ml.ninux.org \
    --cc=daniel@makrotopia.org \
    --cc=gnunet-developers@gnu.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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